hmm tricky
But i am done with api changes and i think the current code is pretty stable
so
[X] Create rc1 on Sunday
But i am fine with an extra beta if others find that necessary
johan
On 10/30/07, Frank Bille [EMAIL PROTECTED] wrote:
Hey all,
I have time to build a release on Sunday. So
[x] Create rc1 on Sunday
-igor
Hi,
after creating yet another WebMarkupContainer to allow a ajaxified
resultset, i wondered why we are forced to this? - I mean, im not a JS
guru, but why do we have to create abstract containers to let some
content change? I know that we need a hook (namely an tag with id) but
couldnt this
a patch is welcome :)
-igor
On 10/30/07, Korbinian Bachl [EMAIL PROTECTED] wrote:
Hi,
after creating yet another WebMarkupContainer to allow a ajaxified
resultset, i wondered why we are forced to this? - I mean, im not a JS
guru, but why do we have to create abstract containers to let some
I know Igor :)
but im currently in the situation where im not sure if it would work...
furthermore, im not sure how to access the new generated page as well as
accessing the old page (or better said: the markup of it)
Igor Vaynberg schrieb:
a patch is welcome :)
-igor
On 10/30/07,
[x] Create rc1 on Sunday
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/
i'm all for
[x] Create rc1 on Sunday
martijn, frank,
since you two build the actual releases,
have you had time to look at (and try out) the patch i provided in
https://issues.apache.org/jira/browse/WICKET-952 ?
it should generate a working wicket site generate with the
maven-site-plugin.
Korbinian Bachl wrote / napísal(a):
Hi,
Hi
after creating yet another WebMarkupContainer to allow a ajaxified
resultset, i wondered why we are forced to this? - I mean, im not a JS
guru, but why do we have to create abstract containers to let some
content change?
You need to create
