>> niphlod/w2p_timezone_plugin Nice. But I was solving this for a customer in a Cherrypy application.
That leads me to one thing. I see you realy use the plugin_... name convention. Do you think is it good idea to follow this recommendation? Does it not lead to problems? I understand that controllers and views must be designed especially for web2py and no problem if they have special names like plugin_... But if they import modules, which sometimes could be usefull for whole Python infrastructure, not exactly for Web2py, wouldn't be nice if modules inside the plugin can have any name to maintain them easier? I can imagine a system, where plugin editor and plugin packaging manager - will analyze starting rows from plugin_.....py file (from the controller), - handle import commands, skip empty lines + comment lines + assign commands (containing =) and break when an other command will occur (usually def...), - for 'import <module>' and 'from <module> import' commands they will check, if the module is located as <app>/modules/<module>.py - and if yes, then handle the <module> as part of the plugin What do you think? Could be such solution better or worse as current state? (yes..it's different topic) Dne pátek 20. února 2015 11:14:56 UTC+1 Niphlod napsal(a): > > good. you're doing exactly this > <https://github.com/niphlod/w2p_timezone_plugin/blob/master/README.md> > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
