jlkalberer / appcelerator-mvc Goto Github PK

Hi there,

Today I was testing your MVC framework but doesn't seems to work on the mobiles simulators.
On the android it crashes when i press "create Account".
On the iPhone/iPad after clicking "create Account" and when I click it back, I can't go to back to the create account view.

Is this framework still in alpha or beta version?

I recently discovered the XML UI module, which is a really cool way to define the app's UI. I think it would be a great addition to your (already brilliant) MVC framework, adding even more separation of concerns (view layout and view logic).

Imagine for example in /app/views/Home/, having a Default.xml file that is automagically picked up and rendered when the view is processed. The resulting UI components would then be exposed to the view function (Mvc.Views.Home.Default) as a ui argument, and one would then only have to deal with events and other logic.

The module isn't free, so I guess it can't be included in your framework, but just having support for this would be great.

This issue originates from a discussion over at John Kalberer's website (http://johnkalberer.com/2011/09/13/appcelerator-mvc-routing/#comment-62)

Having a way to call controller_a.action_a from within the code of controller_b.action_b would be very useful.

Hi,

first of all, great MVC structure, I've been using it for a while now. I was wondering if you are planning to proceed with the commonJS version of this "library". I've been looking through the 1.1 but that's full of bugs/unfinished code..

Need a clean way to allow developers to make webservice or other types of requests. This should allow for a 'loading' screen of some sort and then a refresh when the requested data arrives.

Hi John,

Last week you posted an updated mvc.js, based on our discussion at

http://johnkalberer.com/2011/09/13/appcelerator-mvc-routing/#comment-69

This allowed for actions to be called from within an action in a controller's code. Perfect for our purposes.

However, after successfully calling and executing the action, the framework somehow proceeds to call the default routed action as well, in the background. I know it's the default, catch-all action, since I changed that value in the app.js a couple of times in my tests prior to this post. Each time, the correct action would be called, then followed up by the default action.

That default action call goes on in the background somehow, not replacing the contents of the screen. An alert snuck away in the default action's code does get shown however.

For now I'm just making the default action something harmless, but of course this is no solution.

Any idea on where the routing might go wrong? My understanding of mvc.js is insufficient to go digging in it myself.

I'd be happy to offer you more information or do some more testing though. Let me know what to do.