Assuming separation of concerns (i.e. JavaScript does not appear online in the HTML) then there is no need for the dependency that concerns you. Typically JavaScript handles events while HTML and CSS are responsible for layout and appearance. Moreover JavaScript doesn't interact with the server - it simply messages it and is agnostic as to the effect of the message on the subsequent layout. In a well designed application a controller (servlet, rails or whatever) adds one or more layers of indirection between the JavaScript and the markup (HTML)
On Feb 12, 8:08 am, mikepalmer <[email protected]> wrote: > Hello mentors, > > I've been charged with trying to help our company's web properties > improve the front-end coding of their sites. Taking Zakas' Scalable > Javascript Architecture as a starting point has been very helpful, but > when it comes down to a page or a module structure, I have a question: > where do you generate the HTML? > > Most discussions about accessible usage of Javascript talks about it > as added behavior; eg: the HTML is either static or generated server- > side and Javascript adds value after the page loads. I suppose this is > acceptable when creating a site where the interactive functionality is > an add-on, optional. > > However, when developing a dynamic web application loaded with > interaction, wouldn't having your HTML generated by the server-side > tightly couple your Javascript module to the server-side code? > Wouldn't your Javascript modules be lose their modularity by depending > on HTML generated externally? > > I would love to hear how you approach this type of situation and what > questions you ask yourselves when deciding how to structure your > modules. > > Thanks! > > Mike -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
