Hi,
Bob Zoller <[EMAIL PROTECTED]> words
on 08.09.2005 - 19:33 (-0500 Zulu-Time):
> I've discussed the "individual controllers" idea before.. this is the
> way Rails does it - where each module essentially has one class (a
> "controller") that is made up of methods - one for each action in your
> module. So instead of one execute() method per Action class, you'd
> have a class with lots of methods like actionIndex() and actionList()
> and actionEdit(), etc...
Yeah something like that would be nice. But actually I didn't really
think about a Class with lot's of methodes, instead i though about a
class the dynamically loads other classes and execute them
(Command-Pattern). So you can handle each request in your own class.
> Like you (and a number of us), I have begun to feel bloat in having an
> Action class for every action in every module. Ideally something
> similar could be done with views. These were things that I was
> wanting to tackle in a post 1.0 release, but now that Agavi as we know
> it may not have a post 1.0 release, I'm not sure if/when it will get
> addressed.
>
> illusina's vision of Mojavi 4 may deal with this shortcoming though...
Just to know for me. How looks the development milestones for agavi?
Do we integrate mojavi 4?
Will there be big changes by switching from mojavi 3 to 4 and
is there a 'date' where this should happen?
For me as a user is that interessting, cause i have to plan how to
develop my application and if there are big changes in the underlying
MVC it's additional work to adapt the application-code.
But apart from that i am for every change, that makes the framework
easier to understand an work :)
Regards Erik
--
J. Erik Heinz
Keyboard-samuraing in process
_______________________________________________
agavi-dev mailing list
[email protected]
http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
