From: <ger...@gm...> - 2009-03-21 14:50:58
|
But that's just my point. An end user has no reason to know what the underlying libraries are for or even that they exist. He needs to know about the plugins that are available that he can use directly. The current status display does that nicely. Consider the plugin status display for Firefox, for example. You see what is installed and what sorts of things each plugin handles but you cannot see what libraries they use. Same thing, basically. for other programs like gimp or gedit or many others. On the other hand, I think I like Benny's idea: Move the class so its part of the doc structure and make other HTML classes derive from it. It would no longer be a plugin that way but would perhaps have greater utility. On Mar 21, 2009 9:44am, Brian Matherly <br...@gr...> wrote: > Gerald, > > Moving it is no problem. Registering it? Not so sure. I > > see a few > > other libraries there but I'm not sure what the value > > is except to > > developers. > All plugins should be registered so that when users look in the plugin > status window, they are able to know the purpose of each plugin. > ~Brian |