It was more in reference to large enterprise apps, the one in mind combines 4 formerly separate, disparate apps, a mail server and a file manager into a single install, and doesn’t have any bearing at all to what an actual workflow is. Each Ext tab basically dumps the contents of a database out, or loads an iframe that contains a different install’s instance.
As an front-end engineer, it pains me to see some pixel perfect thing of beauty that a graphic designer has whipped up in Macromedia, with the most $deity-awful pile of auto-generated crud backing it up, with no considerations for usability, or feasibility of making it work on multiple different browsers.
Even getting something close to looking the same across multiple browsers and resolutions is a herculean task.
So yeah, you pooped out something pretty. Well done and all that. Now the hard work begins, polishing that turd until it is dynamic (i.e. loads the appropriate data), usable and accessible.
Get yourself some potty training (e.g. roll the html by hand) and then we'll talk about respect.
As a designer, it pains me to see some interfaces that directly represent the back-end model, not the user's task.