On Fri, Dec 14, 2012 at 1:57 PM, Nick Pratt nbpr...@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
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
Hi,
On Fri, Dec 14, 2012 at 9:19 AM, Martin Grigorov mgrigo...@apache.orgwrote:
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
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
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
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
the Datepicker component?
Tom
-Original Message-
From: Nick Pratt [mailto:nbpr...@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
-
From: Nick Pratt [mailto:nbpr...@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
@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
component?
Tom
-Original Message-
From: Nick Pratt [mailto:nbpr...@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
: 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
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 michael.ha...@1und1.de wrote:
I think
12 matches
Mail list logo
