In each basic component like Check, CheckBox, CheckGroupSelector,
DropDownChoice, Form, FormComponentLabel, Radio, Textfield etc, checks are
performed in the onComponentTag method:
example:
checkComponentTag(tag, input);
checkComponentTagAttribute(tag, type,
This way you could create a generic Panel component in which you could add
any component at RUNTIME ! ( by altering the markup fragments before
rendering ).
We are working on a framework project based on Wicket, named SENRO
(http://senro.codehaus.org). We want this to be something like Apple's
Also to note that I am talking about Wicket 2.0 !.
Flavius Burca wrote:
In each basic component like Check, CheckBox, CheckGroupSelector,
DropDownChoice, Form, FormComponentLabel, Radio, Textfield etc, checks are
performed in the onComponentTag method:
example:
why is it so big? complete wicket is 1.5 so only some date manipulations are
1/3th?
johan
On 2/2/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
Hi all,
For those who don't know, Joda Time: http://joda-time.sourceforge.net/
is a *much* better replacement of the Java date and time APIs it many
but that can then become:
examples.wicketstuff.org/wicket-1.2.x
examples.wicketstuff.org/wicket-1.x
examples.wicketstuff.org/trunk
?
Martijn
On 2/3/07, Johan Compagner [EMAIL PROTECTED] wrote:
looks good
only examples is not 1 we have 3 examples if everybody compiles and builds
fine (1.2/1.3
Eelco Hillenius a écrit :
And in case no-one is working on that anymore, what would be the best
date picker (with a compatible licence!) to start working on? Dojo?
YUI? ...?
Hi,
We've already done a datePicker in Dojo-Contrib (DojoDatePicker) with an
apache compatible license. If you are
This is a proposal to move some documentation that is written and
maintained by core developers to the WICKETxSITE. This gives our
official site more body and content.
Immediate moveable parts:
- migration guides
- ?
Martijn
--
Vote for Wicket at the
if you are building a bean panel what you can do is wrap the components in a
panel, and then insert the panel instead.
so have a TextFieldPanel that wraps a textfield and feeds it the markup
wicket:panelinput wicket:id=tf type=text//wicket:panel
does that not work for you?
also see
actually if you look closer the discussion was around a thread that was on
wicket-private regarding a datepicker.
-igor
On 2/3/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
On 2/3/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
...I saw a lot of traffic on ##wicket on license compatibility
First, congratulations for the great work that you did on
refactoring URL generation in Wicket. Seems to work great.
However launching the examples is now far slower than before,
because you parse web.xml for every WebApplication.
Therefore I suggest to compute the filter path in
Hi all,
This is a followup about WICKET-126 Reload Java Classes for
Improved Developer Experience
Please apply
https://issues.apache.org/jira/secure/attachment/12349956/20070114-wicket-1.x-ReloadingWicketFilter
It adds Javadoc to explain how to activate reloading, and it adds
support for
good idea. similar to the wicket-spring module.
On 2/3/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
-1 for core
+0 for extensions
+1 for a wicket-joda core module
extensions is getting pretty big, its hard to find things. if i am using
joda in my project and see wicket-joda i immediately know
Yeah, that's kind of the problem. We had the same issue with YUI. I
think YUI is a very cool library, but the sizes of the javascripts are
pretty big. So, the Dojo and YUI alternatives are great to have (and
could be advertised more imo) but as a default component, we would
ideally be looking for
Yes, I know this, but the idea is not to wrap components in panels. My idea
is to create an empty Panel in which you can add any kind of component at
runtime ! This cannot be acheived right now because the onComponentTag()
method for standard components check to see if the HTML tag is suitable
Therefore I suggest to compute the filter path in a static block,
as web.xml is not supposed to change during the lifetime of the
app, nor between initialization of the various WicketFilters.
Usually, using static backfires in some way or the other.
I think wicket-example's startup time is
this wont work. some components react differently based on what tag they are
attached to.
take link. if attached to anchor it generates an href, if attached to input
submit it generates an onclick.
what you are suggesting is not future proof and i dont think we will
implement it.
-igor
On
if you want you can even create a mapping yourself using a map, so you have
input type=text - textfield
textarea - textarea
input type=checkbox - checkbox
but for beanpanels it is probably the cleanest to create a panel for every
kind of editor, that way you can have a panel for complex types
Igor Vaynberg wrote:
we already have a pull parser in wicket, why arent we using that?
Hmmm. Do we? It seemed like it was written for HTML. The code is
probably trivial - feel free to improve it, or point me in the right
direction to.
Al
( It's not done to disable the back button. )
For newbies, which will keep flooding in by the thousands, in particular,
up-to-date docs are essential. Otherwise they flood back just as fast.
- nilo
Al Maw wrote:
Hi all,
I've given http://wicketstuff.org a bit of love.
Let me know what
nilo de roock wrote:
I downloaded wicket-1.x
mvn install does not work ( see below )
Is there something wrong with the pom.xml, perhaps?
Please read and follow the instructions on the wiki, which point you to
this document:
Why? It is part of our documentation. It is maintained by wicket core
devs. There is no reason for it to be at the general wiki. The purpose
of our core site is to add content to it, not keep it a 2 pager.
Martijn
On 2/3/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
Imo, we could better just
If it is (at least almost) as easy to maintain then the WIKI, then
fine, so I guess we can see how well the confluence export (cause
that's still what we're going to do right? is there any work done on
documenting how that would work?) works, and if that works well, then
we can give our site some
On 2/3/07, Al Maw [EMAIL PROTECTED] wrote:
Eelco Hillenius wrote:
Al, are you seriously working on date picker you want to contribute to
Wicket?
Yes, but it's really not very far along yet and I don't think we should
hold up 1.3 for it (certainly not the first beta at least).
Cool. We don't
23 matches
Mail list logo
