|
|
Posted by Andy Dingley on 09/14/06 23:59
Runnin' on Empty wrote:
> The more layers of this sort of complexity, the further you get away from
> static HTML templates, the less likely you can vet the HTML to ensure
> validation.
No, the more more complex it is, the more important it is to validate,
and to understand the implications of validation at each step.
My current project is a web app that builds a deliverable package over
100MB. Multi-developer, multi-continent distributed Agile development
using everything form AJAX to XSLT. Just the Java part of it goes from
the worst of years-old Indian bucket-shop structureless JSP through to
the latest in Facelets (I don't even know what a Facelet _is_ yet).
Whatever it is you're building here, I bet it counts as pretty small
and simple in comparison.
Now this doesn't validate (yet). It's also resolutely IE-only and
horribly inflexible. Much of what's wrong with the presentation side of
it comes down to bad HTML and bad CSS. I'd say I can make even _this_
mess standards-based, but I'd have to start playing the A-Team music in
the background. It needs doing though - it's our only way forward if
we're to get the presentation manageab;e and cross-platform portable.
Navigation:
[Reply to this message]
|