James Holmes wrote:
You can make the changes against either, but making them against the
STRUTS_2_0_X might be best.
Done. (And more useful for me, because I was able to just start using
the snapshot to test the added functionality.)
If you make the patches against that branch I will
take
You can make the changes against either, but making them against the
STRUTS_2_0_X might be best. If you make the patches against that branch I will
take care of forward porting them to the trunk (Struts 2.1).
James
On Fri Jul 20 17:35 , Dale Newfield <[EMAIL PROTECTED]> sent:
>Dale Newfield w
Dale Newfield wrote:
https://issues.apache.org/struts/browse/WW-2051 opened. I'll check out
the SVN repository and start working on the patches tonight.
Waitaminit...
Should I be developing patches against
http://svn.apache.org/repos/asf/struts/struts2/branches/STRUTS_2_0_X
or
http://svn.apa
James Holmes wrote:
I ran into this issue as well and was thinking of implementing "onclick" attributes for each of the optionstransferselect buttons so that I could
capture when one of the lists changes.
That seems reasonable, more in line with the existing implementation,
and potentially mor
Dale,
I ran into this issue as well and was thinking of implementing "onclick"
attributes for each of the optionstransferselect buttons so that I could
capture when one of the lists changes. This would be similar to what you're
doing, accept that it would require every button's onlick event to
An optiontransferselect is composed on the page of a couple select
boxes, and buttons to move items around in/between them. The semantic
meaning of this collection of elements is a single selected and ordered
list, and I would like to add an "onchange" javascript call for when the
selected ite
6 matches
Mail list logo
