I have made some more modifications to the LabelTag to make it more
extensible.
The way the tag works now is:
doStartTag() - starts the span (if styles are applied)
doAfterBody() - Determines which label to use (from the resource bundle or
from the body content.)
doEndTag() - ends the span (if
1) Putting an '*' into a label for required fields assumes people want
an
'*', maybe they want a '(R)' or maybe they want something else entirely
(perhaps an image...).
2) Putting an '*' after a label for required fields assumes people want
an '*' after the label. Perhaps they want the '*'
-Original Message-
From: Mike Jasnowski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 25, 2003 9:55 AM
To: Struts Users Mailing List
Subject: Form field styling/error reporting - Alternate solution [Long]
The technique centers around the use of XSLT to process what appears
between
the
IMHO, I think it is a better idea to 'wrap' whatever text
a user wants to use, however they want to generate it.
Ex:
html:label property=firstNameFirst Name: /html:label
-or-
html:label property=firstNamebean:message
property='firstName'//html:label
It's reasonable to allow the user to
message after this input field'. I think that is too much control and is
better left to the developer to put that html:errors tag where they want
it.
Jonathan
-Original Message-
From: DeRose Jonathan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 25, 2003 11:02 AM
To: Struts
Hey guys,
I have modified the LabelTag in my patch to use a key if provided.
If no key is provided, the body content will be displayed.
html:label property=password key=label.password/
-or-
html:label property=passwordPassword/html:label
Check it out at
I have a question about a patch I submitted,
http://issues.apache.org/bugzilla/show_bug.cgi?id=20784
A quick summary for anyone who may have missed it:
The enhancement provides lots of new functionality for error handling
beyond writing out the errors. (Developers could use it to highlight
Hi,
I think Struts should be as flexible/extensible as is possible/practical.
With that in mind, and after reading about this enhancement I have the
following concerns:
1) Putting an '*' into a label for required fields assumes people want an
'*', maybe they want a '(R)' or maybe they want
I am trying to prepare patch files for the dynamic style declaration using
the resource bundle. I am using WinCvs and am having two different problems
with the diff reports it churns out...
1) The first is that it says there are changes to code I havent touched.
Example: cvs diff u
I took my enhancement a step farther today and set it up to work with the
ResourceBundle. With this new implementation it is possible to set the
default styles you want to use once for the entire application. With this
new implementation, you can set the styles to use in one place. Before, you
Yes, that is part of the modifications I am proprosing.
The way I have set it up to work currently involves the creation of a new
LabelTag that would be used the following way.
html:label property=firstName styleClass=normal
errorStyleClass=errorbean:message key=firstName//html:label
(if the
Hello,
I have an idea that I would like to propose to the Struts community
involving the HTML tag library; automatic highlighting of errored form
elements. I have used Struts for a couple medium sized projects and always
extended the tags to get this functionality. After doing this two or
: DeRose Jonathan [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Friday, June 06, 2003 4:05 PM
Subject: Introduction and a proprosal to add new functionality to Struts:
Automatic highlighting of errored form elements
Hello,
I have an idea that I would like to propose
-atlanta.org
770-822-3359
AIM:jmitchtx
- Original Message -
From: DeRose Jonathan [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Friday, June 06, 2003 4:05 PM
Subject: Introduction and a proprosal to add new functionality to Struts:
Automatic highlighting of errored form
14 matches
Mail list logo
