« He looks like a blogger to me... | Main | "Naturally, we were all curious..." »

Better All The Time Special Edition


Dispatches from a rapidly changing, rapidly improving world

Special Edition
12/31/05

Better All the Time, the year in review. Here are 50 good news stories we covered in 2005. We expect that this time next year, we'll be trying to fit 100 pictures into our table of contents collage. At least! Speaking of the collage, here's a bonus game for the kids: how many mouse pictures do you see?

Are you sure? Look carefully!

UPDATE: He may be a screwball, but he makes a good point. I had to resort to using an iFrame for this entry because MT was choking on the size of the file. However, I recognize that it is a problematic approach. So here's the link if the iFrame doesn't work right for you.

Comments

Can I just say that the IFRAME format you use gives me the hives? Particularly since the IFRAME has an exactly set size that ends up being bigger than my screen (and most people's I would gather). I know it looks a bit different in Firefox (and is a little easier to navigate), but that doesn't mean it's all that much more usable.

Could you at least include a link which opens the page directly in the browser, either in the same window or a new one(or a tab in Firefox). I know I could do it myself, but does everyone know how to lift an IFRAME ref out of the source?

Or, if you do the BATT often enough, you could put it in a DB with PHP or ASP (though I doubt you use ASP) putting each entry up seperately. It could still be in an IFRAME. Then all you'd have to do is fill the table rows with entry title (Item x), entry description (for the index file); title (often a url in your case), main body, main body image (+ image position like float:left/right), pros title, pros body, same thing for cons and a misc set of entries, until you get to closing image(if any). Each entry would then be automatically formatted, similairly to how you work with blog entries, and given next/previous/index links. The index itself could be automatically generated based on an index entry in a main DB table that keeps track your BATT entries. Finally, you would be using one table per BATT in the same DB.

Redoing the entries this way would also let you redo the page without all the <table> entries.

The DB option only makes sense though if you're doing at least one of these things a month or so

Post a comment