+1 for this idea. Standardising how plug-ins are done (my personal preference would be to add functionality to the admin app to allow the management of plug-ins) will make adding T2 and other layers on top of the core much easier to do.
I believe decoupling in this case is the preferred route (due to backwards compatibility issues causing the API to freeze and innovation to suffer). Paul D. Eden On Wed, Jan 14, 2009 at 8:36 AM, Markus Gritsch <[email protected]> > > > Can you explain what's the motivation behind this? IMO a small core > which can optionally be extended with T2 functionality is preferrable. > jQuery is very successful using this approach. > > Advantages: > * Easier to learn web2py because one gets not overwhelmed with > functionality. > * T2 can be improved, without the hard web2py backwards compatibility > promise. > > Maybe web2py can ship by default with T2 as an installed > application/plugin like 'admin' and 'welcome' does. > > Kind regards, > Markus > > -- Best Regards, Paul Eden "...and a little looking out for the other guy too." - Mr. Smith --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
