On Fri, Dec 14, 2018 at 3:57 AM Christopher Dodunski <
chrisfromtapes...@christopher.net.nz> wrote:
> Hi Thiago,
>
Hello, Christopher!
> Yes, I'll certainly use your Html5DateField wherever I can, in preference
> to the WebFX based DateField component, whenever just a date is required.
> Good e
Hi Thiago,
Yes, I'll certainly use your Html5DateField wherever I can, in preference
to the WebFX based DateField component, whenever just a date is required.
Good effort!
Indeed, datetime-local is not yet widely implemented in desktop browsers
(seems to work fine in Chrome and Edge, but not IE
On Tue, Dec 11, 2018 at 8:14 AM Christopher Dodunski <
chrisfromtapes...@christopher.net.nz> wrote:
> Hi Thiago,
>
Hello!
> Great, I'll take a look. Meanwhile, because of working to a deadline,
> last weekend I developed my own, and was just about to offer it to the
> Tapestry community. But
Hi Thiago,
Great, I'll take a look. Meanwhile, because of working to a deadline,
last weekend I developed my own, and was just about to offer it to the
Tapestry community. But maybe there's no need now?
I based it on HTML 5 datetime-local. The various browser implementations
of this element ar
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
I'm still waiting for my bosses to release the Html5DateField we have in
our projects . . .
On Thu, Dec 6, 2018 at 9:44 PM Christopher Dodunski <
chrisfromtapes...@christopher.net.nz> wrote:
> On second thoughts, producing a new DateTimeField component is probably
> wiser.
>
> I'm impressed by th
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 t
Thanks Chris.
What puzzled me about the absent closing tag is that it appears
in the first example above, but not the second. Yet this markup is
generated by the same DateField component (line 276 to be precise:
"writer.end()").
I searched the web for alternative 'date pickers'. Bootstrap prov
Hi
is valid html, while is valid xhtml, so depending on what
you are outputting open may be appropriate.
If the built-in datepicker is giving you grief, roll your own... I find
that we (at work) eventually have had to replace almost all of the slightly
fancy "gui" components in tapestry, while
Just a few short questions to help progress with problem solving.
1) Is there any known reason why DateField's WebFX DatePicker wouldn't
work within an embedded Tapestry component? I've had no problem with it
working directly in a Tapestry page. Don't want to be flogging a dead
horse here. :-)
On Sun, Dec 2, 2018 at 10:22 PM Christopher Dodunski <
chrisfromtapes...@christopher.net.nz> wrote:
> After examining the application's log files I noticed that using the
> datepicker resulted in the dashboard page's onActivate() method being
> invoked. This was unexpected.
>
I'm afraid this is
Making some headway...
The base page is "Dashboard", which contains 10 panel components (each
having its own zone). Three of these panels require a "FilterPane" for
limiting the number of records displayed (again, this filter pane has its
own zone). This pane contains a form, and this form conta
On Sun, Dec 2, 2018 at 9:16 AM Christopher Dodunski <
chrisfromtapes...@christopher.net.nz> wrote:
> > Not all components have that parameter. DatePicker doesn't trigger zone
> > refreshes as far as I know.
>
> According to the Tapestry docs for DateField:
>
> "One wierd aspect here is that, becau
>> I imagine others are using the existing DateField with success, whether
>> inside or outside of zones. Assuming the DatePicker javascript is using
>> AJAX to invoke a zone refresh, is there perhaps a way of disabling this
>> without meddling with the code? I had thought that without "async=tru
On Fri, Nov 30, 2018 at 4:03 AM Christopher Dodunski <
chrisfromtapes...@christopher.net.nz> wrote:
> That sounds promising Thiago. Does your component support time also,
Nope, just date, but it could be copied and adapted to one who accepts time
too.
> or just date (you mentioned -mm-dd
That sounds promising Thiago. Does your component support time also, or
just date (you mentioned -mm-dd is hardcoded)?
I imagine others are using the existing DateField with success, whether
inside or outside of zones. Assuming the DatePicker javascript is using
AJAX to invoke a zone refresh
Hello!
Something I did in my day job was to create an Html5DateField class by
copying the DateField sources and removing all the JavaScript from it and
also hardcoding the date format to -MM-dd. In addition, instead of
outputting , it outputs wrote:
> Hi all,
>
> I've successfully been using
Hi all,
I've successfully been using the datefield component within a number of
tapestry pages. But now that I've embedded a datefield within a custom
component that is nested within a zone, the datepicker isn't working as it
should. When the datepicker is used to select a certain date, the zone
18 matches
Mail list logo
