logically, a component should be able to be used without any changes to your app code, other than the interface (calls).
How that is accomplished (directories or not) has more to do with maintenance and deployment (and upgrade) considerations. If there turn out to be practical show stoppers there, then I think code changes to core are a valid and viable consideration - its about what you gain / loose for the effort invested. - Yarko On 10/1/09, mdipierro <[email protected]> wrote: > > Logically, I think the plugin should be organized as sub-folders (in > admin) > > Physically, I am not convinced. The current mechanism only requires a > convention. If plugins where physically in a subfolder then web2py > would need major modifications to handle dispatching, bytecode > compiled applications, be able to locate models, decide order of > execution, etc. > > This would delay the project a lot and would make web2py slower. > > Massimo > > > On Oct 1, 12:42 pm, Jon Romero <[email protected]> wrote: >> I think this is awesome and it was missing from web2py. >> >> The only thing I found strange, is that you have to place the files >> inside your application in multiple places. How about creating a >> plugin directory (see Rails "vendor/plugins") where you could just >> place the whole plugin structure there (like an autonomous >> application)? I know this might make the code more complex but it >> separates plugins from your application (also easier to try many >> plugins without 'polluting your app' and it's easier to upgrade). > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
