|
|
Ajax; Templating; and the Separation of Layout and Logic
|
03/10/2006, By Matthew Batchelder
|
While Ajax is the cause for the article, the heavy focus is on templating. For the past few years I have been using XTemplate as my templating library (I'm a PHP buff) and have been happily separating my logic from my layout...unitl I ran smack dab into the power of Javascript. My PHP still kept its separation from HTML as is the purpose of XTemplate, but it was my HTML that became littered with little nuggets of Javascript all over the place. No matter the method to my Ajax madness, this was my problem.
What Exactly Is Templating And Why Do It?
Templating is definately not new and its use has been debated back and forth for quite some time. But like I stated above, the goal of templating is to keep logic separate from layout which is a good thing for a couple of reasons:
1. Less clutter. Face it, HTML and whatever server-side scripting language you choose to use are two different beasts. Mixing them together is visually unappealing making code hard to read...and hard to read code is hard to debug.
2. Coders can develop code. Designers can develop layout. With templating, you are able to achieve this separation and avoid the need for a developer to butcher a designer's layout to make it function with an application. Each can design/code on their own then combine their efforts with ease.
3. With separation such as this, applications are more easily skinned and/or receptive to complete UI overhauls.
4. Did I mention less clutter?
Layout and Logic separation is a beautiful thing; keeping one language from another has some true value in readability. To do it half-way gains you nothing. True separation has been a blessing in my development and debugging. If you haven't at least tried it, check it out, it may be what you were looking for (even if you didn't know it).
Read more...
|
Rate this Ajax Articles
Rating: 6.0 out of 1 vote cast
| |
|
|
|
|
|
|
|
|
|
|
|
|