I'll try to take a look at these by the end of the week. No promises, though; it's a busy week. ;)
Robert On May 24, 2011, at 5/247:39 PM , Paul Stanton wrote: > 6 months on, this hasn't been looked at by a tapestry committer? > > particularly > https://issues.apache.org/jira/browse/TAP5-1409 > which is clearly a bug, and i've even posted a potential patch. > > I'm starting new tapestry projects and copying a set of patches around is not > ideal ;) > > I understand that some of you use tapx or chenillekit for date pickers, but > the default implementation should still work... > > regards, Paul. > > > On 10/01/2011 8:09 AM, Thiago H. de Paula Figueiredo wrote: >> On Sun, 09 Jan 2011 19:06:59 -0200, Paul Stanton <p...@mapshed.com.au> wrote: >> >>> there is now (as of about 2 hrs ago) >>> >>> https://issues.apache.org/jira/browse/TAP5-1408 >>> https://issues.apache.org/jira/browse/TAP5-1409 >> >> Thanks for the info. :) >> >>> i'd prefer to use a built in tapestry component over another JS solution or >>> tapestry extension but as it stands the component is not suitable. i may >>> try and patch it .... >> >> Please go ahead! >> >>> interesting that tapx has a better datefield and is howards baby ... why >>> isn't this included in tapestry? licensing issues? >> >> Licensing issues (incompatibility with the Apache License). >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
