You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Ernesto Reinaldo Barreiro <re...@gmail.com> on 2012/12/12 20:04:50 UTC

new wicket extensions

Hi,

In discussion at

http://apache-wicket.1842946.n4.nabble.com/a-question-on-different-data-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>

Re: IAjaxRegionMarkupIdProvider

Posted by Martin Grigorov <mg...@apache.org>.
Hi Michael,


On Thu, Dec 13, 2012 at 11:36 PM, Michael Mosmann <mi...@mosmann.de>wrote:

> Hi,
>
> .. maybe someone has a better idea. What's the problem.
>
> One can add a behavior to a component which implements
> IAjaxRegionMarkupIdProvider. This way it's very easy to include some
> content rendered by this behavior even in an ajax-response (see
> http://www.wicket-praxis.de/**blog/2011/05/18/wicket-ajax-**
> iajaxregionmarkupidprovider/<http://www.wicket-praxis.de/blog/2011/05/18/wicket-ajax-iajaxregionmarkupidprovider/>(german only)). But if the component is invisible, the behavior is not
> called except the IAjaxRegionMarkupIdProvider call.
>
> So whatever the behavior does in beforeRender()/afterRender() (wicket
> 1.5.x), it will not be asked again, except for the markup id.
>
> Ok.. some examples:
>
> <body>
>   <wicket:container wicket:id="panel"></wicket:**container>
> </body>
>
> could be rendered to (if visible):
>
> <body>
>     <div id="panel1_mybehavior">
>         <wicket:container id="panel1" wicket:id="panel"></wicket:**
> container>
>     </div>
> </body>
>
> but will be rendered to (if invisible (**setOutputMarkupPlaceholderTag(**
> true)):
>
> <body>
>      <wicket:container id="panel1" wicket:id="panel"
> style="display:none"></wicket:**container>
>

I think a warning log message is logged when the application code tries to
set a markup id for a ComponentTag which wont be rendered, like
<wicket:container> or any HTML element connected to a Java Component with
#setRenderBodyOnly(true).
This warning tells you that there is something wrong.


> </body>
>
> which is in production should simply this:
>
> <body>
>
> </body>
>
> but is (Bug in renderPlaceholderTag?)
>
> <body>
>      <wicket:container id="panel1" style="display:none"></wicket:**
> container>
> </body>
>
> Ok. Here is what i would like to achive:
> - you can update a component via ajax no matter which tag the component is
> bound
>

By default Wicket removes all <wicket:xyz> elements in production mode, so
it is not possible later to replace a non-existing element :-/


> - it should work with invisible components
> - i would like to avoid any additional WebMarkupContainer
>

I think the solution to your problem is to avoid using <wicket:container>.
<wicket:container> is a shortcut of <div> + a Component with
#setRenderBodyOnly(true). So just use a <div> instead and all should be
good.


>
> Any idea?
> It is a bug (wicket 1.5.9 - i can do a quickstart)?
>
> thank you:)
> Michael
>
>
>
>
>


-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>

IAjaxRegionMarkupIdProvider

Posted by Michael Mosmann <mi...@mosmann.de>.
Hi,

.. maybe someone has a better idea. What's the problem.

One can add a behavior to a component which implements 
IAjaxRegionMarkupIdProvider. This way it's very easy to include some 
content rendered by this behavior even in an ajax-response (see 
http://www.wicket-praxis.de/blog/2011/05/18/wicket-ajax-iajaxregionmarkupidprovider/ 
(german only)). But if the component is invisible, the behavior is not 
called except the IAjaxRegionMarkupIdProvider call.

So whatever the behavior does in beforeRender()/afterRender() (wicket 
1.5.x), it will not be asked again, except for the markup id.

Ok.. some examples:

<body>
   <wicket:container wicket:id="panel"></wicket:container>
</body>

could be rendered to (if visible):

<body>
     <div id="panel1_mybehavior">
         <wicket:container id="panel1" wicket:id="panel"></wicket:container>
     </div>
</body>

but will be rendered to (if invisible (setOutputMarkupPlaceholderTag(true)):

<body>
      <wicket:container id="panel1" wicket:id="panel" 
style="display:none"></wicket:container>
</body>

which is in production should simply this:

<body>

</body>

but is (Bug in renderPlaceholderTag?)

<body>
      <wicket:container id="panel1" style="display:none"></wicket:container>
</body>

Ok. Here is what i would like to achive:
- you can update a component via ajax no matter which tag the component 
is bound
- it should work with invisible components
- i would like to avoid any additional WebMarkupContainer

Any idea?
It is a bug (wicket 1.5.9 - i can do a quickstart)?

thank you:)
Michael





Re: new wicket extensions

Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
Hi,

IMHO having a wider set of "official" rich components would not hurt
either...


On Thu, Dec 13, 2012 at 9:08 PM, Martin Sachs <sa...@gmail.com>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)
> > <to...@alaska.gov> 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:nbpratt@gmail.com]
> >> Sent: Thursday, December 13, 2012 5:25 AM
> >> To: dev@wicket.apache.org
> >> 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 <mgrigorov@apache.org
> >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 <
> >>> reiern70@gmail.com> 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/>
> >>>
>
>


