You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Richard Lewis-Shell (JIRA)" <ta...@jakarta.apache.org> on 2005/05/27 08:30:53 UTC

[jira] Commented: (TAPESTRY-336) Change default binding of "tag" parameter in Submit component to "literal"

     [ http://issues.apache.org/jira/browse/TAPESTRY-336?page=comments#action_66425 ]
     
Richard Lewis-Shell commented on TAPESTRY-336:
----------------------------------------------

I am not sure this is a good idea.  All the time of time I have used tag I've used it to select a real object, not just a String.  Just me?

> Change default binding of "tag" parameter in Submit component to "literal"
> --------------------------------------------------------------------------
>
>          Key: TAPESTRY-336
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-336
>      Project: Tapestry
>         Type: Improvement
>   Components: Framework
>     Versions: 4.0
>     Reporter: Paul Ferraro
>     Priority: Minor

>
> The default binding of the "tag" parameter in the Submit component should be changed from "ognl" to "literal" since it is usually bound to a literal string.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Re: [jira] Commented: (TAPESTRY-336) Change default binding of "tag" parameter in Submit component to "literal"

Posted by Erik Hatcher <er...@ehatchersolutions.com>.
It's in Howard's hands on whether this should be changed back to  
always being a default of literal.  After seeing the confusion it has  
already caused, it seems literal across the board is worth reverting  
back to.  But either way is fine with me.

     Erik

On May 27, 2005, at 3:30 PM, Howard Lewis Ship wrote:

> In many cases, the default-binding should not be specified; that way
> it will indicate a literal in templates and an OGNL expression in
> specifications.
>
> I *really* like this style of development, but it is perfectly
> acceptible to always use an ognl: prefix as well.  It's kind of like
> people who always use this.  in front of every instance variable name.
>
>
> On 5/27/05, Paul Ferraro <pm...@columbia.edu> wrote:
>
>> I added this issue in response to a problem a user encountered
>> converting from 3.0 to 4.0.  People seemed surprised that the tag
>> parameter expected an ognl expression and not a literal.  I think the
>> larger issue is that users are finding default bindings to be a  
>> source
>> of confusion.  Especially since every parameter in 3.0, including
>> informal ones, were literal unless otherwise indicated.  Some  
>> users have
>> taken to *always* using a binding prefix - so it appears that this
>> feature is not entirely successful since it's intent was to save
>> keystrokes.  Thoughts?
>>
>> Paul
>>
>> Richard Lewis-Shell (JIRA) wrote:
>>
>>
>>>     [ http://issues.apache.org/jira/browse/TAPESTRY-336? 
>>> page=comments#action_66425 ]
>>>
>>> Richard Lewis-Shell commented on TAPESTRY-336:
>>> ----------------------------------------------
>>>
>>> I am not sure this is a good idea.  All the time of time I have  
>>> used tag I've used it to select a real object, not just a  
>>> String.  Just me?
>>>
>>>
>>>
>>>
>>>> Change default binding of "tag" parameter in Submit component to  
>>>> "literal"
>>>> ------------------------------------------------------------------- 
>>>> -------
>>>>
>>>>         Key: TAPESTRY-336
>>>>         URL: http://issues.apache.org/jira/browse/TAPESTRY-336
>>>>     Project: Tapestry
>>>>        Type: Improvement
>>>>  Components: Framework
>>>>    Versions: 4.0
>>>>    Reporter: Paul Ferraro
>>>>    Priority: Minor
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>> The default binding of the "tag" parameter in the Submit  
>>>> component should be changed from "ognl" to "literal" since it is  
>>>> usually bound to a literal string.
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>>
>>
>>
>
>
> -- 
> 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: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Re: [jira] Commented: (TAPESTRY-336) Change default binding of "tag" parameter in Submit component to "literal"

Posted by Howard Lewis Ship <hl...@gmail.com>.
In many cases, the default-binding should not be specified; that way
it will indicate a literal in templates and an OGNL expression in
specifications.

I *really* like this style of development, but it is perfectly
acceptible to always use an ognl: prefix as well.  It's kind of like
people who always use this.  in front of every instance variable name.


On 5/27/05, Paul Ferraro <pm...@columbia.edu> wrote:
> I added this issue in response to a problem a user encountered
> converting from 3.0 to 4.0.  People seemed surprised that the tag
> parameter expected an ognl expression and not a literal.  I think the
> larger issue is that users are finding default bindings to be a source
> of confusion.  Especially since every parameter in 3.0, including
> informal ones, were literal unless otherwise indicated.  Some users have
> taken to *always* using a binding prefix - so it appears that this
> feature is not entirely successful since it's intent was to save
> keystrokes.  Thoughts?
> 
> Paul
> 
> Richard Lewis-Shell (JIRA) wrote:
> 
> >     [ http://issues.apache.org/jira/browse/TAPESTRY-336?page=comments#action_66425 ]
> >
> >Richard Lewis-Shell commented on TAPESTRY-336:
> >----------------------------------------------
> >
> >I am not sure this is a good idea.  All the time of time I have used tag I've used it to select a real object, not just a String.  Just me?
> >
> >
> >
> >>Change default binding of "tag" parameter in Submit component to "literal"
> >>--------------------------------------------------------------------------
> >>
> >>         Key: TAPESTRY-336
> >>         URL: http://issues.apache.org/jira/browse/TAPESTRY-336
> >>     Project: Tapestry
> >>        Type: Improvement
> >>  Components: Framework
> >>    Versions: 4.0
> >>    Reporter: Paul Ferraro
> >>    Priority: Minor
> >>
> >>
> >
> >
> >
> >>The default binding of the "tag" parameter in the Submit component should be changed from "ognl" to "literal" since it is usually bound to a literal string.
> >>
> >>
> >
> >
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> 
> 


-- 
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Re: [jira] Commented: (TAPESTRY-336) Change default binding of "tag" parameter in Submit component to "literal"

Posted by Richard Lewis-Shell <rl...@mac.com>.
Perhaps it would simplify things then to make template bindings always 
use literal prefix by default, but allow specification bindings to 
default differently.  That way the template bindings would work the same 
as Tapestry 3.

Richard

Paul Ferraro wrote:
> I added this issue in response to a problem a user encountered 
> converting from 3.0 to 4.0.  People seemed surprised that the tag 
> parameter expected an ognl expression and not a literal.  I think the 
> larger issue is that users are finding default bindings to be a source 
> of confusion.  Especially since every parameter in 3.0, including 
> informal ones, were literal unless otherwise indicated.  Some users have 
> taken to *always* using a binding prefix - so it appears that this 
> feature is not entirely successful since it's intent was to save 
> keystrokes.  Thoughts?
> 
> Paul
> 
> Richard Lewis-Shell (JIRA) wrote:
> 
>>     [ 
>> http://issues.apache.org/jira/browse/TAPESTRY-336?page=comments#action_66425 
>> ]
>>     Richard Lewis-Shell commented on TAPESTRY-336:
>> ----------------------------------------------
>>
>> I am not sure this is a good idea.  All the time of time I have used 
>> tag I've used it to select a real object, not just a String.  Just me?
>>
>>  
>>
>>> Change default binding of "tag" parameter in Submit component to 
>>> "literal"
>>> -------------------------------------------------------------------------- 
>>>
>>>
>>>         Key: TAPESTRY-336
>>>         URL: http://issues.apache.org/jira/browse/TAPESTRY-336
>>>     Project: Tapestry
>>>        Type: Improvement
>>>  Components: Framework
>>>    Versions: 4.0
>>>    Reporter: Paul Ferraro
>>>    Priority: Minor
>>>   
>>
>>
>>  
>>
>>> The default binding of the "tag" parameter in the Submit component 
>>> should be changed from "ognl" to "literal" since it is usually bound 
>>> to a literal string.
>>>   
>>
>>
>>  
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Re: [jira] Commented: (TAPESTRY-336) Change default binding of "tag" parameter in Submit component to "literal"

Posted by Paul Ferraro <pm...@columbia.edu>.
I added this issue in response to a problem a user encountered 
converting from 3.0 to 4.0.  People seemed surprised that the tag 
parameter expected an ognl expression and not a literal.  I think the 
larger issue is that users are finding default bindings to be a source 
of confusion.  Especially since every parameter in 3.0, including 
informal ones, were literal unless otherwise indicated.  Some users have 
taken to *always* using a binding prefix - so it appears that this 
feature is not entirely successful since it's intent was to save 
keystrokes.  Thoughts?

Paul

Richard Lewis-Shell (JIRA) wrote:

>     [ http://issues.apache.org/jira/browse/TAPESTRY-336?page=comments#action_66425 ]
>     
>Richard Lewis-Shell commented on TAPESTRY-336:
>----------------------------------------------
>
>I am not sure this is a good idea.  All the time of time I have used tag I've used it to select a real object, not just a String.  Just me?
>
>  
>
>>Change default binding of "tag" parameter in Submit component to "literal"
>>--------------------------------------------------------------------------
>>
>>         Key: TAPESTRY-336
>>         URL: http://issues.apache.org/jira/browse/TAPESTRY-336
>>     Project: Tapestry
>>        Type: Improvement
>>  Components: Framework
>>    Versions: 4.0
>>    Reporter: Paul Ferraro
>>    Priority: Minor
>>    
>>
>
>  
>
>>The default binding of the "tag" parameter in the Submit component should be changed from "ognl" to "literal" since it is usually bound to a literal string.
>>    
>>
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org