You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Jesse Kuhnert <jk...@gmail.com> on 2007/05/02 03:46:57 UTC
[vote] remove renderTags default of true for @If/@Else? (tapestry 4.1.2 )
This is sort of related to
https://issues.apache.org/jira/browse/TAPESTRY-1431 .
I think it was a mistake to have renderTags default to true for the If/Else
components but not For . ...
I'm thinking I'd like to have it default to false for these components
before we release 4.1.2 but as it will potentially cause work for people if
they've been relying on this new behavior I thought it'd be good to see what
everyone else thinks before ripping it out.
I'm +1 of course..
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
Re: [vote] remove renderTags default of true for @If/@Else? (tapestry
4.1.2 )
Posted by Tony Nelson <tn...@starpoint.com>.
I personally don't care which way you default, but I do think that all
tags should have the same default. It's much easier to remember to turn
it on/off if I don't have to try and remember which tags have which default.
I added:
<meta key="org.apache.tapestry.renderTags" value="true" />
to my Tapestry.application and was able to get the behavior I was after.
In short, consistency wins in my book every time.
Tony Nelson
Re: [vote] remove renderTags default of true for @If/@Else?
(tapestry 4.1.2 )
Posted by Matt Brock <br...@gmail.com>.
A year late and a dollar short, but for the record...
+1 for false
*No* component should render itself unless an "element" binding parameter
has been declared. I never understood why this was even an option.
Howard Lewis Ship wrote:
>
> +1 for false
>
> The problem with a hivemind contribution is that it can break behavior of
> framework components which is worse and more subtle than the bugs cause by
> changing the default value (in an alpha stage of the framework).
>
--
View this message in context: http://www.nabble.com/-vote--remove-renderTags-default-of-true-for-%40If-%40Else--%28tapestry-4.1.2-%29-tp10278944p15994717.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [vote] remove renderTags default of true for @If/@Else? (tapestry 4.1.2 )
Posted by Howard Lewis Ship <hl...@gmail.com>.
+1 for false
The problem with a hivemind contribution is that it can break behavior of
framework components which is worse and more subtle than the bugs cause by
changing the default value (in an alpha stage of the framework).
On 5/2/07, Andrea Chiumenti <ki...@gmail.com> wrote:
>
> +1 for both to false, adding a default behaviour into engine settings via
> hivemind contribution
>
> On 5/2/07, Christian Dutaret <cd...@gmail.com> wrote:
> >
> > Hmmm, just checked my own @If components, I have about 40% relying on
> the
> > default value to true.
> > I understand the logic behind this change, but this forces me to upgrade
> > quite a bunch of pages.
> >
> > so: +0.5
> >
> > 2007/5/2, Patrick Moore <pa...@buildcap.com>:
> > >
> > > +1 default to false for @If/@Else
> > > +1 default to true for @For
> > >
> >
>
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
Re: [vote] remove renderTags default of true for @If/@Else? (tapestry 4.1.2 )
Posted by Andrea Chiumenti <ki...@gmail.com>.
+1 for both to false, adding a default behaviour into engine settings via
hivemind contribution
On 5/2/07, Christian Dutaret <cd...@gmail.com> wrote:
>
> Hmmm, just checked my own @If components, I have about 40% relying on the
> default value to true.
> I understand the logic behind this change, but this forces me to upgrade
> quite a bunch of pages.
>
> so: +0.5
>
> 2007/5/2, Patrick Moore <pa...@buildcap.com>:
> >
> > +1 default to false for @If/@Else
> > +1 default to true for @For
> >
>
Re: [vote] remove renderTags default of true for @If/@Else? (tapestry 4.1.2 )
Posted by Christian Dutaret <cd...@gmail.com>.
Hmmm, just checked my own @If components, I have about 40% relying on the
default value to true.
I understand the logic behind this change, but this forces me to upgrade
quite a bunch of pages.
so: +0.5
2007/5/2, Patrick Moore <pa...@buildcap.com>:
>
> +1 default to false for @If/@Else
> +1 default to true for @For
>
Re: [vote] remove renderTags default of true for @If/@Else? (tapestry 4.1.2 )
Posted by Patrick Moore <pa...@buildcap.com>.
+1 default to false for @If/@Else
+1 default to true for @For
Re: [vote] remove renderTags default of true for @If/@Else? (tapestry 4.1.2 )
Posted by Andrea Chiumenti <ki...@gmail.com>.
ooops, the solution by Tony is what I meant!
On 5/2/07, Joe Chen <jo...@gmail.com> wrote:
>
> +1 both false.
>
> Upgrading from 4.0.x to 4.1.2 with the current default of true means that
> I
> have to reverse all the page logic in order for my pages to work as they
> did
> in 4.0.x. This is just a bad decision for people looking to upgrade. If
> the default is false, then at least pages render as they did in 4.0.x, and
> you can still output deprecation warnings for use of "element=".
>
>
> On 5/2/07, Robert J. Walker <rw...@mshare.net> wrote:
> >
> > +1 default both to false, and to make changing the default apply at the
> > app or library level rather than globally as indicated in the JIRA
> issue.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
Re: [vote] remove renderTags default of true for @If/@Else? (tapestry 4.1.2 )
Posted by Joe Chen <jo...@gmail.com>.
+1 both false.
Upgrading from 4.0.x to 4.1.2 with the current default of true means that I
have to reverse all the page logic in order for my pages to work as they did
in 4.0.x. This is just a bad decision for people looking to upgrade. If
the default is false, then at least pages render as they did in 4.0.x, and
you can still output deprecation warnings for use of "element=".
On 5/2/07, Robert J. Walker <rw...@mshare.net> wrote:
>
> +1 default both to false, and to make changing the default apply at the
> app or library level rather than globally as indicated in the JIRA issue.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
RE: [vote] remove renderTags default of true for @If/@Else? (tapestry 4.1.2 )
Posted by "Robert J. Walker" <rw...@mshare.net>.
+1 default both to false, and to make changing the default apply at the app or library level rather than globally as indicated in the JIRA issue.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org