2.1.0 (2024-01-09)
- all: update packages (1837254)
- android: add collapseToolbar support (#1360) (c3f5e95)
- update momentjs (#1358) (100ff29)
- update underscore to version 1.13.6 (36b2fc8)
1.17.3 (2022-01-10)
- pin colors version to avoid dos issue (5f10891)
1.17.2 (2022-01-04)
1.17.1 (2021-11-17)
- compile/hook: error if unable to find the alloy cli (166dc3b)
1.17.0 (2021-11-02)
- compile/sourcemap: use path.join rather than manually constructing a path (537107d)
- all: set default backbone version (fb845f7)
1.16.4 (2021-09-17)
1.16.3 (2021-06-29)
- generate: mark name as optional as it is not required for jmk (bc0e06f)
- new: mark dir as optional as it is not required (d151848)
1.16.2 (2021-06-15)
- compile: don't create widget sourcemaps if sourcemaps are disabled (b1259b1)
1.16.1 (2021-06-08)
- compile: generate source maps for lib files in widgets (ba8d4c2)
1.16.0 (2021-03-03)
- support using OptionBar (93c2df1)
1.15.4 (2021-01-04)
1.15.3 (2020-11-23)
- ALOY-1732 - Add ability to run in the background without UI #959
- ALOY-1733 - Add template for Alloy + webpack usage #963
- ALOY-1256 - Allow using a Widget as a primary control in an XML View #949
- ALOY-1253 - Support WPATH in widget XML view attribute values #948
- ALOY-1720 - Version string comparison will break for SDK 10.0.0 #960
- ALOY-1734 - Declare Alloy globals before execution of app.js/alloy.js #964
- Update node.extend
- Correctly get node name in alloy global transform
- ALOY-1598 - Fix error with binding_no_persistence sample #882
- ALOY-1693 - Maintain db connection during sql sync #933
- ALOY-1633 - Inject _, Alloy, and Backbone variables into files when used rather than make available as globals #911
- ALOY-1701 - XML: Unable to use platform namespace restriction on event handlers #940
- ALOY-1705 - Fix to allow return outside of function #939
- ALOY-1706 - Compile error if Alloy view filename contains hyphen #938
- ALOY-1697 - Add WebView "onlink" callback support
- ALOY-1698 - Compile: Errors thrown during sourcemap step are not visible to a user
- ALOY-1632 Allow passing custom template directories to the
alloy newcommand #912 - ALOY-1646 Allow platform xml namespaces to be used with xml attributes in Alloy #922
- XML attributes can now be prefixed with a platform to have the property be platform specific. For example
<Label android:text="Hello Android!" ios:text="Hello iOS!" windows:text="Hello Windows!" />
- XML attributes can now be prefixed with a platform to have the property be platform specific. For example
- ALOY-1363 Add support to set object properties via XML #765
- Properties that are objects (like
font) can now be set in XML as well as TSS files. For example to set thefont.fontFamilyproperty use<Label font.fontFamily="Roboto">Hello</Label>
- Properties that are objects (like
- ALOY-1316 Support use of $.args.* in any XML attribute or TSS property #885
- ALOY-1629 Upgrade to babel 7 packages #905
- ALOY-1652 Improve handling of missing directories and files in
alloy new#925 - ALOY-1682 Update to moment to 2.24.0 and update moment locales. #928
- Previous version was 2.21.0
- New locales are ar-dz, ar-kw, ar-ly, bm, de-ch, dv, en-SG, en-ie, en-il, en-nz, es-do, es-us, fr-ch, ga, gd, gom-latn, gu, it-ch, kk, kn, ku, ky, lo, mi, mn, mt, nl-be, pa-in, sd, se, ss, sw, te, tet, tg, tlh, ug-cn, ur, uz-latn, x-pseudo, yo, zh-hk,
- ALOY-1683 Update to Underscore.js 1.9.1 #929
- Previous version was 1.8.3
- ALOY-1648 Include Backbone.js 1.4.0 #929
- Includes 42 new locales
- ALOY-1505 Add ability to set cancel and destructive properties on OptionDialog options #879
- ALOY-1612 CLI: Be able to use Alloy source-maps in Safari Debugger / Chrome Dev-Tools #893
- ALOY-1535 Only warn when using an AlertDialog with child views not restricted to Android #810
- ALOY-1653 Runtime error on Android when using optiondialog and not declaring destructive or cancel properties #926
- ALOY-1684 Calling sort for a collection does not call the dataFunction as of backbone 1.1.2 and above #929
- ALOY-1690 sourcemaps not being generated for files under lib #893
- ALOY-1691 Source maps report incorrect "file" value #893
ALOY-1686 Alloy: App crashes due to context used when accessing Ti.Database API
ALOY-1650 Debugger does not hit breakpoints when running Android on Windows
ALOY-1644 Selective compilation does not regenerate platform app.js on Windows
ALOY-1641 iOS: TabbedBar usage on lower than SDK 8 is broken
ALOY-1640 Update TabbedBar to use the Ti.UI namespace
ALOY-1637 ES6 code frame fails when using duplicate variable declarations
ALOY-1639 Update animation library to use createMatrix3D/createMatrix2D in place of the deprecated create3DMatrix/create2DMatrix
ALOY-1638 Theme is "null" when a theme is defined in config.json
ALOY-1622 Error on sql migration due to undeclared variable
TIMOB-24817 Support defining Alloy widgets in ListView templates
- ALOY-1603: Update momentjs to 2.21.0
- View the momentjs release notes here, previous version was 2.16.0
- ALOY-1606: Android: Debugger not hitting breakpoints on Windows
- ALOY-1602: Avoid some global variables to be only available in parent controller
- Thanks to @clementblanco for this contribution!
- ALOY-1607: Fix BaseController.removeListener
- Thanks to @jormagar for this contribution!
- ALOY-1609: Add plugins/ti.alloy to gitignore
- ALOY-1599: Model Data binding problem with the first upper case in the model src
- Thanks to @darknos for this contribution!
- ALOY-1595: alloy compile broken on node 9.3.0
- PR-878: Fix links in README
- Thanks to @dfrankow for this contribution!
- No changes, just a version bump
- ALOY-1597: Improve compile error messages to include a code frame that point to source locations
- ALOY-1596: Do not copy Mobileweb assets on alloy new
- ALOY-1592: Builtins: Reimplement measurement by convertUnits
- ALOY-1534: Add support for Backbone 1.3.3 and Underscore 1.8.3
- ALOY-1528: Checks the theme’s config.json for dependencies when returning widget directories
- ALOY-1168: Replace Underscore with Lodash for Alloy compile
- ALOY-1593: Android Debugger: Some breakpoints not hit if "Resume" is done anytime during debug
- ALOY-1590: OS_IOS assigned to a variable causes a crash
- CLI-1272: Removed mobileweb and blackberry from studio config.json template
- ALOY-1584: Android: Ti.UI.Toolbar has no click event
- ALOY-1318: DefaultIcon(-platform).png should be theme-able
- ALOY-1582: Fix Ti.Platform.osname on Windows
- ALOY-1574: Unable to use ES6 import/exports in alloy controllers
- TIMOB-25269: iOS: Add iPhone X screenshots
- ALOY-1579: Support Titanium.UI.Android.DrawerLayout
- ALOY-1578: Move Ti.UI.iOS.Toolbar to Ti.UI.Toolbar
- ALOY-1572: Alloy doesn't compile external app.js
- ALOY-1564: Broken Require data-binding event translation
- ALOY-1524: Replace wrench with fs-extra
- ALOY-1570: exports.baseController does not work since 1.10.0
- ALOY-1567: Minification produces invalid code
- Remove the minification process from Alloy and handle it from the SDK instead.
- ALOY-1565: KitchenSink v2 errors out on iOS
- Fix to use only 3 of babili's plugins to 'optimize' code and avoid modifying code in a way our old TiCore on iOS chokes on.
- ALOY-1312: Upgrade Alloy to support ES6
- Migrates from using uglifyjs to parse and transform user and library code to using babel and babili
- ALOY-1365: Added support for Alloy-specific i18n and platform folders for both the whole Alloy app and overridable at the theme level. Improved widget i18n support.
- CLI-768: Alloy app fails to build on Windows with error "Alloy compiler failed"
- ALOY-1300: iOS Assets Catalog inconsistency between Alloy and Classic
- ALOY-1239: Set Node 0.10 as minimum supported version
- ALOY-1299: Cannot build a new project for iOS due to missing appicons
- ALOY-1226: To Do sample app - validate() fails to prevent invalid (empty) items from being added
- ALOY-1288: Windows: Label not visible when using default app.tss
- ALOY-1287: Alloy styles compilation does not produce the same results across successive compilations
- ALOY-1280: Support CommandBar in XML markup on Windows
- ALOY-1214: Button in Inheritance sample app difficult to click on iOS
Alloy 1.6.2 is a patch release addressing high-priority issues from previous releases.
- ALOY-1272: Building an Alloy project with the Titanium CLI on Windows fails
Full list of Issues that were addressed in Release 1.6.0
To prepare for forthcoming Windows Phone support, Alloy and the Titaium SDK now support the
windows subfolder to include assets only for Windows Phone applications. If have existing
windows subfolders, you will need to rename them and update any paths.
Alloy 1.6.0 introduces support for Backbone 1.1.2. Due to breaking changes from Backbone 0.9.2 to 1.1.2, Alloy still uses Backbone 0.9.2 as its default Model and Collection implementation. You will need to update the configuration file to use the newer Backbone library, then update your application to fix the breaking behavior changes and take advantage of the new Backbone features.
In the future, Backbone 1.1.2 will become the default and 0.9.2 support will be deprecated and eventually removed.
For details, see the Alloy Backbone Migration guide.
The Alloy CLI extract-i18n command now extracts localized strings from the XML files, in addition to
the JavaScript and TSS files, to populate the strings.xml file.
The underscore.js library was upgraded from version 1.4.4 to version 1.6.0.
To prepare for forthcoming Windows Phone support, Alloy added several conditionals to support logic, UI elements and assets to only be included with Windows Phone applications.
- In controllers, use the
OS_WINDOWSconstant. - In XML and TSS files, assign the
platformattribute of UI elements awindowsvalue. - Under the component folders in the
appfolder, addwindowssubfolders to include assets only for Windows Phone.
- Support <ActionView/> as a child tag of the <MenuItem> object to set the
actionViewproperty ofTitanium.Android.MenuItem. Only supports the Android platform.
Below are the fixes included in this release.
- ALOY-1149. iOS: Gradient array properties are converted into objects
Full list of Issues that were addressed in Release 1.5.0
The sample widgets included in the Alloy repository have been removed.
To find replacements for these widgets, or to find other widgets, we recommend you visit http://gitt.io.
As of this Release, the localStorage sync adapter is deprecated and will be removed in a future
release.
Use the properties sync adapter instead.
The moment built-in now uses version 2.7.0 of the moment.js library.
-
Support data binding for a Picker. Add data binding attributes to the PickerColumn and map model attributes to the PickerRow properties.
-
Support mixture of text and data binding notation when binding model attributes to XML attributes, for example,
<Label text="first name: {model.first_name}"/>. -
Support mapping multiple model attributes to a single XML attribute, for example,
<Label text="{model.title} by {model.author}">.
For more details, see Alloy Data Binding.
-
Support setting ActionBar properties in XML and TSS using the
ActionBarelement. For XML markup, add the<ActionBar/>tag as a child of either a<TabGroup/>or<Window/>. Before this Release, you defined ActionBar properties in theMenuelement. Do not set the same ActionBar properties in both theActionBarandMenuelements. For more details, see the "Android ActionBar" section in Alloy XML Markup. -
Support
<KeyboardToolbar/>as a child tag of the<TextArea/>object to set thekeyboardToolbarproperty ofTitanium.UI.TextArea. Only supports the iOS platform. -
Support
<AndroidView/>or<View/>as a child tag of the<AlertDialog/>and<OptionDialog/>objects to set theandroidViewproperty. Only supports the Android platform. -
Support the localization function
L()with the Label'stextproperty or as node text, for example,<Label text="L('foo')"/>or<Label>L('foo')</Label>. -
Support spaces with the comma-separated values in the
platformattribute, for example,<Label platform="ios, android"/>. Prior to this Release, placing spaces in the platform attribute would throw an error.
Below are the fixes included in this release.
- ALOY-1091. id property of other than 'picker' is treated as a variable
- ALOY-1094. Date or time pickers: cannot use Ti.UI.* type constants, must use Titanium.UI.* abbreviations
Full list of Issues that were addressed in Release 1.4.0
The sample widgets included in the Alloy repository are deprecated and will be removed from the repo in a future version. There are known issues with some of the widgets, which will not be addressed.
If you would like to take over maintenance and support for any of these widgets, please contact Tim Poulsen at tpoulsen@appcelerator.com.
To find replacements for these widgets, or to find other widgets, we recommend you visit http://gitt.io.
This release introduces two new compiler directives used to distinguish distribution targets:
DIST_ADHOC: true if the current compiler target is built for iOS Ad Hoc distribution, for example, if you set the-T dist-adhocoption when building with the Titanium CLI.DIST_STORE: true if the current compiler target is built for deployment to the Google Play Store or iTunes App Store, for example, if you set the-T dist-storeoption when building with the Titanium CLI.
Use these compiler directives in your controller code or initializer file (alloy.js).
Note that the ENV_PRODUCTION constant will be true too since these deployments are only for production builds.
As of this Release, Alloy provides a new way to create controller-less views. Each component in
the controller-less view needs to be assigned an id attribute. Using the Require or Widget
elements to include external views in the controller-less view does not work using this procedure,
that is, you can include the external views, but the styles cannot be updated with the updateViews
method.
- Use the
Alloy.createController()method to create a controller from the controller-less view. - Use the updateViews() method with the controller instance to update the styles of the view components. Pass a style dictionary as the only argument to the method. The style dictionary contains key-value pairs, where the key is the id of the view component and the value is another dictionary containing key-value pairs of attributes you want to set for the view component.
- Use the
getView()method with the controller instance to retrieve the view of the controller, which can be added to another view.
See also:
This release introduces the ability to use a custom query to determine if a style should be applied or not. For example, the application can query if the device is running iOS 7 or later, then apply a style to compensate for view components appearing behind the status bar.
To use a custom query:
- Define a conditional statement, which returns a boolean value, and assign it to a property in
the
Alloy.Globalsnamespace. - Assign the
ifattribute to an element in the XML file or in the conditional block of the TSS file to the defined query with theAlloy.Globalsnamespace.
See also:
This release introduces better integration with the ti.map module,
which includes the ability to define Annotation objects in XML markup and support for data-view binding.
To add Annotation objects in the XML markup, use the <Module> tag to load the map module
and create a map view. Add <Annotation> tags as children of the <Module> tag.
To support data-view binding, set the dataCollection attribute to the name of the collection in
the <Module> tag. Map attributes to bind in the <Annotation> tag. The <Module> tag also
supports the dataFilter and dataTransform attributes.
<Alloy>
<Collection src="places"/>
<Window>
<Module id="mapview" module="ti.map" method="createView" dataCollection="places">
<Annotation latitude="{latitude}" longitude="{longitude}" title="{title}" />
</Module>
</Window>
</Alloy>
See also:
- Alloy Example in ti.map module
- Map Module test app
- Map Module with Data Binding test app
The Alloy CLI can now generate controller, view and style components for widgets.
Add the --widgetname <WIDGET_NAME> option to the alloy generate command
to create components for the specified widget.
This release supports themes for widgets. Widget themes work the same as project themes except for the placement of the files.
Inside your theme folder (app/themes/<THEME_NAME>), create widgets/<WIDGET_NAME> folders,
where <THEME_NAME> is the name of the theme and <WIDGET_NAME> is the name of the widget.
Create two folders, assets and styles, to place your custom images and styles for your widget,
respectively. The assets and styles folders need to be placed in the folder that is named after
the widget.
If the theme is enabled, the files in the widget theme folder will replace the default ones used by the widget.
See also:
- "Themes" section in Alloy Widgets
- Widget Themes test app
-
Support the Android Action Bar in XML and TSS using the
Menuelement. To define an action bar in XML markup, add the<Menu>tag as a child of either a<Window>or<TabGroup>. To add action items in XML markup, add<MenuItem>tags as children of<Menu>. TheActionBarattributes may be defined in the XML markup or TSS file. For details, see the "Android ActionBar" section in Alloy XML Markup. -
Support
Buttonattributes in<LeftNavButton>and<RightNavButton>. Instead of creating aButtonobject for theLeftNavButtonorRightNavButtonelements, add theButtonattributes to eitherLeftNavButtonorRightNavButtonin either the XML markup or the TSS file. For details, see the "iOS Navigation Button Shorthand" section in Alloy XML Markup. -
Support Date Picker attributes. The maxDate minDate, and value attributes now accept date strings. For Alloy XML and TSS files, use a date string that can be parsed by the moment.js constructor, which includes ISO-8601 and RFC2822 dates.
-
Support the localization function,
L(), as node text for theOptionDialog's<Option>tag. -
Support Titanium.UI.RefreshControl in XML markup. Add the
<RefreshControl>tag as a child of either<ListView>or<TableView>. -
Add shorthand notation for
TextFieldkeyboard attributes. When specifying either thekeyboardTypeorreturnKeyTypeattributes, you do not need to useTitanium.UI.KEYBOARD_orTitanium.UI.RETURNKEYTYPE_as part of the constant name. For details, see the "TextField Keyboard Shorthands" section in Alloy XML Markup. -
Support
undefinedas a settable value in the TSS files. Assignundefinedto an attribute to unset it. Do not encaseundefinedin quotes.
See also:
- Action Bar test app
- Button Shorthand test app
- Date Picker test app
- Options Dialog with Localization Function test app
- Refresh Control test app
- Text Field Keyboard Shorthand test app
Alloy 1.4.0 includes changes to the Alloy plugin, which is used by Studio to compile and launch your project. These changes will be applied automatically the first time you build a project after updating to 1.4.0. However, because the first build uses the old plugin, there is a small chance that it will fail. Retrying the build should resolve the issue, or you can manually update the plugin with the following command:
alloy install plugin [path_to_project]
If you enter this command while in your project's folder, omit the path.
CLI users are not affected by this change.
The following APIs are new in Release 1.4.0.
| API | Type | Note |
|---|---|---|
Alloy.Controller.updateViews |
method | Applies a dictionary of properties to the components of a view in the controller. |
Below are the new key features and fixes in this release. Also see the full list of changes.
- ALOY-905. Alloy now supports TiSDK 3.0.0+ again!
- ALOY-907. Fixed unhandled exception errors in invalid JS.
- ALOY-912. Better handling of runtime conditionals on TableView proxy properties.
- ALOY-914. Show Alloy appicon instead of Titanium default.
- ALOY-916. Copy theme assets to platform-specific folders.
- ALOY-920. Fixes compile time error when using should.js.
- ALOY-922. Fixes error when using proxy properties on a TextField in an ItemTemplate.
- ALOY-937. Fixes copying of platform-specific widget assets.
Full list of Issues that were address in Release 1.3.0.
Due changes in the application build process for both Alloy and the Titanium SDK, Alloy 1.3.0 only supports Titanium SDK 3.2.0 and later. You can find details on this in the following tickets:
-
Support children elements for Widget and Require elements. View objects created using the Widget and Require elements can contain child view elements, which are added as children views of the parent Widget or Require view object. Example: require_children
-
Support
<HeaderView>,<FooterView>and<PullView>as children tags of the<ListView>object to specify theheaderView,footerViewandpullViewproperties ofTitanium.UI.ListView. -
Support
<SearchBar>and<SearchView platform="android>as children tags of the<ListView>object to specify thesearchViewproperty ofTitanium.UI.ListView. -
Support
<HeaderView>and<FooterView>as children tags of the<ListSection>object to specify theheaderViewandfooterViewproperties ofTitanium.UI.ListSection. -
Support
<LeftButton>,<RightButton>and<KeyboardToolbar>as children tags of the<TextField>object to specify theleftButton,rightButtonandkeyboardToolbarproperties ofTitanium.UI.TextField. These properties are only supported on the iOS platform. -
Support shorthand method for declaring iOS system buttons. When specifying the
systemattribute for a Button object, you do not need to use theTi.UInamespace. For example, the following markup creates the iOS camera button:<Button systemButton="CAMERA"/>
- Support for bitwise operators, which includes bit shifting ('>>', '<<', and '>>>'), bitwise AND ('&'), bitwise OR ('|') and bitwise XOR ('^').
-
Support fetching a model using its ID attribute rather than an SQL query with the SQLite sync adapter. For example, you can fetch a model by using the attribute:
myModel.fetch({id: 123});rather than using an SQL query:
myModel.fetch({query: 'select * from ... where id = ' + 123 });
This Release added a new compiler task called pre:load that is triggered before copying assets and
other resources to the project's Resources folder. This task is executed near the beginning of
the Alloy compiliation process, after the project is cleaned.
In the project configuration file (config.json), you can combine the os and env keys together
to specify an environment and platform configuration. For example, the code below specifies
configurations for iOS test, iOS development and iOS production:
"os:ios env:production": {
"foo": "os:ios env:production"
},
"os:ios env:development": {
"foo": "os:ios env:development"
},
"os:ios env:test": {
"foo": "os:ios env:test"
}
Previously, you could not specify both a platform and environment together.
The following APIs are new in Release 1.3.0.
| API | Type | Note |
|---|---|---|
Alloy.builtins.animation.flip |
method | Transitions from one view to another using a 3D flip animation (iOS only). |
Alloy.builtins.animation.flipHorizontal |
method | Transitions from one view to another using a horizontal flip animation (iOS only). |
Alloy.builtins.animation.flipVertical |
method | Transitions from one view to another using a vertical flip animation (iOS only). |
Alloy.builtins.animation.HORIZONTAL |
constant | Constant to specify a horizontal flip (iOS only). |
Alloy.builtins.animation.VERTICAL |
constant | Constant to specify a vertical flip (iOS only). |
- ALOY-813. Fixed bug handling unicode characters in XML attributes.
- ALOY-817. Fixed bug adding XML event handlers to UI components that use custom namesapces.
- ALOY-815 & ALOY-818. Support Ti.UI.iOS.NavigationWindow API in XML
- ALOY-789. Fixed improper handling of printable escape characters in TSS.
- ALOY-802. Fixed escape character handling issue in TSS on Windows.
- ALOY-803. Fixed issue with controller subfolders on Windows.
- ALOY-804. Fixed issues with
jakeon Windows.
- Full list of Issues that were addressed in Release 1.2.0
- Fixes for a handlful of Windows issues are available in the latest 1.2.1 release candidate. You can install it like this:
[sudo] npm install -g alloy@1.2.1-cr2.
As of this Release, Alloy supports changing styles dynamically during runtime. There are two methods
to support dynamic styling in Alloy. You can either generate a dynamic style dictionary that can be
passed to applyProperties or a create method, or modify TSS class styles to an existing component on
the fly.
For more information, see:
- Dynamic Styles guide
- dynamic_styling Sample
- Refer to the "New APIs" section below.
ListView objects can now be created in markup and with collection-view binding enabled.
For more information, see:
Use the new Module XML element to include a view from a native module.
For more information, see:
- "Module XML Element" section in the Alloy XML Markup guide
- native_modules Sample
Style files can be generated using the Alloy CLI. The Alloy CLI extracts the IDs and classes from the markup file to create a skeleton style file.
For more information, see the "Generating a Style" section in the Alloy Tasks guide.
The following APIs are new in Release 1.2.0.
| API | Type | Note |
|---|---|---|
Alloy.Controller.addClass |
method | Adds a TSS class to the specified view object. |
Alloy.Controller.createStyle |
method | Creates a dictionary of properties based on the specified styles. |
Alloy.Controller.removeClass |
method | Removes a TSS class from the specified view object. |
Alloy.Controller.resetClass |
method | Applies TSS classes to the specified view object and removes any applied classes that are not specified. |
Alloy.Controller.UI.create |
method | Creates a Titanium UI object with the specified styles. |
- ALOY-661. Code Processor: Get Alloy to recompile before an analysis
- ALOY-424. Blackberry support
- ALOY-628. Error loading platform-specific theme-based styles
- ALOY-632. Builtins being copied into Resources directory more than once causing runtime errors
- ALOY-633. Compiler directives (OS_IOS) undefined when referenced inside a widget
- ALOY-635. Styles not being sorted properly among global, controller, platform-specific, and theme
Just 2 quick fixes to reduce the size of the Alloy distribution and fix one regression.
- ALOY-625. app.tss not being applied to views that don't have view-specific styles.
- ALOY-626. Remove unneeded resources from samples/mapping.
The Alloy run command is obsoleted by the Titanium CLI build command.
If you are only using command-line tools to build your Alloy project, after using the
alloy compile command to convert the Alloy files to Titanium files, use the titanium build
command to build and run the Titanium code.
As of Titanium Studio 3.1.0, breakpoints added in Alloy Controllers and the alloy.js file are
recognized by the Studio Debugger. These breakpoints map to the code in the generated Titanium
files located in the Resources directory.
CommonJS modules and Alloy Models will support this feature in a future release of Titanium
Studio and Alloy. You still need to add breakpoints for these files in the generated Titanium
files located in the Resources directory.
Refer to Alloy Debugging for more information.
As of Titanium Studio 3.1.0, content assistance is supported in Alloy Views (XML markup and TSS files) and Alloy Controllers.
For XML markup, start typing the XML element, attribute or on attribute (for events)
to receive content assistance.
For TSS files, type the name of the element, class (element prefixed with .) or ID name
(element prefixed with #) to receive content assistance.
You need to type the entire name of the element, class or ID name to receive assistance, and
the class and ID name must exist in the associated XML markup file.
For controller code, type the ID name (element prefixed by $.) or start typing a namespace
(Alloy, Titanium, etc.) to receive content assistance. You need to type the entire name of the ID
in order to receive assistance and it must exist in the associated XML markup file.
Some of the Alloy-specific attributes, such as platform, formFactor and the data binding
attributes, will be supported in a future release of Titanium Studio.
Refer to the "Using Content Assistance" section in Alloy Tasks for more information.
ScrollableView, CoverFlowView, ButtonBar, ToolBar and TabbedBar objects support collection-view binding.
For ButtonBar, ToolBar and TabbedBar, refer to the binding_bars example.
For CoverFlowView, refer to the binding_coverflow example.
For ScrollableView, refer to the binding_scrollableview example.
Refer to Alloy Data Binding for more information.
Various enhancements to widgets:
-
Widgets have their own create methods. Use
Widget.createController(),Widget.createWidget(),Widget.createModel()andWidget.createCollection()instead of theAlloy.create*methods to create components relative to the widget context rather than the Alloy project. The method parameters are the same as theAlloy.create*methods. -
Widgets support their own models and collections. Use models and collections the same as with an Alloy project except use the new Widget create methods, that is, use
Widget.createModelandWidget.createCollectioninstead ofAlloy.createModelandAlloy.createCollection, respectively to create models and collections inside a widget.
Refer to Alloy Widgets for more information.
Various enhancements to XML markup:
-
Support
<LeftNavButton>and<RightNavButton>as children tags of the<Popover>object to specify theleftNavButtonandrightNavButtonproperties ofTitanium.UI.iPad.Popover. -
Support
<HeaderView>as a child tag of the<TableViewSection>object to specify theheaderViewproperty ofTitanium.UI.TableViewSection. -
Support the
nameattribute with the<Widget>and<Require>tags to specify a widget view-controller to use besideswidget.xml/widget.js.
Refer to Alloy XML Markup for more information.
The following changes alter the behavior of the Alloy Framework from previous versions and may require code changes to your applications.
Alloy 1.0 only supports Titanium SDK 3.0 and later. Previous versions of Alloy supported Titanium SDK 2.1.x and later.
For Alloy View proxies and Controllers, that is, objects either referenced with $.myid or
created with createController and getView methods, you cannot use the Backbone Events
API on, off and trigger methods to bind and unbind event callbacks, or fire events.
Use the Titanium SDK API addEventListener, removeEventListener and fireEvent methods instead.
Previously, Alloy View proxies and Controllers could use the Backbone Events API.
For Alloy Collection and Model objects, use the Backbone Events API not the Titanium SDK event listener API. This has not changed from previous versions of Alloy.
Model-view binding with the Ti.UI.View proxy should be considered experimental. On the iOS platform, the view items are not being repopulated correctly. To follow this issue, see ALOY-485.
Model-view binding with TableViews works fine and does not suffer from any known issues.
For more information, see the Alloy Data Binding guide.
If you created a custom sync adapter, the order of the passed parameters of the
module.exports.sync method
has changed to match the Backbone.sync method.
Prior to 1.0.0, the order was:
module.exports.sync(model, method, options)
For 1.0.0 and later, the order is now:
module.exports.sync(method, model, options)
To update your custom sync adapter, just switch the order of the method and model arguments.
Additionally, both the module.exports.beforeModelCreate and module.exports.afterModelCreate
methods accept an additional passed parameter--the name of the model file.
Prior to 1.0.0, the methods were:
module.exports.beforeModelCreate(config)
module.exports.afterModelCreate(Model)
For 1.0.0 and later, the methods are:
module.exports.beforeModelCreate(config, name)
module.exports.afterModelCreate(Model, name)
The previous sql sync adapter has been replaced with the sql_new sync adapter as mentioned in
release 0.3.5.
If you have a model that uses the sql sync adapter from Alloy 0.3.6 and before, you need to
migrate
your data to the new table schema of the Alloy 1.0.0 SQLite sync adapter.
First, manually remove the following files from your Alloy project:
- Resources/alloy.js
- Resources/alloy/sync/sql.js
Next, create a one-time migration file to transfer your model data to the new database schema.
Adapt the following code for your table schema. Replace title, author and isbn
with your own specific table schema but leave id and alloy_id alone. The order of fields does matter.
This migration file creates a temporary table, copies your current data to a temporary table,
deletes the old table from the database, creates a new table, then copies your data to the new table.
migration.up = function(migrator) {
var db = migrator.db;
var table = migrator.table;
db.execute('CREATE TEMPORARY TABLE book_backup(title,author,isbn,alloy_id);')
db.execute('INSERT INTO book_backup SELECT title,author,isbn,id FROM ' + table + ';');
migrator.dropTable();
migrator.createTable({
columns: {
title:"TEXT",
author:"TEXT",
isbn:"INTEGER"
},
});
db.execute('INSERT INTO ' + table + ' SELECT title,author,isbn,alloy_id FROM book_backup;');
db.execute('DROP TABLE book_backup;');
};
migration.down = function(migrator) {
}
Run your application once to migrate your data, then remove the migration file.
Note the migrator.db object in the previous example. This object is a handle to a Ti.Database instance
to execute SQLite commands. DO NOT CLOSE THIS HANDLE OR OPEN A SECOND INSTANCE OF THE DATABASE.
This will cause fatal application errors.
See the Alloy Sync Adapters and Migrations guide for information about the new SQLite sync adapter and the new migration features.
The ti.physicalSizeCategory module has been replaced by a background module part of Titanium SDK 3.0.x.
No action is needed to migrate to the new module. However, your tiapp.xml file still references this module,
but does not affect the compilation or execution of the application. You may safely remove this reference from your
tiapp.xml file.
Previously, this module was copied to an Alloy project as part of the alloy new command
and used to determine the size of an Android device.
The following deprecated APIs have been removed in this release:
| API | Type | Notes |
|---|---|---|
Alloy.getCollection |
method | Creates a local instance of a collection. Use Alloy.createCollection instead. |
Alloy.getController |
method | Creates a local instance of a controller. Use Alloy.createController instead. |
Alloy.getModel |
method | Creates a local instance of a model. Use Alloy.createModel instead. |
Alloy.getWidget |
method | Creates a local instance of a widget. Use Alloy.createWidget instead. |
Alloy.globals |
property | Global namespace. Use Alloy.Globals instead. |
datatime.js |
builtin | Collection of functions for datetime formatting. Use moment.js instead. |
size |
XML/TSS attribute | Defines size-specific view components or styles. Use the formFactor attribute instead. |
- ALOY-343. Facilitate Alloy code completion in Studio.
- ALOY-437. Support Android fastdev.
- ALOY-475. Create test app for testing sql adapter apps with no migrations.
- ALOY-209. Remove ti.physicalSizeCategory module for Alloy 1.0.0 (TiSDK 3.0+). Fixes ALOY-188 and ALOY-134.
- ALOY-313. Use applyProperties to assign properties to Ti.Android.MenuItem in parser.
- ALOY-323. Make Alloy support only TiSDK 3.0+.
- ALOY-407. Make
alloy generate modelcalls uniform in format, regardless of adapter. Fixes ALOY-375 where models were not being generated correctly in Titanium Studio. - ALOY-429. Convert jake app runner to use new CLI.
- ALOY-454. iOS is rebuilding apps every time with new CLI.
- ALOY-455. Remove Backbone eventing from Titanium proxies. Fixes ALOY-460 where ScrollableViews displayed noticeable lagging.
- ALOY-457. Make Alloy sync adapter sync() function signature match that of Backbone.
- ALOY-473. Abort compile process with message if trying to compile Alloy 1.0+ for anything less than Titanium 3.0.
- ALOY-476. Widgets within model-bound view get bound to unexisting
$model. - ALOY-479. Fix migration processing bug.
- ALOY-480. Replace
sqladapter withsql_new. - ALOY-482. View-based collection binding not properly clearing children before repopulating.
- ALOY-486.
sqladapter does not update ID in client-side model when using AUTOINCREMENT.
- ALOY-330. Make
alloy runexecutetitanium build. Thealloy runcommand will be removed in version 1.1.0 in favor of only using thetitanium buildcommand of the Titanium CLI.
- ALOY-474. Allow extra commas in TSS files.
- Tons of sql sync adapter features and fixes
- IMPORTANT: Please read the notes on the sql_new adapter below.
- ALOY-458. The sql adapter now allows you to execute custom queries on fetch(). The models/sql_queries test app uses this, specifically in this controller file.
- ALOY-447. Alloy Model column definitions now support SQLite keywords, like PRIMARY KEY and AUTOINCREMENT. The models/sql_keywords test app shows how to use it.
- ALOY-467. idAttribute is now assignable from the model.js file's definition object. The models/sql_keywords test app, specifically this model file shows how to use it to identify which column in your table is the unique identifier for syncing between SQLite and Backbone.
- ALOY-453. Full support for up() and down() migrations in sql adapter. models/sql_keywords is also a multiple migration test app.
- ALOY-345. sql adapter databases can now be preloaded from a database file. The models/sql_preload test app shows how.
- ALOY-456. sql adapter now supports multiple SQLite databases. The model/sql_queries test app makes use of multiple SQLite databases.
- ALOY-468. Added insertRow() and deleteRow() functions to migration object. You can see these in use for prepopulating and deleting rows in this migration file of the models/sql_queries test app.
- TSS parsing and features
- ALOY-272. TSS parsing is now grammar based. Makes code assist in TiStudio possible.
- ALOY-252. Commas are now optional between top-level style objects in TSS files. Check this style file for an example.
- ALOY-452. expr() syntax has been removed from TSS files. Here is the cleaner and more powerful alternative for using runtime values in TSS files.
- ALOY-284. Titanium constants can now be used as XML attributes in markup. Check this view xml file for an example.
- ALOY-191. The models/todo test app now works with all supported sync adapters (sql, properties, localStorage).
- ALOY-336. Mobileweb logs not showing up in console (related to TISTUD-2525).
- ALOY-449. Parsing state not cleaned properly when processing multiple top-level UI elements.
- ALOY-446. sql adapter should open/close between all operations (best practices).
Due to the massive amount of changes in the sql adapter, it is being introduced as "sql_new". This is the "type" you would use in your model definitions, as seen in this model from the models/sql_queries test app. The unchanged "sql" adapter still exists temporarily for compatibility.
All freshly built apps will work with the sql_new adapter, including all the sql ones in the test/apps/models folder in the repo. There may be conflicts, though, if you attempt to just drop the sql_new adapter on an app that has been previously using the old sql adapter. This is because sql_new uses a different, smarter, less invasive means of identifying the unique id of your sql records, adding an "alloy_id" column only if absolutely necessary. If you can delete your existing sql storage and just rebuild it, then all you need to do is delete and then you can start using the sql_new adapter. If not, we'll have a migration guide soon.
One final important note is that the old sql adapter will be replaced with sql_new when Alloy 1.0.0 is released, tentatively scheduled for mid-February. This'll give you a month to try it out and migrate data if necessary. Any questions or concerns, hit me up at the google group.
- ALOY-432. Added $.destroy() function to all controllers. When using model/collection binding in a controller, you MUST call this when closing a controller to prevent potential memory leaks. This is especially true if your binding makes references to global models/collections. More detailed documentation on this point will be added to the Alloy Data Binding Guide very soon. (TEST APP)
- ALOY-394. Support collection binding on Views, allowing for arbitrary component repetition. (TEST APP)
- ALOY-103. Support model binding of models to discrete properties on UI components. (TEST APP)
- ALOY-382, ALOY-383. Support in markup for proxy properties, like rightNavButton, leftNavButton, titleControl, etc... (TEST APP)
- ALOY-387, ALOY-388. Support view (XML) and controller (JS) code completion in Titanium Studio.
- ALOY-421. Add moment.js as builtin. Deprecates datetime.s builtin.
- ALOY-342. Support '--platform' option with 'alloy generate' command to create platform-specific views and controllers.
- ALOY-359, ALOY-423. Improve buttongrid widget and fix a memory leak.
- ALOY-361. Fix a bug with style prioritization as it relates to the formFactor attribute.
- ALOY-420. Refactor TableView parser to allow model-bound tables to use proxy properties.
- ALOY-430. Collection binding now responds to the Backbone "reset" event.
- ALOY-433. Removed "unreachable code" warning in production Android builds.
- ALOY-436. Alloy compile failures will now abort the Titanium build process, as expected, with the Titanium 3.0+ SDK.
- ALOY-438. Fixed bug where the Backbone off() function on Titanium proxies created from markup was not working.
-
ALOY-104. Enable Model-View binding on TableViews. For more information, see the basic tableview_binding test app or the slightly more complete todo_binding sample app which shows how to do data filtering and transformations on bound data.
NOTE: This is brand new stuff with lots more functionality coming, so any feedback on the current state is very welcome. It's best to let us know at the Alloy google group.
-
ALOY-312. Update Underscore.js to version 1.4.2 and Backbone.js to minified production 0.9.2 version.
-
ALOY-373, ALOY-379. Add Collection tag in markup to create a singleton or instance(s) of a collection.
-
ALOY-390, ALOY-391. Add Model tag in markup to create a singleton or instance(s) of a model.
-
ALOY-396, ALOY-397, ALOY-156. Add completion callback to all methods in the animation.js builtin library.
- ALOY-311. Improve Ti.UI.Android.MenuItem parser.
- ALOY-370. Fix ability to assign functions with variable assigned functions in controllers.
- ALOY-376. Improve handling of Ti.Android.Menu component.
- ALOY-393. (Re-)enable optimizer.js as part of runtime JavaScript file optimization.
- ALOY-403. Improve Alloy.Collection and Alloy.Model code optimization.
- ALOY-417. Improve properties adapter.
- ALOY-401. Deprecate Alloy.globals; use Alloy.Globals instead.
- ALOY-353. Support all Backbone eventing in Titanium proxies, on(), off(), trigger(). Fixed multiple event firing bug with on().
- ALOY-355. Improve path handling in compiler plugin for OS X.
- ALOY-356. Remove string builtin dependency to shorten compilation time.
- ALOY-365. Add Alloy.globals namespace for global context.
- ALOY-380. Create app/alloy.js file automatically for all new projects.
- ALOY-192. Add to-do sample application. Code is available on github.
- ALOY-337. Support themes to change the appearance of the entire GUI by customizing styles and assets. For more information, see:
- ALOY-306. Support platform, formFactor, and inline event attributes with abstract types in markup.
- ALOY-340. Fix Android "too deep recursion while parsing" error with Rhino runtime.
- ALOY-341. Improve adapter-backbone processing.
- ALOY-352. Fix SQL adapter to work if no migrations are present.
- ALOY-354. Fix "alloy generate jmk" command.
- Removed node-appc dependency.
- Added Alloy splash screens and icons
- Updated widgets, added new button-grid widget.
- Ti.UI.OptionDialog markup parser added. Check out this link for a test app and usage: https://github.com/tidev/alloy/tree/master/test/apps/ui/optiondialog
- You can get the Alloy version at runtime now with
Alloy.version - Tightened up XML ID restrictions. As an enforced best practice, no reserved JS words as IDs. If you try to, you'll get a compile time error message.
- Revamp of code processing, better organized, more efficient. It's all under the hood, you shouldn't notice, other than compiles might be faster.
- Quick fix to error output in compiler plugin.py
- Some minor cleanup in the test apps