On 2/15/07, ChuckDeal <[EMAIL PROTECTED]> wrote: > > I was trying to use the datetime.DateTextField and it was giving me a little > grief when I was trying to use DateTime objects with it. It was my > understanding that that datetime project was to be built around the joda > package. Here is a patch the removes the java.util.Date "stuff" in an > attempt to be a pure DateTime converter. > > With the following patch in place, my code works properly (ie, no errors > parsing or returning dates). Let me know if I'm on the wrong track here, > please.
Hmmmm. Yeah, I can see your point. My - original - idea was to use Joda-time internally and have this thing work for normal java.util.Dates transparently. I think the best way to do here is to create another converter, the other one being fully based on joda time and build a separate text field for it etc. I definitively want to support normal dates, but I realize it's quite logical to expect wicket-datetime to work with joda-time all the way as well. What do you think? Eelco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
