Re: Why does FieldLabel not produce ?

[Eric Everman <ev...@precedadesign.com>]

Yep, I would agree that the form components are lacking.  I just 
completed a very small forms application (2 pages) for a customer 
needing very quick turn-around time - I found that some of the things I 
had taken for-granted ended up consuming all my time.  For instance:

-The only fields that are validated are text fields.
-Out of the box validation only sets a min length & required, not max 
length.  Sure this is an input tag property, but that would put 
validation in the .html, the .page, possibly the .class, and still in 
the db.  Sheesh!
-I don't see an easy way to make a 'vanilla' Select list.  IE.  I just 
want to have a list of Countries in a select list.  I want it in the 
page because its not really domain data, its just a convenience for the 
user and I want a casual HTML person to be able to add to the list.
-The input/validation tags don't support label - this means I need to 
nest extra tags all over the place.  My HTML source is much less 
readable and I still don't have proper linkage between my label tags 
and my input tags.  This one is a real killer for usability as it 
encourages Tapestry developers to *not* provide those 'for' links.
-(Misc Gripe while I'm at it)  I end up duplicating tags all over the 
place because the tag containing the jwcid is not rendered for many 
tags.  It would be nice to have a way to control this so that I I have 
a conditional tag it could double as the <tr> or <div> tag I intend to 
conditionally create.  Again, my pages end up being much less readable. 
  Perhaps this one has been solved and I didn't realize it?

Anyway, I love using Tapestry - but there are still some foibles.  
Anyone else have suggestions / ideas / comments on these?

Cheers,
Eric Everman



On 30 Sep 2004, at 02:24, Filip S. Adamsen wrote:

> Because whoever developed the @FieldLabel overlooked the fact that 
> usability
> is one of the hottest issues in user interface design? Maybe. There 
> are room
> for a lot of improvements in this area regarding form components. But I
> think a lot of those will be found in Tapestry 3.1 - or at least, I 
> hope it.
>
> -Filip
>
>> -----Original Message-----
>> From: Eric Everman [mailto:everman@precedadesign.com]
>> Sent: Thursday, September 30, 2004 12:52 AM
>> To: Tapestry users
>> Subject: Why does FieldLabel not produce <label>?
>>
>> Hi-
>>
>> Just started playing with validation and I'm wondering if there is a
>> reason why the FieldLabel component doesn't produce a <label> tag.  I
>> realize I could use a span tag wrapped in a label tag, but I'll need 
>> to
>> sync up the label's 'for' attribute so that the html form will allow
>> label clicks to be translated into focus placement.
>>
>> Thoughts?
>>
>> Eric Everman
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>


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