Lets merge that stuff, right. I would like to sync in my View branch, tho. Will test it this weekend.
- David P.S: Mike's globalization stuff for 0.10? yes/no? > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Bob Zoller > Sent: Friday, September 09, 2005 5:45 PM > To: Mike Vincent; Agavi Development > Subject: Re: [agavi-dev] get a central controller? > > I'm all for rolling 0.10.0 now, I think that's a great idea. Everyone > ok with me merging in the Logging bits I've got as well? > --Bob > > On 9/9/05, Mike Vincent <[EMAIL PROTECTED]> wrote: > > On 9/9/05, J. Erik Heinz <[EMAIL PROTECTED]> wrote: > > > 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. > > > > It doesnt really do much to address the main issue, though. Does it? > > > > ..TOO MANY DAYUM FILES :) > > > > Consolidate the actions as methods off a single class and the number of > > files one needs to maintain is reduced considerably. > > > > > > 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 :) > > > > > > > I cant speak for everyone, but I'm not even thinking about M4. > > > > I'm thinking we need to roll a 0.10.0.. NOW, there's been an enourmous > > amount of change since the .9 release. After which, we continue our > efforts > > towards a 1.0 release which may or may not be preceeded by an 0.11.0 > dunno > > at this point. > > > > > > > > -Mike > > > > _______________________________________________ > > agavi-dev mailing list > > [email protected] > > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev > > > > > > > _______________________________________________ > agavi-dev mailing list > [email protected] > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
