yeah, all that api is public. you can install your own IMarkupFilter that
does what you want. of course it will badly conflict with components that
werent written with this in mind, thus why this is a bad idea.
-igor
On 4/23/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Imo, that would only
Imo, that would only mean confusion. But if you want to interpret
normal ids as Wicket ids as well, you might be able to do so if you
would be willing to dig deep.
Eeloc
On 4/23/07, Bruno Borges <[EMAIL PROTECTED]> wrote:
I know these reasons Igor. Is just that for very simple cases, it would
I know these reasons Igor. Is just that for very simple cases, it would be
handy if wicket could lookup for ids, if wicket:id is not there.
On 4/24/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
there are a lot of reasons for this. the few that come to mind are:
designers want control over the i
there are a lot of reasons for this. the few that come to mind are:
designers want control over the id attribute for css styling
wicket:id allows duplicates in markup while id doesnt, so validation would
fail.
is allowed.
it is cleaner to use our own namespaced attribute to avoid interference
I couldn't find any thread related to this in the archives, probably because
the terms "id", "style" and "wicket:id" :)
But, did anyone ever asked to Wicket just use the style id instead wicket:id
to bind components? If yes, where is the thread? If not, ... why not allow
this? :D
Cheers!
PS: I p
Hi,
I've searched the mailing list for this, and looked at implementing
classes etc, but I fail to see the use case for
IFormProcessingListener.
Can anyone enlighten me and give me a concrete example of where this
is useful AND needed (meaning that it is utterly impossible to
implement it withou
This is a vote to release our first official incubator release into
the wild. The intent is to release Apache Wicket 1.3.0 beta1 to the
general Wicket community. Most API breaks are in, and we expect no
major changes in the final stages of this release.
With any release done inside the Apache Fou
Thx, should be fixed now.
Martijn
On 4/23/07, Jon Steelman <[EMAIL PROTECTED]> wrote:
FYI - The last bullet from the first list on the Welcome section on
the home page says "Download Wicket 1.2.5" when it should say 1.2.6.
Jon
--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join
FYI - The last bullet from the first list on the Welcome section on
the home page says "Download Wicket 1.2.5" when it should say 1.2.6.
Jon
Could you please open up a JIRA issue to avoid that this gets lost in
the archives (and let's hope it doesn't get lost in JIRA either,
looking at our current back log). Even if it turns out to be not a
bug, we can use JIRA as our TODO list.
Eelco
On 4/20/07, fattymelt <[EMAIL PROTECTED]> wrote:
Guys, have someone played with Ext-js? It appears to be an impressive
collection of UI Ajax components.
http://extjs.com/deploy/ext/docs/index.html
Among the other things controls are skinnable with a theme and you can
choose the underling library between Yahoo UI Library or jQuery or Prototype
> Why didn't you just roll back to the previous revision? Or asked me to
> do this? I wouldn't have committed if I knew you wanted to create a
> release for 1.3 this weekend as well.
Because I didn't know what the script solved. It was there for a
reason and the issue was not resolved. Instead of
12 matches
Mail list logo
