From: Joanna C. <jo...@th...> - 2011-01-23 20:35:43
|
Hi, I would like to second the notion of using modules - definitely you'd otherwise end up with too many actions per controller to be manageable. Also what were you thinking of using for db abstraction? Zend, Doctrine, something else? Regards, Joanna On 23 January 2011 19:04, Udo Schochtert <u.s...@gm...> wrote: > hello, > > not quite sure if a starting point could be this (just some ideas) > > - define whether or not to use modules > note: in my opinion there should be modules. > - define the modules/controllers/actions (naming) to have a rough > structure > - assign legacy code to the module/controller/action where it would be > handled > - define the sequence of rewriting legacy code functionalities > > best, udo > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > |