Hej Eugene,
In practice the wicket frontend development is interrupted by frequent
small changes to the HTML, Javascript or CSS. Changes to these markups
are very expensive because they effort a new software release followed
by a software rollout. This depends on the fact, that the markup is
>
>>
>> --
>> View this message in context:
>> http://apache-wicket.1842946.n4.nabble.com/The-best-way-for-designers-and-Wicket-developers-to-collaborate-tp4656560p4656570.html
>> Sent from the Users forum mailing list archive at Nabble.com.
>>
>>
sandbox" template folders?
> >
> > The main issue has been Panels, but there are also some other tweaks the
> > developers are making to "make it work" while the designers aren't aware
> and
> > are working in their own sandbox.
&g
re also some other tweaks the
developers are making to "make it work" while the designers aren't aware and
are working in their own sandbox.
Just wondering, what's the best practice, the way things are supposed to
work in Wicket?
--
View this message in context:
http://apac
