i apply the same practice as igor. it works great for both sides, dev
and des. once des already has the html model, dev creates the first
integration to the object-tree, providing feedback to des, so dom-tree
follows the same coherence (in case needed to correct some parts), and
following are just
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
We have a Web design team and a Java development team on our project. We're
using Wicket for our pages.
I know Wicket was designed to make it easy for designers and developers to
work together, but we're actually finding the opposite -- it's difficult to
communicate changes back and forth. We're
Hi,
I'm a happy user of https://github.com/42Lines/wicket-source with a small
improvement from https://github.com/cleiter/wicketsource-contextmenu (provides
an item in the context menu instead of an entry in the Dev Tools - Markup
- Style - ...)
Maybe this can be extended to look for the html
