i look at it differently. i see wicket-datetime as a collection of date/time-related components built around joda. only one of them is a datepicker and that just happens to be backed by yui. if i want to use a datepicker why would i need a dependency on the entire wicket-yui? i dont care what the datepicker is backed by. and why would wicket-yui contain a bunch of date/time related classes like textfields,etc?
-igor On 2/17/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 2/17/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > I would say don't add it in extentions > but add a special project wicket-yui > > and try to sync up with all the nice components they have there. > (including datetime) > > and if that is the case then if it was me, depricate datetime (if that one > is build on yui) > and have wicket-yui project/jar that gives you the date time. > I don't care that you get something extra. > one project pure for date time is a bit over kill if you ask me.... Yeah, that was kind of my idea behind option 1) Eelco
