[OT] Why jwcid?

[Rui Pacheco <ru...@gmail.com>]

Hi all

Its slightly off-topic, but I've been wondering about this for a while: why
do we need to use "jwcid" to identify which elements in a form are to be
treated as Tapestry components? Why not use the normal "name" and "id"
identifiers used in HTML?

Once again, I'm  just curious, and sorry for disrupting the mailing list. We
didn't have much traffic today either :)
-- 
Cumprimentos,
Rui Pacheco

Re: [OT] Why jwcid?

[Howard Lewis Ship <hl...@gmail.com>]

You can configure what attribute Tapestry uses to "recognize" components.
The default is "jwcid", you can change this to anything you like, even "id".

http://tapestry.apache.org/tapestry4/UsersGuide/configuration.html

org.apache.tapestry.jwcid-attribute-name

On 8/10/06, Karthik N <ka...@gmail.com> wrote:
>
> i largely agree, although for some cases tapestry chooses to override your
> assigned id, with an id that tapestry chooses.
>
> On 8/10/06, Nick Westgate <ni...@key-planning.co.jp> wrote:
> >
> > In addition, id (and maybe name) are useful attributes for javascript
> > programming, so tapestry leaves them alone when it doesn't need them.
> > That way you can still use them in your own javascript.
> >
> > Cheers,
> > Nick.
> >
> >
> > Karthik N wrote:
> > > every element that does not have the jwcid attribute is treated as
> > "normal"
> > > html - tapestry does not care too much about it.
> > >
> > > every element that has jwcid is an indicator to tapestry that we're
> > > creating
> > > a tapestry component - so such html takes a very different lease of
> life
> > as
> > > a tapestry component.
> > >
> > > On 8/9/06, Rui Pacheco <ru...@gmail.com> wrote:
> > >
> > >>
> > >> Hi all
> > >>
> > >> Its slightly off-topic, but I've been wondering about this for a
> while:
> > >> why
> > >> do we need to use "jwcid" to identify which elements in a form are to
> > be
> > >> treated as Tapestry components? Why not use the normal "name" and
> "id"
> > >> identifiers used in HTML?
> > >>
> > >> Once again, I'm  just curious, and sorry for disrupting the mailing
> > list.
> > >> We
> > >> didn't have much traffic today either :)
> > >> --
> > >> Cumprimentos,
> > >> Rui Pacheco
> > >>
> > >>
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Thanks, Karthik
>
>


-- 
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: [OT] Why jwcid?

[Karthik N <ka...@gmail.com>]

i largely agree, although for some cases tapestry chooses to override your
assigned id, with an id that tapestry chooses.

On 8/10/06, Nick Westgate <ni...@key-planning.co.jp> wrote:
>
> In addition, id (and maybe name) are useful attributes for javascript
> programming, so tapestry leaves them alone when it doesn't need them.
> That way you can still use them in your own javascript.
>
> Cheers,
> Nick.
>
>
> Karthik N wrote:
> > every element that does not have the jwcid attribute is treated as
> "normal"
> > html - tapestry does not care too much about it.
> >
> > every element that has jwcid is an indicator to tapestry that we're
> > creating
> > a tapestry component - so such html takes a very different lease of life
> as
> > a tapestry component.
> >
> > On 8/9/06, Rui Pacheco <ru...@gmail.com> wrote:
> >
> >>
> >> Hi all
> >>
> >> Its slightly off-topic, but I've been wondering about this for a while:
> >> why
> >> do we need to use "jwcid" to identify which elements in a form are to
> be
> >> treated as Tapestry components? Why not use the normal "name" and "id"
> >> identifiers used in HTML?
> >>
> >> Once again, I'm  just curious, and sorry for disrupting the mailing
> list.
> >> We
> >> didn't have much traffic today either :)
> >> --
> >> Cumprimentos,
> >> Rui Pacheco
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>


-- 
Thanks, Karthik

Re: [OT] Why jwcid?

[Nick Westgate <ni...@key-planning.co.jp>]

In addition, id (and maybe name) are useful attributes for javascript
programming, so tapestry leaves them alone when it doesn't need them.
That way you can still use them in your own javascript.

Cheers,
Nick.


Karthik N wrote:
> every element that does not have the jwcid attribute is treated as "normal"
> html - tapestry does not care too much about it.
> 
> every element that has jwcid is an indicator to tapestry that we're 
> creating
> a tapestry component - so such html takes a very different lease of life as
> a tapestry component.
> 
> On 8/9/06, Rui Pacheco <ru...@gmail.com> wrote:
> 
>>
>> Hi all
>>
>> Its slightly off-topic, but I've been wondering about this for a while:
>> why
>> do we need to use "jwcid" to identify which elements in a form are to be
>> treated as Tapestry components? Why not use the normal "name" and "id"
>> identifiers used in HTML?
>>
>> Once again, I'm  just curious, and sorry for disrupting the mailing list.
>> We
>> didn't have much traffic today either :)
>> -- 
>> Cumprimentos,
>> Rui Pacheco
>>
>>
> 
> 

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

Re: [OT] Why jwcid?

[Rui Pacheco <ru...@gmail.com>]

Ok, many thanks.

On 8/9/06, Karthik N <ka...@gmail.com> wrote:
>
> every element that does not have the jwcid attribute is treated as
> "normal"
> html - tapestry does not care too much about it.
>
> every element that has jwcid is an indicator to tapestry that we're
> creating
> a tapestry component - so such html takes a very different lease of life
> as
> a tapestry component.
>
> On 8/9/06, Rui Pacheco <ru...@gmail.com> wrote:
> >
> > Hi all
> >
> > Its slightly off-topic, but I've been wondering about this for a while:
> > why
> > do we need to use "jwcid" to identify which elements in a form are to be
> > treated as Tapestry components? Why not use the normal "name" and "id"
> > identifiers used in HTML?
> >
> > Once again, I'm  just curious, and sorry for disrupting the mailing
> list.
> > We
> > didn't have much traffic today either :)
> > --
> > Cumprimentos,
> > Rui Pacheco
> >
> >
>
>
> --
> Thanks, Karthik
>
>


-- 
Cumprimentos,
Rui Pacheco

Re: [OT] Why jwcid?

[Karthik N <ka...@gmail.com>]

every element that does not have the jwcid attribute is treated as "normal"
html - tapestry does not care too much about it.

every element that has jwcid is an indicator to tapestry that we're creating
a tapestry component - so such html takes a very different lease of life as
a tapestry component.

On 8/9/06, Rui Pacheco <ru...@gmail.com> wrote:
>
> Hi all
>
> Its slightly off-topic, but I've been wondering about this for a while:
> why
> do we need to use "jwcid" to identify which elements in a form are to be
> treated as Tapestry components? Why not use the normal "name" and "id"
> identifiers used in HTML?
>
> Once again, I'm  just curious, and sorry for disrupting the mailing list.
> We
> didn't have much traffic today either :)
> --
> Cumprimentos,
> Rui Pacheco
>
>


-- 
Thanks, Karthik