I think we'd need to hold on to Plugin for a little Longer. We may get to a point were we need something implemented in plugins only. If we switch now and need that in the future, we'd need to break plugins again. This sure is a possibility.
On Tue, Jun 2, 2009 at 2:23 PM, rick c <[email protected]> wrote: > > Since info() is the only thing left in Plugin at the moment, am I > correct in concluding this means that Plugin can go away completely? > Which would also mean that all plugins should derive from Pluggable, > and also need rewritten? > > Rick > > On Jun 2, 1:11 am, Owen Winkler <[email protected]> wrote: > > Hi folks. > > > > We need to move the Info method of Plugin and Theme up to Pluggable so > > that they use the same stuff. As a result, we need to form the XML used > > to define plugin/theme info a little better. As a result of changing > > the format, all existing themes will explode. > > > > This has to be done, because the areas that are published for a theme > > need to go in that XML, and the XML needs to be stable. > > > > I want to do this this week. I can publish a schema for the XML on the > > wiki (Relax?), and others can look it over. > > > > The schema should allow for themes and plugins to use the same format of > > xml data, since they're both Pluggable. Soon after the info method of > > plugins would go away to be replaced by the Pluggable info method, > > meaning plugins wouldn't need to execute any more to get their infos. > > It would just use the xml file instead (although the plugin should still > > be sandboxed so it's known to work). > > > > Your consideration is appreciated. > > > > Owen > > > -- Ali B. / dmondark http://awhitebox.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 -~----------~----~----~----~------~----~------~--~---