-- 
Regards - Ernesto Reinaldo Barreiro
Antilia Soft
http://antiliasoft.com/ <http://antiliasoft.com/antilia>

Re: new wicket extensions

Posted by Maarten Bosteels <mb...@gmail.com>.
On Fri, Dec 14, 2012 at 1:57 PM, Nick Pratt <nb...@gmail.com> wrote:

> Jquery-ui vs bootstrap vs another doesn't matter to me - as long as I can
> get something functional as soon as I can and then worry about tweaking
> components later on
>

+1

Re: new wicket extensions

Posted by Nick Pratt <nb...@gmail.com>.
If we take that view everyone rolls their own and repeats the same thing.
While I've added new components I'd rather use pre packaged ones, swapping
out the components for alternates as and when we need to for improved
functionality / appearance.

When learning / working with a framework I don't want to spend time
wondering if my code isn't working because of a home made component but
rather assume the up to date packaged components work and its likely my
usage that's at fault. I have this confidence for textfield,
dropdownchoice, datatable etc. but not for the JS based ones.

Some of the other libs aren't kept up to date. If one of those jquery ui
based libs was built immediately after Wicket builds it would help.  I've
already hit odd behavior with wiquery and wicket 6.3 which was resolved by
using the latest jquery-ui ultimately removing wiquery. I'd rather not do
that.

As a framework trying to appeal to a broad base of users I think we should
provide a good base of components.  The flexibility of Wicket is already
there - if you know how to use it - but there's quite a learning curve.

Jquery-ui vs bootstrap vs another doesn't matter to me - as long as I can
get something functional as soon as I can and then worry about tweaking
components later on. If wicket-bootstrap was to become a core supported lib
then I'd switch my current project purely from a support standpoint and
belief that as a core lib it would have broader usage, generate more
questions etc.

Why don't we put together a survey to ask folks?

N
On Dec 14, 2012 3:20 AM, "Martin Grigorov" <mg...@apache.org> wrote:

