On Mon, Sep 8, 2008 at 11:25 AM, Owen Winkler <[EMAIL PROTECTED]> wrote: > I've tried a bit this morning to find the thread that explained why we > don't do it this way already, but bailed before accomplishing the task. > > Points will be awarded to those who look into it and come up with the > answer, which I know exists.
Quickly scanning, I assume yhou are talking about http://groups.google.com/group/habari-dev/browse_thread/thread/3a5bcb42582bbbb5/ Using xml file for info would still allow for extensibility of adding metadata, in fact I see it as more extensible than simply using a an array/infoobject. calling the info() method would operate exactly as it does now, returning all meta data from xml file. Also, xml could provide additional fields that are not required for "info". If we had an <info> section that data would be returned with the info call, but we could also provide other things like <postActivation><readme lang="en_US"> etc. We could also provide something like glade xml format for creating formui plugin options interface, but I don't really see much of a benefit there, just blabbing out ideas :) The downside is it requires parsing the xml file if you need this data, but during normal operation this data is only currently used in the admin plugins area. The point is to seperate the metadata from the code, which I would prefer over requiring the plugin class to be loaded. -- Matt Read http://mattread.com --~--~---------~--~----~------------~-------~--~----~ 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/habari-dev -~----------~----~----~----~------~----~------~--~---
