The problem at hand was : how to still have an html preview -before having all the logic implemented- for a complex page, when the page is technically separated into multiple parts/panels.
But now I see this question has no answers, and that is normal, due to the fact that the real types of the panels composing my complex page are not embarqued in the page itself. Since the wiring of the panels to the page is not done in the html markup itself, there's no way out. And I can see it's due to the fact that it is the components that drive their markups, and not the contrary, and that's great : much more power. Oh wait! Maybe I just ended to understand what is said in the Features page, when one writes about the difference between the Wicket & JSF philosophy ? On 11/4/05, Eduardo Rocha <[EMAIL PROTECTED]> wrote: > The fact that one cannot preview html only using panels without > running a web server means that java code it is mandatory. Do you > think this is a drawback to Wicket (as well as Tapestry) that claims > that designers and coders can work almost independently? > > 2005/11/3, Laurent PETIT <[EMAIL PROTECTED]>: > > On 11/3/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > > > in order to be pre-viewable the html editor must be able to find the > > > css file without the help of wicket. The easiest way to accomplish it > > > is to put the css into your source path and by means of <wicket:link> > > > (autolinks) wicket is able to find them at runtime. > > > > Ok, I understand that. > > But this does not solve the second issue, as you stated: > > > > > > > And also, I'd like to have this preview include the markup of nested > > > > > panels, > > > > > Is it possible in development mode ? > > > A html editor can not do it. The html editor does not know anything > > > about wicket and panel. > > > > Oh sorry, I just re-thought about it, and I clearly understand it cannot > > work. > > > > > > > This should be great, because it is hard to decompose a page into > > > > > logical parts without the hassle of maintaining in synch two tag > > > > > bodies or two <wicket:remove> elements. > > > ?!?! What is the question? > > > > No more questions, since I had the evidence that what I was thinking > > of isn't at all possible (since, of course, the associated panel > > markup is bound to the class of the panel, and in the parent markup, > > there is nothing special but a wicket:id attribute, which isn't > > sufficient to deduce the right nested markup file ...) > > > > Sorry for this one, > > > > -- > > Laurent > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: > > Tame your development challenges with Apache's Geronimo App Server. Download > > it for free - -and be entered to win a 42" plasma tv or your very own > > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > > _______________________________________________ > > Wicket-user mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
