most of the time at least as far as i know you work the other way around. First the webdeveloper then the programmer And maybe after that the webdeveloper only tweaks. But he can do that just fine he just should leave the wicket tags alone
johan On Thu, Mar 6, 2008 at 2:10 AM, Alex Jacoby <[EMAIL PROTECTED]> 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] > >
