The DateField has always been on my list of things that require fixes/enhancements/workarounds for some minor flaws, but I never got to it because of other higher priority issues I had to deal with. I was always annoyed by the fact that I couldn't cancel the popup just by clicking outside like I can with other dropdowns/popups. I would think that it could be fixed fairly easily by people who know the code behind the component. However, I am beginning to lose heart when most people seem to have simply given up on this component that is part of Tapestry. Is it really "dead", or should I keep believing that DateField is still alive and will continue to be improved upon?
Benny On Sun, Jan 9, 2011 at 3:34 PM, Bryan Lewis <jbryanle...@gmail.com> wrote: > I switched our apps some time ago to Tapx Datefield and we've been happy > with it. The only annoyance about it was the inability to easily override > the date parser. I was asked to make it accept two-digit years and I had > to > hack the source. But we were totally happy with it before that > requirement! > > > On Sun, Jan 9, 2011 at 3:17 PM, Paul Stanton <p...@mapshed.com.au> wrote: > > > yeah unfortunately, i'm going to have to give up on it too. have logged > > jira issues. > > > > jQuery isn't the best fit for me though, since prototype/scriptaculous is > > already required and i don't want to have another javascript framework > > dependency. > > > > what other date components are there out there that people have used? > > > > On 9/01/2011 8:54 PM, Gunnar Eketrapp wrote: > > > >> I gave up on datefield and switched to jQuery datepicker ... > >> > >> 2011/1/9 Paul Stanton<p...@mapshed.com.au>: > >> > >>> further to this, say your date format is m/d/yyyy and the initial value > >>> is > >>> 1/1/2011 and you want to change it to 2/1/2011.. that is not possible. > >>> changing month, the selected 'day' is still selected and therefore not > >>> selectable. > >>> > >>> use case: > >>> > >>> initial date is 2/1/2011 > >>> 1. open date picker > >>> 2. change month to feb > >>> 3. try to click on 1st of feb > >>> - nothing happens. > >>> > >>> On 9/01/2011 9:50 AM, Paul Stanton wrote: > >>> > >>>> hi all, > >>>> > >>>> using the datefield component, if a user changes their mind there > seems > >>>> to > >>>> be no way for them to close the popup without changing the value in > some > >>>> way > >>>> > >>>> > >>>> > >>>> > http://tapestry.apache.org/tapestry5.2-dev/tapestry-core/ref/org/apache/tapestry5/corelib/components/DateField.html > >>>> > >>>> once the icon has been clicked, there's no option to close the popup > >>>> explicitly and selecting the current value is disabled so the user has > >>>> to > >>>> select another date to close the popup. > >>>> > >>>> am i missing something or should i log an issue? > >>>> > >>>> p. > >>>> > >>>> --------------------------------------------------------------------- > >>>> 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 > >>> > >>> > >>> > >> > >> > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > >
