Eclipse obviously has better tool support ... it has the PDE. Eclipse doesn't include the <rules> concept, the ability to convert contributed XML directly into useable Java objects. In Eclipse, your plugin gets, effectively, a light-weight DOM to walk; in HiveMind you get an array of objects. Biggest difference is that HiveMind includes a services model; Eclipse has nothing like this beyond its interesting approach to classloading and plugin activation. Participation: subscribe to the commons dev mailing list, post with "[HIveMind]" in the list. HiveMind is reorganizing into three sub-projects: framework contains the core framework; library contains standard (well understood, well tested, well documented, generally useful) services. contrib will be created soon, it's a kind of sandbox for new stuff.
-- Howard M. Lewis Ship Creator, Tapestry: Java Web Components http://jakarta.apache.org/tapestry http://jakarta.apache.org/commons/sandbox/hivemind/ http://javatapestry.blogspot.com <http://javatapestry.blogspot.com/> -----Original Message----- From: Arias Juan [mailto:[EMAIL PROTECTED] Sent: Sunday, September 21, 2003 2:15 PM To: [EMAIL PROTECTED] Subject: Hello Howard, I have passed this evening of Sunday looking around your project and I only write to you to congratulate you... If you decide to build a community, you have a volunteer... in next days I'll study it in more depth for see the application in one project I'm working (a plugin based framework with integration with WebStart) Only one question, what's the difference of your approximation with the eclipse framework one? Nothing more, good work, and sorry for my English... (I'm from Spain)... See you... Juan Arias Computer Engeneer of Izar Ferrol _____ Yahoo! Messenger <http://es.rd.yahoo.com/mail_es/tagline/messenger/*http://es.messenger.yahoo.com/> Nueva versi�n: Super Webcam, voz, caritas animadas, y m�s �Gratis!
