I am -1 on any further changes to the behavior of the PropertyTag (after the id attribute change) and any new tags that duplicate the functionality of the PropertyTag. These reasons have been explained ad nauseam on this list. If you are unfamiliar with the argument, please search the archives.

For those unfamiliar with what all this +1/-1 stuff means, a -1 is a veto. To get something approved past a veto you will have convince the person vetoing to change his/her vote.

-Maurice


On Monday, November 11, 2002, at 06:24 AM, boxed wrote:

Attached to this email I have the code for the following tags: ContextTag,
FocusTag, PopTag, PushTag and PrintTag. These do what PropertyTag does today
and more:

<ww:context id="foo" value="bar"/> pulls "bar" from the valuestack and puts
it into the page context as "foo".

<ww:focus value="foo"></ww:focus> moves the focus to "foo" within the body
of the tag (push at start of tag, and pop at end of tag).

<ww:push value="foo"/> pushes foo to the top of the valuestack.

<ww:pop/> pops the top value off the valuestack

<ww:print value="foo"/> fetches "foo" and prints it.

You will note that the code is way cleaner, that the resulting tags are more
flexible and most importantly, the entire documentation for them is pretty
much what I wrote above. This last point is the most important since the
full page and confusing document on property tag that we have today is no
user friendly.

// Anders Hovmöller
<ContextTag.java><FocusTag.java><PopTag.java><PrintTag.java><PushTag.ja va>

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork


Reply via email to