Hi David and others,
I've converted my tiny project to Wicket 1.2, but encounter the same
problems as with Wicket 1.1.1.
- the image on the first page is not found,
- clicking the About link shows the about page, but does not render the
links correctly (About is still a link).
My "exploded" directory contains this structure:
+---META-INF
| context.xml
|
+---pages
| | Index.html
| | PageTemplate.html
| |
| +---about
| | Index.html
| |
| \---graphics
| logo.gif
|
\---WEB-INF
| web.xml
|
+---classes
| \---com
| \---foo
| \---website
| | FooWebApplication$1.class
| | FooWebApplication.class
| |
| +---pages
| | | Index.class
| | |
| | \---about
| | Index.class
| |
| \---templates
| PageTemplate.class
|
\---lib
commons-logging-1.0.4.jar
log4j-1.2.12.jar
wicket-1.2-20060227-0200.jar
I'd really appreciate it, if someone please could take a look at the tiny
project (http://regnis.de/_wicket/wicket-060228.zip) and give a hint about
what's wrong and how to make it better. Thanks in advance.
--
Best regards,
Thomas Singer
David Leangen schrieb:
Most of your questions were already answered by Johan (who can answer better
than I, anyway). For the others, see inline.
In any case, something like this is surely possible with
mountable links.
I have read a lot about different links in wicket, but nothing yet about
*mountable* links. Also, the wiki does not show anything.
Indeed. These are available from Wicket 1.2. I'm in the process of writing a
wiki page, but haven't had time to finish it yet. These mountable links are
really nice, BTW...
(3) Even at design-time, relative paths to images or the
style-sheet should
be valid, so IDEA can verify their existence and image size. This
requires
the page templates to be in the same directory structure as the
images and
style-sheet.
Wicket does this if you want it to.
See above example, I do not get it to work as expected. Please
note, that I
need the application to work at http://<server>:<port>/foo/ and not at
http://<server>:<port>/foo (the trailing slash problem).
Again, works with mountable links. You need to set up 1.2 and mount your
links.
(5) It should be very easy to turn links, e.g. used in the menu
bar snippet,
into "smart links". If pointing to the current page, they must not be
rendered as a link, but the look should be customizable (wicket
seems to use
italics in this situation).
All out of the box.
How to customize the look of the not rendered link?
CSS works just fine. Wicket allows you to customise the "not-rendered-link",
just like any other component. Or, if it's not customizable enough for you,
you can create your own component.
If you're playing around with 1.2, I suggest you also download the latest
snapshot of the examples and look directly into the code there.
HTH
-------------------------------------------------------
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
-------------------------------------------------------
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
