Yet more TagLibs problems

Question

As jato2 still doesn't know about some HTML4 tags like <label>
ex:
<label><input type="radio" ... />TheLabel</label>
if you click on "TheLabel", it clicks on the radio button, like every
other GUI
I thought I would be able use the <label for=""> as a workaround
<input type="radio" name="choice" id="choice1" /> <label
for="choice1">TheLabel</label>
BUT despite it generates several tags, <jato:radioButtons> sets the id
attribute to the same value for every tag :< This not only defeats my
workaround but also id main purpose to uniquely identity elements.
We really need a generic mechanism to specify attributes when jato tags
generate multiple HTML tags.
I can still change the generated tags in endDisplay but it be neat if
the 201 taglib was a little bit more XHTML compliant and savvy ;)
Fr?d?ric
ps: release this part of the source code and we'll do it !

Answer 1

Give me until monday and I'll have what you "ask" for (WML/XHTML
Basic/Mobile as well as ViewBean).
Following Todd advices,
for the former, I am having new tags to render the same components. I
may need to write new components but I'm not sure yet.
for the latter, 1 pagelet per "rendering" type with an inner
ContainerView when the logic is different ; the pagelet tags being
surrounded by a homemade tag that "activates" the pagelet based on the
client type. A specialized tag seems better than <jato:content> as the
logic is wired.
Further step would be to make the tags client aware but I'm not sure
yet it is the right thing to do. Are tags "allowed" to store data in
the session (to avoid computing client type ever and ever) ?
Fr?d?ric
PS: James Baty will confirm I'm not cheap ;?)
On mercredi, nov 13, 2002, at 21:11 Europe/Paris, Craig V. Conover
wrote:
Fr?d?ric
Is there anyway that we could talk with you about your WML efforts with
JATO?
I would love to get a sample WML app to show the world. And then have a
WML/HTML app to show multiple clients using the same ViewBeans.
craig
Fr?d?ric Miserey wrote:
On mercredi, nov 13, 2002, at 13:34 Europe/Paris, Todd Fast wrote:
Fr?d?ric--
Thanks for the info; I will look into a way of doing something
about
this.
However, please keep in mind that you can write your own complementary
tags
to render JATO components any way you like (or write JATO components
that
render themselves any way you like), and this is expected to be a
normal, if
infrequent, part of writing JATO 2.0 components.That's what I'm doing right now for the WML tags. But I was planning on
using the standard tags for mainstream HTML ;)
May you elaborate a little bit on complementary tags vs components ?
(first part of the suggested thread.
Until the 2.0 taglib is documented, you can use the 1.2.1 JATO
source
to
guide this effort.? It's actually pretty easy, but you will need the
source
to guide you without docs to that effect.? You can download the JATO
1.2.1
source, free of charge, etc. here:
???? http://iplanet.com/downloads/developer/5102.html
(If that doesn't work, just do a search for "JATO" on sun.com).? We
can also
start a tag-writing thread here if you like.
I would love to get your perspective on any XHTML shortcomings of the
current tag library.? Can you plase send your thoughts, list of
issues, etc.
to jatoteam@e...?you don't know what you've just asked ;)
Todd
----- Original Message -----
From: "Fr?d?ric Miserey" <frederic@n...>
Sent: Tuesday, November 12, 2002 8:35 AM
Subject: [SunONE-JATO] yet more TagLibs problems
As jato2 still doesn't know about some HTML4 tags like <label>
ex:
<label><input type="radio" ... />TheLabel</label>
if you click on "TheLabel", it clicks on the radio button, like
every
other GUI
I thought I would be able use the <label for="">? as a workaround
<input type="radio" name="choice" id="choice1" /> <label
for="choice1">TheLabel</label>
BUT despite it generates several tags, <jato:radioButtons> sets the id
attribute to the same value for every tag :< This not only defeats my
workaround but also id main purpose to uniquely identity elements.
We really need a generic mechanism to specify attributes when jato tags
generate multiple HTML tags.
I can still change the generated tags in endDisplay but it be neat if
the 201 taglib was a little bit more XHTML compliant and savvy ;)
Fr?d?ric
ps: release this part of the source code and we'll do it !
[Non-text portions of this message have been removed]