Ah, okay, thanks!
On Tue, May 3, 2016 at 2:38 PM, Martin Grigorov
wrote:
> There is a task for Wicket 8 for this.
> On May 4, 2016 12:32 AM, "Lon Varscsak" wrote:
>
> > Shouldn’t DateLabel allow Joda dates to be used in addition to
> >
There is a task for Wicket 8 for this.
On May 4, 2016 12:32 AM, "Lon Varscsak" wrote:
> Shouldn’t DateLabel allow Joda dates to be used in addition to
> java.util.Date?
>
> Thanks,
>
> Lon (Wicket Newb :D)
>
datefield should be attached to a span or a wicket:container tag
rather then an input tag.
so span wicket:id=datefield/span
-igor
On Wed, Jan 14, 2009 at 8:46 PM, Phillip Rhodes
spamsu...@rhoderunner.com wrote:
This is my first full day with wicket, so please bear with me.
I am trying to use
Subject: Re: wicket-datetime
I'd potentially like to use this component, but its putting a ridiculous
amount of markup into the script section in the head. Including a copy of
the license...
Licenses are only included/ not filtered out when Wicket runs in
development mode.
Also, if I add 2
On Tue, Mar 11, 2008 at 9:58 AM, Hoover, William [EMAIL PROTECTED] wrote:
It looks like the datetime component has major issues of its own that make it
virtually unusable (https://issues.apache.org/jira/browse/WICKET-1412).
We've been using this component for quite a while (eating our own dog
There was sometrouble with safari 2, but wicket got patched and that
fixed it.
Alex Jacoby wrote:
Side note: the demo doesn't seem to be working in Safari (3.0.4).
Clicking the calendar icon doesn't do anything. I don't see any JS
errors in the console.
Anyone else seen this?
Alex
On
Odd... Just tested again and it's working now.
Pretty sure I wasn't hallucinating before but if no one else notices
the problem I'll chalk it up to gremlins in my computer.
I was using Safari 3 on leopard, btw.
Alex
On Mar 11, 2008, at 4:00 PM, Nino Saturnino Martinez Vazquez Wael wrote:
Hi Igor,
The picker works fine - its the implementation I'm concerned about.
If you have 2 instances, then all the javascript exists twice. All the
translations exist twice.
The demo does not show 2 date pickers and you can clearly see the dependance
on initdateTextField2 being pasted into
Hi all,
This is causing me some issues as well. I have a page which contains
21 datepickers... These add 59KB of JavaScript to the head and I now
believe might be the cause of a ~three second browser pause I'm seeing
when the entering the page.
The 1.2.6 datepicker component kept its
Side note: the demo doesn't seem to be working in Safari (3.0.4).
Clicking the calendar icon doesn't do anything. I don't see any JS
errors in the console.
Anyone else seen this?
Alex
On Mar 6, 2008, at 1:20 AM, Igor Vaynberg wrote:
it seems to be working just fine here
If you don't have licence matter you can download the old 1.2.x datepicker
available here
http://wicketstuff.org/confluence/display/STUFFWIKI/wicket-contrib-datepicker
and refactor to make it use the Wicket 1.3.x core classes.
That's all .
/ Paolo
On Thu, Mar 6, 2008 at 11:23 AM, Charlie
i have no idea how much of that javascript can be factored out and how
much of it is requried to init each instance of the yui calendar.
(didnt write that one). perhaps gerolf or eelco wouldnt mind pipinig
in... i didnt see any license headers being dumped into html though.
personally ive used
off the top of my head, i'd say we could skip the localization part for
Locale.ENGLISH (and the like), as it's the default language in YUI.
couple of YUI releases, we switched to using the YUILoader to
dynamically load the needed .js files. and now that you've mentioned it,
it may not be an ideal
Thanks for the calendar info - i'll check it out.
nb, they both share the same bug in StyleDateConverter.java where the
formatter does not take the component locale.
I've created a Jira item for this for the wicket-datetime component.
https://issues.apache.org/jira/browse/WICKET-1401
Rgds
Ned
Thanks for the reply.
Core to my requirement is internationalisation, and per locale date formats
(both client and server side).
The wicket-datetime one is close to ideal, just has some implementation
issues which I believe could be cleaned up in a manner similar to *.js
convenience methods.
On 3/6/08, Ned Collyer [EMAIL PROTECTED] wrote:
I'd potentially like to use this component, but its putting a ridiculous
amount of javascript into the script section in the head. Including a
copy
of the license...
Is there an easy way to move this into a separate request/resource - 1
it seems to be working just fine here
http://wicketstuff.org/wicket13/dates/
-igor
On Wed, Mar 5, 2008 at 8:33 PM, Ned Collyer [EMAIL PROTECTED] wrote:
I'd potentially like to use this component, but its putting a ridiculous
amount of markup into the script section in the head.
this should be fixed in trunk.
Gerolf
On Thu, Feb 28, 2008 at 9:21 AM, Andrew Moore [EMAIL PROTECTED]
wrote:
I've just upgraded to wicket 1.3.1 and seem to be having a problem getting
the calendar to display correctly.
It works, but it's not picking up calendar css.
From having a quick
Answering myself. The problem does not occur anymore in yesterday's snapshot.
Thanks to whoever fixed it,
Wilko Hische
--
View this message in context:
http://www.nabble.com/wicket-datetime-rc2-javascript-error-in-generated-event.js-tp14438031p14457168.html
Sent from the Wicket - User mailing
GREAT!! :)
Thanks. Did you also get the patch for the standalone (always shown)
calendar commited?
regards Nino
Gerolf Seitz wrote:
On 10/1/07, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED]
wrote:
Multipage calendar
http://developer.yahoo.com/yui/examples/calendar/calgrp.html
On 10/3/07, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED]
wrote:
GREAT!! :)
Thanks. Did you also get the patch for the standalone (always shown)
calendar commited?
which patch?
do you mean the DatePicker#renderOnLoad and #hideOnSelect thingy? that
should be in.
gerolf
regards
Yup thats the one:)..
Gerolf Seitz wrote:
On 10/3/07, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED]
wrote:
GREAT!! :)
Thanks. Did you also get the patch for the standalone (always shown)
calendar commited?
which patch?
do you mean the DatePicker#renderOnLoad and
Hmm, Im trying to make the calendar work with the DateTextField from the
extensions(I guess thats the one I should use right?). But something are
wrong, now my ajax update behaviors are no longer called, could you
provide a snipplet of how it should be setup?
Im doing this now
you should use org.apache.wicket.datetime.markup.html.form.DateTextField in
wicket-datetime, not the one from wicket-extensions ;)
concerning your approach for the additional renderer:
i think that's the way to go, since you can't just simply render such a call
to the head section of the page,
@DateTextField
Hmm, I have to supply a custom converter then. Could there be a default
one in the YUI extension?
How does your dateconverter look like?
regards Nino
Gerolf Seitz wrote:
you should use org.apache.wicket.datetime.markup.html.form.DateTextField in
wicket-datetime, not the one
ahh didnt see the PatternDateConverter...:)
Nino Saturnino Martinez Vazquez Wael wrote:
@DateTextField
Hmm, I have to supply a custom converter then. Could there be a
default one in the YUI extension?
How does your dateconverter look like?
regards Nino
Gerolf Seitz wrote:
you should
On 10/2/07, Gerolf Seitz [EMAIL PROTECTED] wrote:
you should use org.apache.wicket.datetime.markup.html.form.DateTextField in
wicket-datetime, not the one from wicket-extensions ;)
I didn't read the whole discussion, but the date picker is designed so
that it should function with other text
hi nino,
@ your problem:
if there is no model which can be updated (ie with an
AjaxFormComponentUpdatingBehavior), so wicket doesn't know what happened on
the client side. as a consequence the calendar is initialized with the
default dates.
are we talking about a standalone calendar with an
Im having trouble finding out how popups are actually done. It does not
look at it is setup like this:
http://developer.yahoo.com/yui/examples/calendar/popup.html
Or it's either merged deep in some of the js scripts bundled..
It doesn't actually really popup like windows do. It's an element
nino filed WICKET-979 and i've attached a patch that should allow what
nino
wants to achieve.
basically it adds two new options for configuring the datepicker:
boolean hideOnSelect() and boolean renderOnLoad()
Ah, that sounds fantastic!
heh, i'm thinking about a detection-mechanism
Hi Gerolf
It should be pretty easy to implement right?
Should I make a patch if I can?
regards Nino
Gerolf Seitz wrote:
from the top of my head i'd say it's not yet possible.
yould you please file a RFE? thanks.
gerolf
On 9/14/07, Nino.Martinez [EMAIL PROTECTED] wrote:
Hi
Im
yeah, patches are always welcome (and increases the chances for the issue to
be processed, although no guarantee for that ;) )
gerolf
On 9/14/07, Nino.Martinez [EMAIL PROTECTED] wrote:
Hi Gerolf
It should be pretty easy to implement right?
Should I make a patch if I can?
regards Nino
32 matches
Mail list logo