> My personal experience is like Martin Sachs' one.
> So far the projects I was working on never used the pre-build rich
> components because they didn't fit the "company standards" either because
> of the used technology or because of the UI mismatch.
>
> I think the current YUI datetime component needs a change because:
> - it uses YUI 2.x which is no more supported
> - Wicket comes with jQuery by default and using YUI for a widget just
> contributes to the slower responses
>
> Why I think Apache Wicket doesn't need its own date component ?
> Because there are several out there already (wiquery, wicket-jquery-ui,
> wicket-bootstrap, jqwicket, jwicket, ....)
>
> Maybe we should adopt some of those ?
> If we decide to do that then we have to invite their developers too because
> at the moment we have no resources to maintain it ourselves.
>
> Few months ago I was in favour of jQueryUI, lately I like Twitter Bootstrap
> more and more, and I'm not sure what new fancy JS UI library will arise
> next year, that's why I think Wicket should not provide "default" UI
> widgets by itself. The above listed libraries do this good enough. Some
> users prefer WiQuery, other - Wicket Bootstrap, third prefer to make their
> own components ...
>
>
>
> On Fri, Dec 14, 2012 at 1:23 AM, tetsuo <ro...@gmail.com> wrote:
>
> > Wicket already uses jquery for its ajax support. A jquery-ui module
> > (thus the dependency to jquery-ui.js) would be completely optional, as
> > is the embedded yui library currently used by wicket-extensions.
> >
> >
> >
> > On Thu, Dec 13, 2012 at 8:29 PM, Michael Haitz <mi...@1und1.de>
> > wrote:
> > > I think wicket should only provide basic components without
> dependencies
> > to keep clean and simple (and extendable). Libraries like jquery-ui or
> > bootstrap would break this and everyone who wants to use wicket has to
> use
> > the choosen ui lib too. And there isn't a "all in one" lib suitable for
> > every purpose.
> >
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com <http://jweekend.com/>
>

Re: new wicket extensions

Posted by Martin Grigorov <mg...@apache.org>.
Hi Ernesto,

I personally can file issues to your projects, send pull requests, etc. but
I cannot judge whether your project is good enough to be a "satellite"
project.
Such "satellite" projects should prove themselves naturally. They have to
build their community, they have to provide communication channels for
their users, etc.
WicketStuff indeed contains projects with different quality. The benefit of
being part of WS is that the project is released regularly and that its
issues/pull requests can be processed by another contributor in WS.

What we can do is to add links to related projects at
http://wicket.apache.org with a description, links to their main site,
mailing lists, issue trackers, ...
For example in http://wicket.apache.org/learn/projects/

If you like the idea then checkout the site files from
https://svn.apache.org/repos/asf/wicket/common/site/trunk and send us a
patch

On Fri, Dec 14, 2012 at 10:47 AM, Ernesto Reinaldo Barreiro <
reiern70@gmail.com> wrote:

> Hi,
>
> On Fri, Dec 14, 2012 at 9:19 AM, Martin Grigorov <mgrigorov@apache.org
> >wrote:
>
> > My personal experience is like Martin Sachs' one.
> > So far the projects I was working on never used the pre-build rich
> > components because they didn't fit the "company standards" either because
> > of the used technology or because of the UI mismatch.
> >
>
> But  for other companies having an "official" set of rich components, that
> could be easily customized to satisfy not so strict standards, would be a
> great plus. Mind that I write "official" meaning by that that they do not
> need to be hosted or maintained by core wicket developers but on
> a satellite project that is "mentored" by core developers and that follows
> the same release schedules that wicket does. The closest thing to that now
> is wicket-stuff. But IMHO that project is too open and there are projects
> of many different quality levels hosted under the same "umbrella".  So, IMO
> a satellite project, where successful-well-maintained-mature projects would
> be invited to join in, is needed and it will be welcomed by the community.
>
>
> > I think the current YUI datetime component needs a change because:
> > - it uses YUI 2.x which is no more supported
> > - Wicket comes with jQuery by default and using YUI for a widget just
> > contributes to the slower responses
> >
> > Why I think Apache Wicket doesn't need its own date component ?
> > Because there are several out there already (wiquery, wicket-jquery-ui,
> > wicket-bootstrap, jqwicket, jwicket, ....)
> >
>
> Not needed to "pollute" core... if some of those projects are invite to
> join satellite project.
>
>
> > Maybe we should adopt some of those ?
> > If we decide to do that then we have to invite their developers too
> because
> > at the moment we have no resources to maintain it ourselves.
>
> Few months ago I was in favour of jQueryUI, lately I like Twitter Bootstrap
> > more and more, and I'm not sure what new fancy JS UI library will arise
> > next year, that's why I think Wicket should not provide "default" UI
> > widgets by itself. The above listed libraries do this good enough. Some
> > users prefer WiQuery, other - Wicket Bootstrap, third prefer to make
> their
> > own components ...
> >
> >
> No need to discard anything useful and good quality....
>
>
> --
> 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/>

