Mike, You might check out the ideas behind JavaScriptMVC. We've put all our best ideas that help create a 'thin server architecture'. But most of the ideas are not unique. Generally speaking, almost everyone agrees that you need:
1. Client side templates to efficiently build HTML. 2. A 'model' layer (dojo data) to provide a common interface to your services 3. A widgeting layer The next question is how do you break up your app into separate parts. For example maybe you want a list of users. I encourage people to make the 'list' independent of users so the list can later be reused. Essentially, try to keep everything isolated to only what it should be doing. On Feb 12, 10: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]
