- Titanium-to-Alloy Guidance
- In my Titanium application, I previously loaded libraries upon startup. In organizing my patterns with MVC, do I need to organize application functionality further under namespaces within controllers?
- Are there best practices to employ within controllers for performance?
- Do I simply load controllers with a bunch of callbacks that relate to the view and let Alloy handle the linkage?
- Is there a best practice that I should use to help out Alloy for my own organization here, as I did in the standard Titanium applications?
- Coding Style Best Practices
This guide provides recommendations for writing Alloy applications. This guide supplements the existing Titanium SDK Best Practices and Recommendations guide with a primary focus on the Coding Best Practices and Style and Conventions pages.
In my Titanium application, I previously loaded libraries upon startup. In organizing my patterns with MVC, do I need to organize application functionality further under namespaces within controllers?
Not unless you want to. If you have a pre-existing set of functionality that you want to make available globally throughout your app, there is no reason to further sub-categorize it unless it serves you in terms of organization or scalability. There is nothing preventing you from requiring your pre-existing modules in all your Alloy controllers, or even making a single global reference to your module that can be referenced throughout your app. For example:
Are there best practices to employ within controllers for performance?
The same best practices that apply to traditional Titanium development still apply in the world of Alloy. In fact, everything you can do in traditional Titanium development you can do in Alloy's controllers. Use the Coding Best Practices you learned with traditional Titanium development in Alloy. That said, the best trick you can use now is taking advantage of the compiler directives to speed up runtime performance. Refer to Alloy Controllers: Conditional Code
Do I simply load controllers with a bunch of callbacks that relate to the view and let Alloy handle the linkage?
You can do this, or you can use eventing between your controllers to handle this communication. The latter is preferred as it encourages loose coupling between you controllers. For a basic example of using controller eventing to communicate between controllers, refer to the master-detail Alloy test application: https://github.com/appcelerator/alloy/tree/master/test/apps/advanced/master_detail
Is there a best practice that I should use to help out Alloy for my own organization here, as I did in the standard Titanium applications?
It depends on the size and depth of your existing organization. You need to determine if it makes sense to bend Alloy around your existing organization, or bend your existing organization around Alloy. One of the driving forces behind Alloy was a need to standardize the many disparate Titanium coding methodologies out there. In doing so, your projects will be cleaner and more in line with best practices, but also give it a familiar feel and structure that makes it easier for other developers to help and contribute.
Coding Style Best Practices
- Do not use double underscore prefixes on variables, properties, or function names (e.g.,
__foo). They are reserved for use in Alloy. If you use them, there is potential for conflicts and unexpected behavior.
- Do not declare global variables in app.js and use them in other files. Such usage is currently allowed but not recommended, and it will be deprecated in the future. Users who wish to use globals in Alloy applications can declare the following in their JS files:
As an example:
Although you can use
Ti.App.fireEvent('name') to call an event declared as
Instead of that, you can use better approaches, depending on the problem you are addressing:
- If you have the classic problem communication between a master - child screens (you need that a child event triggers something in the parent), then use the callback approach: you can pass a function to be called as a callback when needed:
- If you need to communicate between different parts of the app, then use the Backbone dispatcher approach: create a global object with Backbone capabilities. You can do either, declare it in a file and require it when needed or, more practical, create it in
alloy.jsfile to be available to all your project. Another advantage of use the Backbone approach is that you can cancel the events in any place because are global:
Note: in the first example, Alloy controllers are Backbone event dispatchers as well. So you could do also
Alloy.createController('child').on('refresh', refreshData) to get the same behavior of a callback approach but with Backbone approach, and then trigger the event when you need it.