With the risk of hijacking the thread. It's really easy registering new
stuff with the parser, I recently had a look at something in the
formcomponent hieracy, and you just call a method or 2 to register new
tags.. :)
James Carman wrote:
That's my opinion, also. I voted -1 to removing wicket
thanks
-igor
On Mon, Nov 24, 2008 at 10:51 PM, Jeremy Thomerson
<[EMAIL PROTECTED]> wrote:
> Accepted. I'm going to add something to the 1.4 migration guide.
>
> Thanks!
>
> On Tue, Nov 25, 2008 at 12:47 AM, Igor Vaynberg <[EMAIL PROTECTED]>wrote:
>
>> the change is to make that component work c
Accepted. I'm going to add something to the 1.4 migration guide.
Thanks!
On Tue, Nov 25, 2008 at 12:47 AM, Igor Vaynberg <[EMAIL PROTECTED]>wrote:
> the change is to make that component work consistently with how all
> other components work. an id only constructor will look for a compound
> pro
the change is to make that component work consistently with how all
other components work. an id only constructor will look for a compound
property model like all the other components.
the change is basically to get rid of legacy cruft. when this
component was first written it didnt have an option
Igor,
It has come up a couple of times on the user list, but in 1.4rc1 there was
a change to FileUploadField to make it always use a model. Now, the new
FileUploadField("id") constructor is practically useless, and I would
venture to say that tons of apps out there (like mine do in numerous
plac
[X] - YES - I would like to see at least the most used Wicket Stuff
projects structured so that they mirror Wicket, and a release is
produced for each Wicket release.
This should be a no-brainer ;o)
-Original Message-
From: Jeremy Thomerson [mailto:[EMAIL PROTECTED]
Sent: Monday, Novembe
[ X ] - YES - I would like to see at least the most used Wicket Stuff projects
structured so that they mirror Wicket, and a release is produced for each
But I also believe this is how it are today sort of anyway not so
strict, but cool with me.. Igor did a branch when the initial release of
1-4
[X] - YES - I would like to see at least the most used Wicket Stuff
projects
structured so that they mirror Wicket, and a release is produced for
each
Wicket release.
Sounds like a good idea, if you can get enough WS projects to actively
participate. My concern would be waning interest.
Hello everyone,
I would like to get your opinion on an idea regarding the Wicket Stuff
project(s). As you are familiar with, Wicket Stuff is where anyone can
create anything related to Wicket, small or large. One problem that new
users of Wicket (and us "old" users) come across is that there is
