It's only a thought but can't the syntax be changed so that any run
time overhead by looking something up from the stack can be avoided
based on syntax of the string? I mean ... by all means add the support
in WebWorkTagSupport to look all things up on the stack but allow the
user to choose whe
ilto:[EMAIL PROTECTED]]
> Sent: Friday, January 31, 2003 8:49 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [OS-webwork] Parameters and the ValueStack
>
>
> I'm talking about webwork 2.0. Should everything be lookedup
> on the stack? Pat's TextfieldTag currently doesn&#
I'm talking about webwork 2.0. Should everything be lookedup on the stack?
Pat's TextfieldTag currently doesn't. I just want some clear standard to
be decided upon.
--Erik
On Sat, 1 Feb 2003, Scott Farquhar wrote:
> Erik,
>
> Which values are not looked up on the stack? I know that "id" isn't (
Erik,
Which values are not looked up on the stack? I know that "id" isn't (in
iterator tag). Anything else?
I don't think that this can be fixed in current webwork, as we would not
be able to maintain backwards compatibility? You should add this as a
feature to webwork 2.0.
Cheers,
Scott
The biggest complaint that I hear about the ww taglib is the when to and
when not to enclose params in single quotes. Currently, the best method
for figuring this out seems to be to check the source to see if the param
is ever looked up on the stack. Could there be some standard agreement
made as t
