"When you're designing a piece of code, or a web page, or you're putting together an image, always keep one logical action or piece of work in one file or one named block. If you want to do several things, then write an encompassing element to contain them both."

Such is Computer Science Theory, but what does it mean, and why? Let me give you an example.

On the left hand side of our web page, we have an image that's 132 pixels wide by 300 pixels tall, and until the current version of our site it also included a band of 8 white pixels on the right to space the text in. Great - the site worked very well. Until we came to add in colour changes required under the UK's Disability Discrimination Act. Then we saw an ugly white line to the right of the image on all non-standard pages and had to make retrospective changes.

Had we used two images in a table to start with, "one image, one function", then not only would that problem have been solved, but also we could have made use of the images for other purposes. I'm glad to say that's done on the new site, which is why you can see images of Lisa and I to the sides of this page - great reuse of work and THAT's what allows us to do so much with such a small team!

(written 2005-12-19 09:21:28)

 Q907 - Object Orientation and General technical topics - Object Orientation: Design Techniques

Back to Bigger Box Campaign

Previous and next or Horse's mouth home

Forward to MySQL permissions and privileges

A company we can work with
Daily Image Santafied
Cancellations and penalties
MySQL permissions and privileges
Design - one name, one action
Bigger Box Campaign
Copyright - how much can I legally copy?
Packages in packages in Perl
Perl course during the week, getting married at the weekend
Halal in Melksham