Well, I don't think drag-and-drop modal tree tables are essential to any widget toolkit, but date pickers and modal dialogs are. It's fairly easy to integrate javascript libraries (like jquery-ui) to wicket, but it surely demands some work to do it.
I try to sell Wicket to enterprise developers, since it is the market I work for. We often don't have the requirement of pixel-perfect design fidelity to a designer's vision, so the pre-built components, with some style tuning, are more than enough (even the ugly Wicket-built-in-ModalWindow). And a set of out-of-the-box components are a nice productivity boost. And, in this market, being an official (or officially 'blessed') library is important, and breaks many barriers. Saying to your manager that it is not maintained by some random guy of the Internet, but by Apache, makes a huge difference. On Thu, Dec 13, 2012 at 6:08 PM, Martin Sachs <[email protected]> wrote: > hi, > > you sell wicket to people, that want to have rich components ? > > We developing an application for an enterprise with wicket and have no > need for rich component, because we need to create a page in a specific > design from a design agency. no rich component library has the > flexibility to meet the need of the customer (i know that from jsf and > its primefaces or whatever). With wicket its quite easy to create all > widgets you need, yourself in a very short time. > > People who just create small sites could probably have little need for > this, but only for at the beginning of a project-lifecycle > > just my 2 cents > > > Am 13.12.2012 20:33, schrieb tetsuo: >> What about home-baking or incorporating (if donated, obviously) a >> library that integrates jquery-ui components into an official >> wicket-jqueryui or wicket-widgets project? >> >> When I'm trying to sell Wicket to people, one thing they always >> complain is that it lacks a rich component library (sf.net and >> googlecode projects don't count). >> Having jquery-ui pre-integrated would be a huge win. >> >> >> >> >> On Thu, Dec 13, 2012 at 4:34 PM, Burton, Tom F (DOR) >> <[email protected]> wrote: >>> +1 I would like to see a Date/Time/Picker remain a part of core as well. >>> >>> However, I find myself getting confused are we talking about. >>> >>> Are we talking about one of the full blown fields on the Dates example page? >>> http://www.wicket-library.com/wicket-examples/dates/ >>> Or are we just talking about the Datepicker component? >>> >>> Tom >>> >>> >>> -----Original Message----- >>> From: Nick Pratt [mailto:[email protected]] >>> Sent: Thursday, December 13, 2012 5:25 AM >>> To: [email protected] >>> Subject: Re: new wicket extensions >>> >>> Since most data entry forms Ive seen involve dates, a well supported >>> datetime component as part of the core wicket distribution, based on >>> jquery-ui, released in lock-step with the other core wicket JARs, would >>> IMHO, be most beneficial. It would reduce barriers to entry, provide a >>> common good looking, functional datetime component that would work for 90%+ >>> of the cases, that most people would use, understand, and be able to debug >>> and support. >>> >>> It doesn't preclude the use of other date time components, but as a >>> developer using a framework, I prefer common supported out-of-the-box >>> components to other libs. >>> >>> N >>> >>> On Thu, Dec 13, 2012 at 3:45 AM, Martin Grigorov >>> <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> Here is my opinion on this topic >>>> >>>> Option 5) Deprecate wicket-datetime and move it in WicketStuff when >>>> Wicket >>>> 7 is released. >>>> If someone needs a date picker there are several other options: >>>> - wiquery >>>> - wicket-jquery-ui >>>> - wicket-bootstrap >>>> >>>> >>>> >>>> On Wed, Dec 12, 2012 at 8:04 PM, Ernesto Reinaldo Barreiro < >>>> [email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> In discussion at >>>>> >>>>> >>>>> >>>> http://apache-wicket.1842946.n4.nabble.com/a-question-on-different-dat >>>> a-grid-components-available-for-wicket-tt4654273.html >>>>> Martin Grigorov mentioned that maybe it is time to improve >>>>> wicket-datetime. >>>>> >>>>> I see following possibilities. >>>>> >>>>> 1- Try to upgrade to more resent version of YUI. >>>>> 2- Try to rewrite wicket-date.js "in terms" of jquery, now that >>>>> wicket 6.0.x is jquery based. Similarly to what it has been done >>>>> for inMethod grid. This has the advantage that "existing >>>>> functionality" will not >>>> break. >>>>> 3- Replace, or provide an alternative to, wicket-date.js rolling out >>>>> a component based on one of the (many) existing jquery based date pickers. >>>>> 4- Any other option? >>>>> >>>>> What would be the most useful thing to do? >>>>> >>>>> In case of option [3]. >>>>> >>>>> What would be a good jquery based replacement/alternative for >>>>> wicket-datetime? >>>>> >>>>> >>>>> 1-http://jqueryui.com/datepicker/? Maybe also >>>>> http://trentrichardson.com/examples/timepicker/ >>>>> 2-http://www.kelvinluck.com/assets/jquery/datePicker/v2/demo/ >>>>> 3-http://keith-wood.name/datepick.html >>>>> 4-http://www.eyecon.ro/datepicker/ >>>>> 4-Others? >>>>> >>>>> >>>>> Also see >>>>> http://www.tripwiremagazine.com/2012/08/jquery-datepicker.html >>>>> >>>>> -- >>>>> Regards - Ernesto Reinaldo Barreiro >>>>> Antilia Soft >>>>> http://antiliasoft.com/ <http://antiliasoft.com/antilia> >>>>> >>>> >>>> >>>> -- >>>> Martin Grigorov >>>> jWeekend >>>> Training, Consulting, Development >>>> http://jWeekend.com <http://jweekend.com/> >>>> >
