Jeremy Lowery wrote:Interfaces could formalize the API of components for plug-in play functionality. I've been looking at the Zope3 source a bit and this is going to be their entire new architecture logic. <<For the benefit of our readers : Zope definition of Component : http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/Component Interfaces documentation : http://www.zope.org/Wikis/Interfaces/InterfaceUserDocumentation As I said elsewhere in this thread, Interfaces have a lot of benefits but they add a lot more pipework to the framework - first define the Interface then create classes that implement that interface (2x the typing+). The benefits are worthwhile but the resultant code feels more Java-ish. Do we want to start thinking about the interface(s) for Plugins?
I like this idea. On my first project I started with UserKit, but needed postgreSQL support and wound up writing my own system, but I initially tried to maintain the interface setup by UserKit. If there was a formal interface spec I would not have just astared adding functions into the userManager when I wanted to.
This will also solve the some of the new user problems.
-Aaron
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
