Your site began to swell, first to 5 pages, then 15, then 50. It
seemed to grow exponentially. Then came that fateful decision, the one you always
knew was coming but always managed to cast aside: it was time to redesign the site.
Unfortunately, perhaps because of the euphoric emotions induced by the need to
create the coolest Web site on the planet, you forgot one of programming??™s basic tenets:
always strive to separate presentation and logic. Failing to do so not only increases
the possibility that application errors are introduced simply by changing the interface,
but also essentially negates the possibility that the designer could be trusted to
autonomously maintain the application??™s ???look and feel??? without becoming entrenched
in programming language syntax.
Sound familiar?
It??™s also worth noting that many who have actually attempted to implement this
key programming principle often experience varying degrees of success. For no matter
the application??™s intended platform, devising a methodology for managing a uniform
presentational interface while simultaneously dealing with the often highly complex
code responsible for implementing the application??™s feature set has long been a difficult
affair. So should you simply resign yourself to a tangled mess of logic and presentation?
Of course not!
Although none are perfect, numerous solutions are readily available for managing
a Web site??™s presentational aspects almost entirely separate from its logic.
Pages:
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551