Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Views and controller,
In titanium do you normally have 1 controller per view? or 1 controller per group of views?
You have a form, PageX_Detail, PageX_Confirm, and PageX_Results.
In this case would you create 3 views and 3 controllers or 3 views and 1 controller?
I think it’s best to have one controller per the group of views.
Titanium applications currently don’t typically follow a strict MVC structure (although Appcelerator is working on an MVC framework for use with Titanium called Alloy).
The most popular ways to organize Titanium applications that I’ve discovered are:
1) The Tweetanium style, where a global namespace contains application-wide functionality and a main window hosts each application view.
Or, my favorite (and the most Appcelerator-supported way),
2) The CommonJS approach and the use of
require()instead of the deprecatingTi.include()