Well, the whole concept of

bear.bibeault — Fri, 28 Mar 2008 21:11:58 -0400

Well, the whole concept of Unobtrusive JavaScript pretty much describes exactly what you are talking about. The body markup becomes just that: document markup, with no style embedded (CSS takes care of that) and with no behavior (script) embedded.

I'm not sure that the "servlet injection" step is really necessary. Since the designer is markup-savvy, surely a <script> tag or two in the <head> wouldn't be a problem?

My vision of how dynamic

okidoky — Fri, 28 Mar 2008 13:31:55 -0400

My vision of how dynamic database driven websites ought to work is like this:

- the graphic designer mocks up some html pages. These are raw html files with no special markup whatsoever. No weird statements inside. No code stuff inside. No application server needed to see the mock up page.

- the mock up has each table populated with at least one element. A table has one row for instance.

- the code would load the page in to memory, and take a copy of each data section's first element, and remove all subsequent elements.

- based on the database data, items get populated by repeating the elements taken from the mock up.

This is the closest way of truly separating design from program. For the first time in the history of web development can developers hire graphic designers, which do a waaaaayy better job designing websites. No more clunky crappy developery websites.

I'm seeing in jQuery ways of manipulating the dom. It also can make ajax calls. Would it be possible to do this:

- make each web page request be handled by a servlet that inserts the contents of a secondary file into the raw html file. That secondary file contains all the javascript and jQuery stuff. I want to keep any of these jQuery instructions and programming gobbledegook away from the designer. They only thing that's acceptable is id or class attributes, which are needed anyway for the stylesheets. The result is that the browser is served that html page with a bunch of jQuery script injected in to it.

This really would be THE way to build websites I think. For years and years, solution after solution, they just didn't get it. They all failed in my opinion.

I've written two java + javascript based servers that does this sort of thing on the server side. I worked with a designer, and my designer never saw the application server. She delivered very nice refreshing little html pages with all sorts of little photoshop bits and pieces, stuff no developer would ever dream of making.

Book Zone - Comments for "Interview: Authors of jQuery in Action"

Well, the whole concept of

My vision of how dynamic