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
Yeah thats the usual way.. But still if you panalize a lot, tweaking for
them could become a little hard. But I guess if you spend a little hour
with them they should not have those trouble..
Johan Compagner wrote:
most of the time at least as far as i know
you work the other way around.
Thanks for all the advice -- guess I'll see how it goes, possibly post
something to the wiki if it seems to be useful.
Alex
On Mar 6, 2008, at 4:58 AM, Nino Saturnino Martinez Vazquez Wael wrote:
Yeah thats the usual way.. But still if you panalize a lot, tweaking
for them could become a
I searched the wiki and the list archives, but I haven't found any
sort of wicket reference appropriate for a web designer who doesn't
speak Java. The list of xhtml tags in the wiki is the closest, but
it's definitely written more for the programmers.
Am I missing something? If not, I'll
is the closest, but
it's definitely written more for the programmers.
Am I missing something? If not, I'll contribute the guide I write to
the wiki.
Thanks,
Alex
--
View this message in context:
http://www.nabble.com/Guide-for-html-designers-tp15852223p15861127.html
Sent from the Wicket
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
