I think we should do everything.. as I was saying, we've already run into FilterChain as a conflict with phing. Since this will cause major breakage with existing apps, I think it's best to fix everything all at once, rather than doing only some now and then discovering the need to do more later on down the road. --Bob
On 7/5/05, David Zülke <[EMAIL PROTECTED]> wrote: > The question is: which classes do we rename and which don't we rename? > Obviously, core stuff gets an "Agavi" prefix, so we end up with AgaviUser, > AgaviController etc. > But... AgaviExecutionFilter? Or ExecutionFilter? AgaviSecurityFilter? > AgaviBasicSecurityFilter? AgaviFrontWebController? > > We need to discuss/clarify that. After that, it's a piece of cake (luckily > we haven't reached 1.0 yet, so we can break BC at will). > > - David > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > Behalf Of Bob Zoller > > Sent: Saturday, July 02, 2005 8:03 PM > > To: Agavi Development > > Subject: Re: Class Names (was: RE: [agavi-dev] Logging opinions needed) > > > > +1 for me.. a small sed script should do the trick ;) Does anyone > > else have reservations about doing this at this point? > > --Bob > > > > On 7/2/05, David Zülke <[EMAIL PROTECTED]> wrote: > > > I can do so, shouldn't be a big deal. Basically just a find/replace on > > all > > > files. People will have to modify their code a lot tho (class MyModel > > > extends AgaviModel etc) > > > > > > - David > > > > > > > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > On > > > > Behalf Of Bob Zoller > > > > Sent: Saturday, July 02, 2005 2:04 AM > > > > To: Agavi Development > > > > Subject: Re: Class Names (was: RE: [agavi-dev] Logging opinions > > needed) > > > > > > > > Yeah.. we already ran into it when writing tests, because FilterChain > > > > is defined by both phing and Agavi ;) Definitely a big +1 for > > > > renaming our base objects... I guess someone should compile a list on > > > > the wiki? ;) > > > > --Bob > > > > > > > > On 7/1/05, David Zülke <[EMAIL PROTECTED]> wrote: > > > > > > I'll rename it AgaviMessage (avoid stepping on toes) > > > > > > > > > > Hmm right; however, that would break with the existing naming > > > > "conventions" > > > > > we have right now. Except of AgaviObject, all classes don't carry > > > > "Agavi" in > > > > > their names. Maybe we should change that; it would lead to way less > > > > naming > > > > > conflicts anyway (think of class "User" for example). > > > > > > > > > > - David > > > > > > > > > > > > > > > _______________________________________________ > > > > > 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 > > > > > _______________________________________________ > > 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