Re: new wicket extensions

Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
Hi,

On Fri, Dec 14, 2012 at 9:19 AM, Martin Grigorov <mg...@apache.org>wrote:

> My personal experience is like Martin Sachs' one.
> So far the projects I was working on never used the pre-build rich
> components because they didn't fit the "company standards" either because
> of the used technology or because of the UI mismatch.
>

But  for other companies having an "official" set of rich components, that
could be easily customized to satisfy not so strict standards, would be a
great plus. Mind that I write "official" meaning by that that they do not
need to be hosted or maintained by core wicket developers but on
a satellite project that is "mentored" by core developers and that follows
the same release schedules that wicket does. The closest thing to that now
is wicket-stuff. But IMHO that project is too open and there are projects
of many different quality levels hosted under the same "umbrella".  So, IMO
a satellite project, where successful-well-maintained-mature projects would
be invited to join in, is needed and it will be welcomed by the community.


> I think the current YUI datetime component needs a change because:
> - it uses YUI 2.x which is no more supported
> - Wicket comes with jQuery by default and using YUI for a widget just
> contributes to the slower responses
>
> Why I think Apache Wicket doesn't need its own date component ?
> Because there are several out there already (wiquery, wicket-jquery-ui,
> wicket-bootstrap, jqwicket, jwicket, ....)
>

Not needed to "pollute" core... if some of those projects are invite to
join satellite project.


> Maybe we should adopt some of those ?
> If we decide to do that then we have to invite their developers too because
> at the moment we have no resources to maintain it ourselves.

Few months ago I was in favour of jQueryUI, lately I like Twitter Bootstrap
> more and more, and I'm not sure what new fancy JS UI library will arise
> next year, that's why I think Wicket should not provide "default" UI
> widgets by itself. The above listed libraries do this good enough. Some
> users prefer WiQuery, other - Wicket Bootstrap, third prefer to make their
> own components ...
>
>
No need to discard anything useful and good quality....


-- 
Regards - Ernesto Reinaldo Barreiro
Antilia Soft
http://antiliasoft.com/ <http://antiliasoft.com/antilia>

Re: new wicket extensions

Posted by Martin Grigorov <mg...@apache.org>.
My personal experience is like Martin Sachs' one.
So far the projects I was working on never used the pre-build rich
components because they didn't fit the "company standards" either because
of the used technology or because of the UI mismatch.

I think the current YUI datetime component needs a change because:
- it uses YUI 2.x which is no more supported
- Wicket comes with jQuery by default and using YUI for a widget just
contributes to the slower responses

Why I think Apache Wicket doesn't need its own date component ?
Because there are several out there already (wiquery, wicket-jquery-ui,
wicket-bootstrap, jqwicket, jwicket, ....)

Maybe we should adopt some of those ?
If we decide to do that then we have to invite their developers too because
at the moment we have no resources to maintain it ourselves.

Few months ago I was in favour of jQueryUI, lately I like Twitter Bootstrap
more and more, and I'm not sure what new fancy JS UI library will arise
next year, that's why I think Wicket should not provide "default" UI
widgets by itself. The above listed libraries do this good enough. Some
users prefer WiQuery, other - Wicket Bootstrap, third prefer to make their
own components ...



On Fri, Dec 14, 2012 at 1:23 AM, tetsuo <ro...@gmail.com> wrote:

