wicket is very flexible, you just have to get used to it. composition is especially easy due to wicket's component oriented nature.

-Igor


On 3/15/06, Matthias Albert <[EMAIL PROTECTED]> wrote:

Igor Vaynberg schrieb:
> i would create a page that has the layout, add a label to that page with
> a model that streams the appropriate static page. that way you only have
> one wicket page that can display all the static ones.


But this layout page should be able to modify the static source pages to
inject a common top area and a menu-like link list (like in the
navomatic example) common only for each subdirectory.

Is this possible with Wicket?

>
> -Igor
>
>
> On 3/15/06, *Guillermo Castro* <[EMAIL PROTECTED]
> <mailto: [EMAIL PROTECTED]>> wrote:
>
>     Matthias,
>
>     I'm also in the early stages of learning wicket, but I thought I'd
>     throw my 2c.
>
>     If the 200+ pages are static, why can't you just keep them that way?
>     Wicket doesn't preclude you from having static
>     pages/images/resources. You can use Wicket only for the dynamic part
>     of the website and leave the rest as it is.
>
>     regards.
>
>
>     On 3/15/06, *Matthias Albert* < [EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>> wrote:
>
>         After some reading and experimenting with wicket, I am just
>         trying to
>         collect the steps that would be necessary to migrate  an web
>         application
>         (that used XSLT transformations) to wicket. There are several
>         questions
>         that I would like to ask.
>
>         I surely do not understand Wicket enough, these are all beginner's
>         questions.
>
>         The main characteristics are:
>
>         1. There are ca. 200 static HTML-Pages without any header and
>         navigation
>         elements. They are distributed over several subdirectories, the root
>         being WEBAPP/content.
>
>         My Question: How can the single root directory for all HTML pages be
>         configured? I found a IResourcePath and WebApplicationPath
>         class, but no
>         usage of it.
>
>         2. So far there were several XML pipelines to insert a header
>         block and
>         a navigation block on the left via XSLT transformations. The
>         navigation
>         block has links to all pages in a subdirectory and is the same
>         for all
>         pages in this subdirectory and is defined in a XML file
>         "siteindex.xml".
>
>         Question: Do I really have to write a class for every HTML page?
>         That
>         means about 200 classes that are all nearly the same! They all
>         could
>         extend a common base class and add nothing apart from their
>         classname.
>         I would be happy to write a class per subdirectory that could
>         evaluate
>         the siteindex.xml file and create a dynamic navigation
>         component. This
>         class could even be the same for all pages, if it could be
>         configured.
>
>         The HTML pages should remain unchanged. There should be no
>         wicket:id in
>         every HTML page for the header and navigation block, this should
>         rather
>         be done outside the pages. Maybe, I could write a XSLT preprocessor
>         stage to achieve that.
>
>         3. There will be some Java classes to do real work, some
>         protected pages
>           visible only to registered users and a lot more which I
>         believe Wicket
>         is suited very well for.
>
>
>         I hope anyone can give me some hints where to find additional
>         information.
>
>         Thanks in advance
>
>         Matthias Albert
>
>
>
>
>
>         -------------------------------------------------------
>         This SF.Net email is sponsored by xPML, a groundbreaking
>         scripting language
>         that extends applications into web and mobile media. Attend the
>         live webcast
>         and join the prime developer group breaking into this new coding
>         territory!
>         http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>         <http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642>
>         _______________________________________________
>         Wicket-user mailing list
>         Wicket-user@lists.sourceforge.net
>         <mailto: Wicket-user@lists.sourceforge.net>
>         https://lists.sourceforge.net/lists/listinfo/wicket-user
>         < https://lists.sourceforge.net/lists/listinfo/wicket-user>
>
>
>
>
>     --
>     Guillermo Castro             [EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>
>     Monterrey NL, Mexico     http://www.javageek.org/
>
>



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to