These projects are retired. The development has stopped and we don't provide support for them anymore.

Searching a solution

Initially we thought that somewhere there had to be a solution available to all these problems and we evaluated the options.


Several WYSIWYG[1] tools exist that hide the differences of the DOMs from the developers and also allow the quick development and deployment of a working site. The tendency to be as distant as possible from the actual code (HTML, Javascript, ...) works for small and fairly generic designs, intricate and custom tailored systems are however quite difficult to develop using this approach. Since those projects are often composed of several interacting standards, tools and languages it is rarely possible to never touch the code itself.

WYSIWYG tools are producing their own code which might not be readable by humans. With a bit of efforts it's sometimes possible to be able to comprehend and modify that code. The real problem occurs when the edited code is re-used with the WYSIWYG tool. Either the code is completely messed up again and misunderstood, or just misunderstood (if it's one of the better WYSIWYG tools).

Cross-browser classes

A number of Javascript classes exist that implement an API that automatically detects which browser is being used. The methods adapt themselves to the underlying DOM and allow a programmer or designer to forget about the browser differences and still have the power to dig as far in the code as necessary.



What You See Is What You Get