Re: [Stripes-users] Feature Request for label selection
Many thanks. I did consider all of your suggestions. I don't want to use Javascript at present for a variety of reasons, not least the impact it has on screen readers used by the visually impaired. I agree I could use HTML but I decided in the end to create another event. It was just a suggestion for a new feature. A better suggestion , as it applies to several tags, might be to be able to alter the value resolution order in the tag. So I could put in a value attribute or body (as one of the suggestion was but it won't work) and force the tag to use that instead of the normal resolution order. This would be useful for other tags as well, e.g.g when collecting a value and altering it to pass on (say a flag that indicated read only but needs to be switched to the opposite). I currently do this by declaring a write-only property that in fact alters its readonly variant. -- View this message in context: http://old.nabble.com/Feature-Request-for-label-selection-tp26525265p26540671.html Sent from the stripes-users mailing list archive at Nabble.com. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
Re: [Stripes-users] Feature Request for label selection
Iwao AVE! wrote: It wouldn't work, unfortunately. Please see: http://www.stripesframework.org/jira/browse/STS-679 It's strange: I used it once and works fine ! (with stripes 1.5.2) -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
Re: [Stripes-users] Feature Request for label selection
Hey Simon -
You've got lots of options... one would be to just use HTML:
input type=submit name=newDetails value=fmt:message key=newDetails//
This will invoke the same event but set the value to be the localization string
passed in by the JSTL localization tag.
There's nothing too magical about the stripes:submit tag.
You could even use:
stripe:hidden name=newDetails/
button onClick=document.form[0].submit(); fmt:message
key=newDetails//button
On Nov 26, 2009, at 12:06 AM, Simon Keen wrote:
I am building a multi-national system and localisation is very important. I
admit to only using stripes for about 8 months and may have missed something
so please advise me if I am doing something wrong. Hwoever, I find the
overlaoded use of the 'name' attribute in some tags gets in the way.
For example in stripse:submit the name attribute controls the event that
will invoked and the localisation lookup. This causes problems when you
want 2 or more buttons that invoke the same event but because of different
parameters being set will actually cause different effects on the subsequent
page.
For example, assume I have a form that contains information about a
department. I wish to have 2 buttons that will call a newDetails event to
display a blank form. In one case the do not set the parent department id
to that of the current department's parent ( create a sibling) and in
another case the parent dept id is set to the department currently displayed
(ie create a child dept).
This could be easily achieved with:
s:form bean=...
...
s:hidden name=newParentDept value=${actionBean.parentDept}/
s:submit name=newDetails/
/s:form
s:form bean=...
...
s:hidden name=newParentDept value=${actionBean.id}/
s:submit name=newDetails/
/s:form
This would all work well, including the transferring the value by setting
and property that has not getter and actually sets the parentDept property
via the setter setNewParentDept except the two buttons can not be given
different labels as the resource lookup (fixed labels are no good) has no
way of resolving them differently. It would be great to have another option
in the tags that enables a lookup key as another labeling option, a bit like
the for and name attributes in s:label.
--
View this message in context:
http://old.nabble.com/Feature-Request-for-label-selection-tp26525265p26525265.html
Sent from the stripes-users mailing list archive at Nabble.com.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
Re: [Stripes-users] Feature Request for label selection
It wouldn't work, unfortunately.
Please see:
http://www.stripesframework.org/jira/browse/STS-679
Regards,
Iwao
On 2009/11/26, at 18:39, Lionel lio...@art-informatique.com wrote:
Simon Keen wrote:
This could be easily achieved with:
s:form bean=...
...
s:hidden name=newParentDept value=${actionBean.parentDept}/
s:submit name=newDetails/
/s:form
s:form bean=...
...
s:hidden name=newParentDept value=${actionBean.id}/
s:submit name=newDetails/
/s:form
Did you try this:
s:submit name=newDetailsfmt:message key=myKey//s:submit
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
Re: [Stripes-users] Feature Request for label selection
You could also work around this another way... define another event that
calls the first, like so:
public Resolution newDetails() {
...
}
public Resolution otherDetails {
return newDetails();
}
Then you could use two different submit 'names', which would resolve to
different names. The downside of this is that you'll have to annotate the
two events independently, because they won't fire when being called
manually.
-Brandon
On Thu, Nov 26, 2009 at 6:50 AM, Iwao AVE! haraw...@gmail.com wrote:
It wouldn't work, unfortunately.
Please see:
http://www.stripesframework.org/jira/browse/STS-679
Regards,
Iwao
On 2009/11/26, at 18:39, Lionel lio...@art-informatique.com wrote:
Simon Keen wrote:
This could be easily achieved with:
s:form bean=...
...
s:hidden name=newParentDept value=${actionBean.parentDept}/
s:submit name=newDetails/
/s:form
s:form bean=...
...
s:hidden name=newParentDept value=${actionBean.id}/
s:submit name=newDetails/
/s:form
Did you try this:
s:submit name=newDetailsfmt:message key=myKey//s:submit
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus
on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
