On Oct 22, 3:08 pm, Yarko Tymciurak <[email protected]> wrote: > On Thu, Oct 22, 2009 at 10:54 AM, mdipierro <[email protected]> wrote: > > > Yarko, at least send us a document explaining how you think this > > should work. An example of API, an example of admin interaction with > > plugins. > > NO, actually I want you to specify what you want (it's your project) - I am > just reviewing and telling you what doesn't look like it fits, or is > incongruent, will not work well, or will work counter to your stated > objectives (If I define it, it will be my plugin, and I have other > priorities now).
I implemented what I want. I am very happy with it. ;-) This is still at the RFC status because I am asking users to tell me if something is wrong. Specifically what do you want to do that you cannot do with what I am proposing. I envision a next stage and I have not really given much thought to that. I.e. using the plugin system to build one ore more CMS. This requires plugins to be discoverable, self documented, and have hooks for the CMS. I do not think there will be a single CMS. Some plugins may be specific of a certain type of CMS. This will require a plugin manifest with some standard structure/syntax. It should be the CMS app to read the plugin manifests. This should not be a web2py feature. web2py is not a CMS. This in my view is a separate discussion and I do not know what I want. I only know people seems to be happy with Drupal and perhaps we should take some inspiration from it. Massimo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
