You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Mind Bridge <mi...@yahoo.com> on 2005/01/16 01:35:16 UTC
Tapestry 3.1 and T-Deli components
Hi guys,
Have you had any experience with the components located on T-Deli
(www.t-deli.com)? Does it make sense to make some of them or components
similar to them to be a part of 3.1? I am refering particularly to the For,
If, and Else components, but I think the others may make sense to be a part
of the distribution as well. The FormLinkRenderer will probably be of use
once properties go into the URL, for example.
What do you think?
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Tapestry 3.1 and T-Deli components
Posted by Mind Bridge <mi...@yahoo.com>.
Hi,
I have tried to model the existing components as closely as possible. The
IActionListener parameter is a feature of ListEdit, and hence I have added
it in to maintain compatibility. I personally do not mind removing it since
I have not used it, but I suspect it has been used by others. What do people
think, does this need to be removed?
Also, the components by default figure out whether they are in a form or not
and alter their behaviour accordingly. If they are in a form, Hidden fields
will be generated automatically. The 'formless' parameter is simply a way to
turn this off -- if it is set to 'true', For will not generate Hidden fields
even if it is in a form. In other words, it will simply behave as a Foreach.
I think such a parameter is essential in some cases.
Finally note that the parameters like 'templateTag' are really private and
should actually be removed from the documentation. They are filled in by the
framework, not by the user.
I hope this clears things up a bit...
----- Original Message -----
From: "Paul Ferraro" <pm...@columbia.edu>
To: "Tapestry development" <ta...@jakarta.apache.org>
Sent: Tuesday, January 18, 2005 4:12 AM
Subject: Re: Tapestry 3.1 and T-Deli components
> Only because they have fairly fat interfaces. The baseline components
> are lean and mean, and yet provide functional coverage.
> Still, I like the concept of proactively addressing
> StaleLinkExceptions. Maybe the interfaces can be trimmed?
> e.g. are IActionListeners really necessary? Can the 'formless'
> parameter be determined by: (Form.get(requestCycle) == null)?
>
> Paul
>
> Mind Bridge wrote:
>
> >May I ask why you think so?
> >
> >The only effect of replacing the current components with those ones would
be
> >to remove the significant number of "Why do I get a StaleLinkException?"
> >messages on the -user list and possibly cut down on the number of white
> >hairs.
> >
> >Is that a bad thing?
> >
> >
> >----- Original Message -----
> >From: "Paul Ferraro" <pm...@columbia.edu>
> >To: "Tapestry development" <ta...@jakarta.apache.org>
> >Sent: Monday, January 17, 2005 8:47 PM
> >Subject: Re: Tapestry 3.1 and T-Deli components
> >
> >
> >
> >
> >>I haven't used any of these components, but my initial reaction is that
> >>they are more appropriate for the contrib library.
> >>I think the FormLinkRenderer should definitely go into 3.1.
> >>
> >>Paul
> >>
> >>Mind Bridge wrote:
> >>
> >>
> >>
> >>>Hi guys,
> >>>
> >>>Have you had any experience with the components located on T-Deli
> >>>(www.t-deli.com)? Does it make sense to make some of them or components
> >>>similar to them to be a part of 3.1? I am refering particularly to the
> >>>
> >>>
> >For,
> >
> >
> >>>If, and Else components, but I think the others may make sense to be a
> >>>
> >>>
> >part
> >
> >
> >>>of the distribution as well. The FormLinkRenderer will probably be of
use
> >>>once properties go into the URL, for example.
> >>>
> >>>What do you think?
> >>>
> >>>
> >>>---------------------------------------------------------------------
> >>>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
> >>
> >>
> >>
> >>
> >
> >
> >---------------------------------------------------------------------
> >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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Tapestry 3.1 and T-Deli components
Posted by Paul Ferraro <pm...@columbia.edu>.
Only because they have fairly fat interfaces. The baseline components
are lean and mean, and yet provide functional coverage.
Still, I like the concept of proactively addressing
StaleLinkExceptions. Maybe the interfaces can be trimmed?
e.g. are IActionListeners really necessary? Can the 'formless'
parameter be determined by: (Form.get(requestCycle) == null)?
Paul
Mind Bridge wrote:
>May I ask why you think so?
>
>The only effect of replacing the current components with those ones would be
>to remove the significant number of "Why do I get a StaleLinkException?"
>messages on the -user list and possibly cut down on the number of white
>hairs.
>
>Is that a bad thing?
>
>
>----- Original Message -----
>From: "Paul Ferraro" <pm...@columbia.edu>
>To: "Tapestry development" <ta...@jakarta.apache.org>
>Sent: Monday, January 17, 2005 8:47 PM
>Subject: Re: Tapestry 3.1 and T-Deli components
>
>
>
>
>>I haven't used any of these components, but my initial reaction is that
>>they are more appropriate for the contrib library.
>>I think the FormLinkRenderer should definitely go into 3.1.
>>
>>Paul
>>
>>Mind Bridge wrote:
>>
>>
>>
>>>Hi guys,
>>>
>>>Have you had any experience with the components located on T-Deli
>>>(www.t-deli.com)? Does it make sense to make some of them or components
>>>similar to them to be a part of 3.1? I am refering particularly to the
>>>
>>>
>For,
>
>
>>>If, and Else components, but I think the others may make sense to be a
>>>
>>>
>part
>
>
>>>of the distribution as well. The FormLinkRenderer will probably be of use
>>>once properties go into the URL, for example.
>>>
>>>What do you think?
>>>
>>>
>>>---------------------------------------------------------------------
>>>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
>>
>>
>>
>>
>
>
>---------------------------------------------------------------------
>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: Tapestry 3.1 and T-Deli components
Posted by Mind Bridge <mi...@yahoo.com>.
May I ask why you think so?
The only effect of replacing the current components with those ones would be
to remove the significant number of "Why do I get a StaleLinkException?"
messages on the -user list and possibly cut down on the number of white
hairs.
Is that a bad thing?
----- Original Message -----
From: "Paul Ferraro" <pm...@columbia.edu>
To: "Tapestry development" <ta...@jakarta.apache.org>
Sent: Monday, January 17, 2005 8:47 PM
Subject: Re: Tapestry 3.1 and T-Deli components
> I haven't used any of these components, but my initial reaction is that
> they are more appropriate for the contrib library.
> I think the FormLinkRenderer should definitely go into 3.1.
>
> Paul
>
> Mind Bridge wrote:
>
> >Hi guys,
> >
> >Have you had any experience with the components located on T-Deli
> >(www.t-deli.com)? Does it make sense to make some of them or components
> >similar to them to be a part of 3.1? I am refering particularly to the
For,
> >If, and Else components, but I think the others may make sense to be a
part
> >of the distribution as well. The FormLinkRenderer will probably be of use
> >once properties go into the URL, for example.
> >
> >What do you think?
> >
> >
> >---------------------------------------------------------------------
> >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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Tapestry 3.1 and T-Deli components
Posted by Paul Ferraro <pm...@columbia.edu>.
I haven't used any of these components, but my initial reaction is that
they are more appropriate for the contrib library.
I think the FormLinkRenderer should definitely go into 3.1.
Paul
Mind Bridge wrote:
>Hi guys,
>
>Have you had any experience with the components located on T-Deli
>(www.t-deli.com)? Does it make sense to make some of them or components
>similar to them to be a part of 3.1? I am refering particularly to the For,
>If, and Else components, but I think the others may make sense to be a part
>of the distribution as well. The FormLinkRenderer will probably be of use
>once properties go into the URL, for example.
>
>What do you think?
>
>
>---------------------------------------------------------------------
>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: Tapestry 3.1 and T-Deli components
Posted by Robert Zeigler <rd...@u.arizona.edu>.
I use these all the time, and would love to see them included in the
standard distribution.
Robert Zeigler
Mind Bridge wrote:
> Hi guys,
>
> Have you had any experience with the components located on T-Deli
> (www.t-deli.com)? Does it make sense to make some of them or components
> similar to them to be a part of 3.1? I am refering particularly to the For,
> If, and Else components, but I think the others may make sense to be a part
> of the distribution as well. The FormLinkRenderer will probably be of use
> once properties go into the URL, for example.
>
> What do you think?
>
>
> ---------------------------------------------------------------------
> 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