Actually we have some things that you can use outsite web2py like DAL and template system. We don't have a roadmap to decouple other things but yes, it is in or mind (web2py developers) and we'll be implementing decoupling of other modules as soon as possible. :-)
On 12/9/09, snfctech <[email protected]> wrote: > Someone posed a good question about framework decoupling on > comp.lang.python, here: > > http://groups.google.com/group/comp.lang.python/browse_thread/thread/f04940f9d4b136bc?hl=en > > The author is coming from a Flex+Java paradigm and the arguments he/ > she raises for decoupling are: > > - better scalability > - easier to test > - easier to maintain > - easier to re-use code for different applications > - easier to migrate/port (e.g. to a different framework) > > These are all nice things. I guess you could argue against the first > three that you didn't need to decouple your code for very good > scalability, testability and maintainability - but decoupling is > probably a good idea for reuse and in case you ever want to use a > different framework. > > Was this development pattern considered during the design of web2py? > What would the web2py response be to a post like the one above where > someone is looking for a decoupled framework for the reasons I > mentioned? > > -- > > You received this message because you are subscribed to the Google Groups > "web2py-users" 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. > > > -- Álvaro Justen Peta5 - Nós fazemos TV digital http://www.peta5.com.br/ 21. 3021-6001 / 9898-0141 -- You received this message because you are subscribed to the Google Groups "web2py-users" 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.
