I believe in choosing a strong name and letting it become assocaiated with the concept of the product. At one point (remember, this was about six years ago), I toyed with the idea of naming components "Weavers" and so forth, but abandoned that as just stupid.
I once had someone ask me at a NFJS, "What does 'TAPESTRY' stand for?" ... took me a moment to understand he thought it was an acronym. "Transation APllication Expression System, for, uh ... okay, it's not an acronym". On 12/21/05, Nils Zonneveld <[EMAIL PROTECTED]> wrote: > Vinicius Carvalho wrote: > > >Sorry about this, but could not found on the wiki. Why Tapestry? I mean the > >name ;) > > > >Regards > > > > > > > I guess because with a tapestry things are woven into each other. A > tapestry of objects, if you like. But this is just a guess of course :-) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
