> > HiveMind just makes me think of StarCraft. ;-) Exactly eheheh :D
On Wed, Sep 12, 2012 at 8:11 PM, Lenny Primak <lpri...@hope.nyc.ny.us>wrote: > HiveMind always had negative connotations in my mind as well. > I say de-emphasize Tapestry in Tapestry-IoC. > Just call it IoC. > > I hate Spring myself, and anything that gets people off it is a good thing > IMHO > > On Sep 12, 2012, at 1:52 PM, Daniel Jue wrote: > > > I'd say keep the same name but market the IOC more heavily, with > tutorials > > and demos (a quickstart, perhaps) of it being used in a non web app. (I > > don't think this is out there, right? If it is, it wasn't in-my-face > > enough. :-) ) A T5 IOC quickstart might work well with an Apache Shiro > > example, since that can also be used outside of a web app. > > > > I use the T5 IOC as a major selling point to using T5 as a web framework, > > because they work so well together, and I'm loving the common version > > numbering. HiveMind just makes me think of StarCraft. ;-) > > > > On Wed, Sep 12, 2012 at 12:26 PM, Howard Lewis Ship <hls...@gmail.com > >wrote: > > > >> On Wed, Sep 12, 2012 at 2:59 AM, Lance Java <lance.j...@googlemail.com> > >> wrote: > >>> I've often had a conversation like this in the workplace: > >>> > >>> colleague: Let's start a new spring project > >>> me: I hate spring, how about we use Tapestry IOC instead? > >>> colleague: Tapestry, isn't that a web framework? > >>> me: Well... yes, but Tapestry (the web framework) is build on > >> top > >>> of Tapestry IOC which can be used without the web framework > >>> colleague: Oh, I didn't know that. > >> > >> Maybe we could resurrect the HiveMind name? I always loved that name! > >> > >>> > >>> Does anyone else think that Tapestry IOC should have it's own name? > (and > >>> possibly it's own release cycle) > >> > >> HiveMind had its own release cycle; this wasn't quite a disaster, but > >> it made things much more difficult. I really like that in Tapestry you > >> don't need a cheat sheet to figure out which versions of the main > >> libraries work together: they all have the same version number. This > >> means that for some libraries that don't change from release to > >> release you have virtually identical binaries with different version > >> numbers, but that's more than acceptable to me. > >> > >>> > >>> > >>> > >>> -- > >>> View this message in context: > >> > http://tapestry.1045711.n5.nabble.com/Tapestry-IOC-Should-it-have-it-s-own-name-tp5716228.html > >>> Sent from the Tapestry - User mailing list archive at Nabble.com. > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > >>> For additional commands, e-mail: users-h...@tapestry.apache.org > >>> > >> > >> > >> > >> -- > >> Howard M. Lewis Ship > >> > >> Creator of Apache Tapestry > >> > >> The source for Tapestry training, mentoring and support. Contact me to > >> learn how I can get you up and productive in Tapestry fast! > >> > >> (971) 678-5210 > >> http://howardlewisship.com > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > >> For additional commands, e-mail: users-h...@tapestry.apache.org > >> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
