HiveMind is going to incorporate some of the same concepts as Tapestry IoC. We are actively discussing the future of HiveMind and its goals. I'm glad to hear you use HiveMind and find it very helpful to you. If you have any suggestions or features that you want in HiveMind, please shoot an email over to the HiveMind developers list for discussion (the lists have moved recently since we're going to be a top-level project soon). You can be sure that we'll be peeking over Howard's shoulder to "borrow" some of his ideas from Tapestry IoC for HiveMind! :-)
-----Original Message----- From: Benjamin Tomasini [mailto:[EMAIL PROTECTED] Sent: Sunday, July 30, 2006 8:37 PM To: [email protected] Subject: Tapestry IoC as a general purpose container I have been using HiveMind now for quite a while and have come to depend on it quite heavily on many projects - some web apps, some not. It's features have very much improved the quality and modularity of my code. What would prevent a user from employing Tapestry IoC as a general purpose container like HiveMind? Would there be any benefit to building one monolithic Tapestry jar and a set of segmented jars (something Spring does) for more targeted use? Or why not keep Tapestry a single project with sub-modules for IoC and the Web framework? Alternatively, what about merging Tapestry IoC and HiveMind at some later date? It could remain as HiveMind, or it could take on the Tapestry IoC name. The conversations on this list indicate that key principals of both projects intend to keep some degree of parity anyway. Ben --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
