I actually thought your question to be good, I think using markup inheritance could help some inorder for web designers since the could have a larger base of the html in one file..

But again all your panels html are still fragmented.

btw I belive that designers should just ignore the wicket specific tags, and maybe dont rely too much on id's since they could change..


regards Nino

Alex Jacoby wrote:
Heh, slight misunderstanding -- I *am* the programmer, and my site is just about done, and I'm going to be passing it on to the web folk (HTML, CSS, graphics people who don't program) to prettify it asap.

I know that it will involve me teaching them some of the basics of wicket, but I was wondering if there were resources out there for helping in this type of situation... a "Wicket for non-programmers" type guide. I've written a few pages so far...

Thanks again for the suggestions,
Alex

On Mar 5, 2008, at 4:54 PM, Ned Collyer wrote:


A web designer being a graphics or a HTML guy (or a combination thereof)?

Seriously tho, design your site, give the output to the programmer to
"wicket up".

I don't see how wicket will work for you if you don't understand the basic
bits of java.  If you do, the tutorials and examples on the website
http://wicket.apache.org/examples.html then that should be an easy enough
stepping stone to forage deeper.

Things you are probably interested in are panels, borders, includes and
fragments.
http://wicketstuff.org/wicket13/compref/

But I think you will find it tough with zero java knowledge. It may work
well if you are working with a programmer :), but solo - good luck!


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
-Wicket for love
-Jme for fun

Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to