On 8/22/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > Not yet, until now I prepared the markup loading process to be better > prepared for the change. The change we are talking about is not a > small change. It means to turn the render process inside out and I > thought that is planned for V3. IMO there will be no perfect solution > for V2 which is due in ~2 months.
Wicket 2.0 doesn't have to be release ready in two months though. What Martijn and I want is that the API - more specifically the common API for clients - is stable by then, so we don't have to rewrite portions of Wicket In Action. However, markup loading is internal for a large part, and even if would result in an API change, it would have an effect on one or two pages at most. So, *if* guys can, I'd say the sooner the better. It will probably save everyone time/ effort when we implement it just right this time instead of keeping on tweaking it. Now, I don't know how big you think this will be Juergen? How many days/ weeks of work you figure this will take? As it is such a crucial thing to Wicket, we'll find out right away when things stop working, so my guess is that we wouldn't need a lot of time of doing little tweak after fix after tweak? Eelco ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
