Hi Matt,
You've touched on a interesting topic and everyone has their own way of
doing it.
Personally I split my code into two sections, backend and frontend, or
rather data and presentation.
With this in mind I consider javascript to be on the frontend and therefor a
designers tool.
On 8/2/07, Matt Penner <[EMAIL PROTECTED]> wrote:
> I just think code like:
> $('#courseHist').append('<div><span class="heading">Course
Title</span><span class="content">' + crs.title + '</span></div>');
> is very ugly and muddled.
I see nothing wrong with this as at this point it is the designers decision
how to present the data given.
I like to use XML because then the designer can decide which information to
grab and manipulate using XSL into HTML.
Here's a rundown of how the languages map on the model I'm using.
Data Layer: MySQL / PHP / XML
Presentation Layer: XML / XSL / HTML / CSS / JS
~Sean
