Also what has to be considered is not just the immediate name, but what it takes from the pool of names that can be better used in the future, and its clarity of what it does along side future names & functionality. I feel that verbatim and literal have more of a place possibly defining rules someplace else, and in the futre will become esoteric and developers will have to hunt down docco for their meaning more often.
freetext - For the reason above & the same reason that Tom said not to. It says "do what you want"... and that add's its own nature of "there is power here, but don't be stupid" and still has the open & texty feel of it. custom - A close second. Almost as cool as freetext verbatim & literal - for my money they just state more as to how something is handled and not describing what it is that it provides. All attributes of a tag are taken as "literal". Just a little too ambiguous. freetext is for me. Most important is that when one is picked... one is picked. Arron. Will Jaynes wrote: >[+1] literal > >----- Original Message ----- >From: "Ted Husted" <[EMAIL PROTECTED]> >To: "Struts Developers List" <[EMAIL PROTECTED]> >Sent: Monday, December 10, 2001 6:02 AM >Subject: Re: Freetext attribute for all tags... > > >>Is freetext all right with everyone, or should we use something like >> >>literal >> >>custom >> >>or >> >>verbatim >> >>It's just that I feel we have not paid close enough attention to the >>naming of things in the past, and we might want "measure twice" before >>we document this. >> >> >>-- Ted Husted, Husted dot Com, Fairport NY USA. >>-- Custom Software ~ Technical Services. >>-- Tel +1 716 737-3463 >>-- http://www.husted.com/struts/ >> >>-- >>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> >> > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>