Hi, I’ve been investigating your library, just wondering if there’s a way to break the view’s reliance on the model where the view’s outgoing events are concerned?
For example, in the login tutorial you have, the view calls “SuperWebsite.gi.runEvent(new LoginEvent(email.text));”. Shouldn’t it be the controller’s responsibility which type of event is called? Or am I misunderstanding the way it’s supposed to be used?
For example, maybe I want the same view somewhere else in my app to send a “ChangeTitleEvent”, with the same email.text parameter. This means I would have to have two separate views classes (one calling LoginEvent and one calling ChangeTitleEvent), instead of one view and two actions.
June 14th, 2009 at 9:14 am
I’ll definitely be checking flashmvc out sometime this week and leave my thoughts here once I get to play with it.
October 1st, 2009 at 6:44 pm
Hi, I’ve been investigating your library, just wondering if there’s a way to break the view’s reliance on the model where the view’s outgoing events are concerned?
For example, in the login tutorial you have, the view calls “SuperWebsite.gi.runEvent(new LoginEvent(email.text));”. Shouldn’t it be the controller’s responsibility which type of event is called? Or am I misunderstanding the way it’s supposed to be used?
For example, maybe I want the same view somewhere else in my app to send a “ChangeTitleEvent”, with the same email.text parameter. This means I would have to have two separate views classes (one calling LoginEvent and one calling ChangeTitleEvent), instead of one view and two actions.