Re: DateField behaviour when within a zone

"Thiago H. de Paula Figueiredo" <[email protected]> Mon, 10 Dec 2018 10:41:50 -0200

Newsgroups	gmane.comp.java.tapestry.user
Message-ID	<CAE_88GbMieAXii=gfUzLH=QviFTjVB7K5H4YnJjYOM7YFga_NQ@mail.gmail.com>

Hello, Christopher!

I got tired of waiting for my bosses and I had to release Tapestry 5.4.4
anyway (see the vote thread on the Tapestry dev mailing list for more
details) so I decided to rewrite it from scratch to be included in this
release. Please take a look. :)

On Thu, Dec 6, 2018 at 9:44 PM Christopher Dodunski <
[email protected]> wrote:

> On second thoughts, producing a new DateTimeField component is probably
> wiser.
>
> I'm impressed by the HTML5 "datetime-local" input type.  Browsers that
> don't support it should gracefully degrade to plain textfield.
>
> A DateTimeField component based on this HTML5 element would be lighter
> weight than the existing DateField component, as there would be no need
> for server round trips to wire the field and picker.  Dates would be
> formatted and parsed on component rendering and submission only.
>
> What do you think?
>
> Regards,
>
> Chris.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

-- 
Thiago