On 10/28/05, Aaron Trevena <[EMAIL PROTECTED]> wrote: > I'd like to have a consistent API through the generic model, rather > than having the current situation where stuff works significantly > differently if you use CDBI and the huge range of odds and ends that > come with it. > > There is no reason not to put most of the Sweet stuff into an > underlying module used by the improved Model and CDBI Model, so long > as it is integrated nicely. > > The one advantage Rails has over Maypole is the seamless, polished > integration, just importing a shedload of CDBI subclasses, plugins, > etc is hardly going to come close to providing that and makes > installation harder than it needs to be with hundreds of dependancies > with their own release cycles, unpatched bugs, etc. >
I agree with Aaron. We should beef up the Model so that it is more funcitoinoal out of the box. With CDBI changing so rapidly it seems a good idea to steal Sweet rather than *use* it. One Sweet author was complainng about cdbi changes the other day. With the code under Maypoles control it will be easier to cope with CDBI changes. Are you planning on big new functionality for 2.11, Aaron or just the simple Form stuff so that Maypole works again. I guess you kind of have to have a good idea of where your going before you can add anything to the model.. cheers. ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Maypole-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/maypole-devel
