[ALOY-640] Don't minify backbone.js and underscore.js in development build
|Affected Version/s||Alloy 1.1.0|
|Fix Version/s||Alloy 1.2.0, 2013 Sprint 09|
|Components||Runtime, Titanium SDK|
DescriptionThis is related to profiling alloy project. For the stacktrace we get back for the profiling data that includes JS library such as backbone.js and underscore.js in alloy project, since those sources are currently minified, the line number info just shows line 1, and user can't exactly tell which part of the code in the library is taking the specific amount of the time. The suggestion here is to not minimize them in development build.
- Tony Lukasavage 2013-04-27
underscore.jsPR: https://github.com/appcelerator/alloy/pull/121 test case: https://github.com/appcelerator/alloy/tree/master/test/apps/testing/underscore 8 tests fail on the iOS 6.1 iPhone simulator. 14 fail on the Android 2.2 Google APIs HVGA emulator. These are expected results.
backbone.jsPR: https://github.com/appcelerator/alloy/pull/122 test case: https://github.com/appcelerator/alloy/tree/master/test/apps/testing/backbone 0 tests fail on the iOS 6.1 iPhone simulator. 1 fails on the Android 2.2 Google APIs HVGA emulator. These are expected results. In addition to this test app, it would be a good idea to test at least a few model-based test apps, like [models/todo](https://github.com/appcelerator/alloy/tree/master/test/apps/models/todo) or [models/sql_queries](https://github.com/appcelerator/alloy/tree/master/test/apps/models/sql_queries).