On Wed, Jan 14, 2009 at 4:23 PM, mdipierro <[email protected]> wrote: > > The example described new functionality of web2py. Eventually most of > T2 will be replaced by web2py functionality. > > This is a request for comments before it moves from trunk (testing) to > stable (cannot be undone because of backward compatility).
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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
