Order of included files in sproutcore/javascript.js after sc-build not the same as when you run sc-server in production mode.
Reported by Lawrence Pit | August 17th, 2008 @ 08:46 PM | in REL 0.9.21
See this thread:
http://groups.google.com.au/grou...
When you run sc-server in production mode it will create one big sproutcore/javascript.js file. For me this worked fine, however, it turns out that when you do an sc-build which creates a sproutcore/javascript.js file in /tmp the content is distinctly different, leading to errors that weren't present when running in production mode. The output of both should be exactly the same though.
Comments and changes to this ticket
-

Erich Ocean (onitunes) September 30th, 2008 @ 04:07 AM
- → Milestone changed from to REL 0.9.21
- → State changed from new to open
- → Assigned user changed from to Erich Ocean (onitunes)
-

Erich Ocean (onitunes) November 8th, 2008 @ 09:26 AM
- → Assigned user cleared.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
SproutCore: JavaScript Application Framework
Source available from github
The Git repository resides at http://github.com/sproutit
Check out the current development trunk with:
git clone git://github.com/sproutit/sproutcore.git
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Submitting Patches
Resist adding new tags, use the ones in the tag cloud already. If you are submitting a patch or a pull request from a fork, tag the ticket as a "patch". If you are submitting a new feature enhancement, tag it as "enhancement". If you are submitting a fix for a bug, tag it as "fix".
Thanks!
We're glad you're contributing. Feel free to drop by the Google Group as well to let us know you are involved.