> Wicket already uses jquery for its ajax support. A jquery-ui module
> (thus the dependency to jquery-ui.js) would be completely optional, as
> is the embedded yui library currently used by wicket-extensions.
>
>
>
> On Thu, Dec 13, 2012 at 8:29 PM, Michael Haitz <mi...@1und1.de>
> wrote:
> > I think wicket should only provide basic components without dependencies
> to keep clean and simple (and extendable). Libraries like jquery-ui or
> bootstrap would break this and everyone who wants to use wicket has to use
> the choosen ui lib too. And there isn't a "all in one" lib suitable for
> every purpose.
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>

Re: new wicket extensions

Posted by tetsuo <ro...@gmail.com>.
Wicket already uses jquery for its ajax support. A jquery-ui module
(thus the dependency to jquery-ui.js) would be completely optional, as
is the embedded yui library currently used by wicket-extensions.



On Thu, Dec 13, 2012 at 8:29 PM, Michael Haitz <mi...@1und1.de> wrote:
> I think wicket should only provide basic components without dependencies to keep clean and simple (and extendable). Libraries like jquery-ui or bootstrap would break this and everyone who wants to use wicket has to use the choosen ui lib too. And there isn't a "all in one" lib suitable for every purpose.

Re: new wicket extensions

Posted by Michael Haitz <mi...@1und1.de>.
I think wicket should only provide basic components without dependencies to keep clean and simple (and extendable). Libraries like jquery-ui or bootstrap would break this and everyone who wants to use wicket has to use the choosen ui lib too. And there isn't a "all in one" lib suitable for every purpose. 

michael



Am 13.12.2012 um 22:19 schrieb "tetsuo" <ro...@gmail.com>:

> 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 <sa...@gmail.com> 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)
>>> <to...@alaska.gov> 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:nbpratt@gmail.com]
>>>> Sent: Thursday, December 13, 2012 5:25 AM
>>>> To: dev@wicket.apache.org
>>>> 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 <mg...@apache.org>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 <
>>>>> reiern70@gmail.com> 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/>
>> 

Re: new wicket extensions

Posted by tetsuo <ro...@gmail.com>.
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 <sa...@gmail.com> 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)
>> <to...@alaska.gov> 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:nbpratt@gmail.com]
>>> Sent: Thursday, December 13, 2012 5:25 AM
>>> To: dev@wicket.apache.org
>>> 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 <mg...@apache.org>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 <
>>>> reiern70@gmail.com> 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/>
>>>>
>

Re: new wicket extensions

Posted by Martin Sachs <sa...@gmail.com>.
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)
> <to...@alaska.gov> 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:nbpratt@gmail.com]
>> Sent: Thursday, December 13, 2012 5:25 AM
>> To: dev@wicket.apache.org
>> 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 <mg...@apache.org>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 <
>>> reiern70@gmail.com> 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/>
>>>


Re: new wicket extensions

Posted by tetsuo <ro...@gmail.com>.
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)
<to...@alaska.gov> 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:nbpratt@gmail.com]
> Sent: Thursday, December 13, 2012 5:25 AM
> To: dev@wicket.apache.org
> 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 <mg...@apache.org>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 <
>> reiern70@gmail.com> 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/>
>>

RE: new wicket extensions

Posted by "Burton, Tom F (DOR)" <to...@alaska.gov>.
+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:nbpratt@gmail.com] 
Sent: Thursday, December 13, 2012 5:25 AM
To: dev@wicket.apache.org
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 <mg...@apache.org>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 < 
> reiern70@gmail.com> 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/>
>

Re: new wicket extensions

Posted by Nick Pratt <nb...@gmail.com>.
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 <mg...@apache.org>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 <
> reiern70@gmail.com> wrote:
>
> > Hi,
> >
> > In discussion at
> >
> >
> >
> http://apache-wicket.1842946.n4.nabble.com/a-question-on-different-data-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/>
>

Re: new wicket extensions

Posted by Martin Grigorov <mg...@apache.org>.
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 <
reiern70@gmail.com> wrote:

> Hi,
>
> In discussion at
>
>
> http://apache-wicket.1842946.n4.nabble.com/a-question-on-different-data-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/>