Everything is becoming, nothing isPlato
1 | 2
1 - 5 
Relates to CSS Design
Courtesy Mr CSS :
Relates to Peregrinations
While the SoBig.F virus spawning was successfully blocked over the weekend, it seems to have come back with a vengeance to a few of my mailservers these last two days. Today I had 75 virus bearing emails in one mailbox, and one of my webmail servers (from a mojor UK ISP) seems to have been totally shut down. Following a spasmic burst of SoBig mail to my boxes middle of last week, it certainly seems to have returned with a vengeance at the moment. Mailwasher is proving a very versatile ally in the cause, allowing me to just remove all infected messages with a single click. Evenso, I have found it unwise to check mail mid-afternoon, when new infected messages seem to appear within the time it takes to clear out with mailwasher and connect to a mail server with my mail client. It would be refreshing to know that September 10th would be the end of this irksome beast, but the warnings are out for a more malicious variant and the patterns suggest it could be very soon - a sobering thought!
Relates to Movies
The wait is finally over, and I have seen those tender last minutes of The Two Towers - last Christmas the Odean dramatically ground to a halt just as Gollum once more overpowered Smeagol in the wooded foothills of the Ephel Duath. As it happened, what I missed was a minute of dialogue as the most impressive animated character of all time concoted his trap in Jackson & Co's interpretation of events.
As the poignant lyrics of Gollum's Theme played over the final credits, I couldn't help but wonder whether the choice of ending fell short of the emotion that just leaps off those last few pages of Tolkien's book. At the end of the first installment, in 2002, the expression on those in the audience, who knew not the story, had just left me thinking what are they going to be like when that door is slammed shut in Sam's face come next year. Well of course, it did not happen. The screen writers have decided to hold off the battle with Shelob, and the instance the real hero of the story takes hold of the ring to, I guess, the opening segment of the ROTK.
I dont think The Two Towers can really be assessed until the final piece of the Trilogy fits into place. On its own, it is a masterful piece of cinematography with phenomenal action sequences, set designs, makeup, costumes and, of course, supperior CGIs. As an interpretation of the book, it has clearly been presented as part of the whole - this is not the Two Towers as Tolkien wrote it, it is the Two Towers purely by nomenclature. Some parts of the book are emphatically bought to the screen version - the growing relationship between Legolas and Gimli, the conflict of Gollum, and Frodo's struggle as he follows a similar demise. Aragorn's own conflict with his regal future is somewhat blurred by the Hollywood-esque love triangle with Arwen and Eowyn (Arwen a particularly unusual inclusion being only a four page appendix of the original book. But then without these two characters the film would be entirely male cast). Of course Eowyn's true moment is, hopefully, yet to come in the final part as she changes the course of the Great Battle, one of many tear wrenching moments! Perhaps, the wisdom of the Ents that is somewhat downplayed will come to light in the additional thirty minutes footage of the extended version. One oddity I felt was the unusual portrayal of Faramir, almost a replica of his brother, desiring the Ring of Power and almost ignorant to its effects. His knowledge was implicity demonstrated by his association of the One Ring with Gollum's Precious - the name preserved in parchment by Isildur. But Faramir's own lust for the Ring and reluctance to release the three made him just another man of Gondor, a shadow of his brother.
Still, everyone will interpret Tolkien's book differently and to translate it into over 600 minutes of movie is a phenomenal acheivement. The ROTK is surely going to be a true classic. A trilogy that does not lose energy, as happens in most trilogies (Indy J excluded!), reching the ultimate cinematic triumph in the battle of the Pelennor and the fall of the Black Gate. Perhaps, for once, in contrast to the Hollywood mould of movie making, the final words, that were denied Samwise Gamgee in the Fellowship and The Two Towers, might rightfully be allowed him this Christmas. For surely, the Lord of the Rings, while a tale of good staving of evil in a fantastical world of heros and villains, has one legend above all others. The simple poorly gardener from Bagend, Hobitton in the Shire, Samwise the stouthearted, Samwise the Brave.
Ok, yet another FIR technique has been created by Levin Alexander to resolve the inherent problem
for CSS enabled browsers with images disabled. While this solution does display the header in plain text when images are disabled, it falls foul of reintroducing a
span element, which the techniques of Stuart Langridge and Seamus Leahy had
tried to resolve. While this new approach makes nice use of the relative→absolute relationship between parent and child in CSS positioning, it fails with transparent PNG (or GIF) header graphics, and for any design with coloured background,
transparency is a prerequisite to avoid visual discrepancy between the browser interpretation of the color and that defined in the image file.
Determined to resolve this, I tried changing visibility, third dimension placement (z-index) and container heights, but there is always going to be one scenario that breaks the hack. Since FIR and its many derivatives are just that, a hack, I have come to the conclusion that FIR by itself cannot succeed as an Accessibility tool. It does present an excellent method for separating design and content, implementing alternative graphics with each stylesheet, and fortifying the semantics of the XHTML document's markup. But once accessibility is contemplated, other methods must also be introduced to present each user with the same material. The obvious way to acheive this is to use a Stylesheet Switcher to offer a plain text version of the page. Here I am not talking about the plain text of 90's websites, where the content of the site must be completely duplicated in the appropriate format. With the tools of the DOM the same XHTML marked-up page can be used, and a simple alternative stylesheet created to display plain text for the entire site.
So the graphic design version of the site can implement a FIR technique to ensure the content does not contain superfluous code. For example a header would be just a header.
<h1 id="header">This is the page header</h1>
And the stylesheet would implement FIR to replace the text with the graphic. This can offer an accessible page to most users. For the neglected few, switching to the plain text style sheet presents the header as is (there are simply no FIR techniques declared). Hence, users browsing with CSS enabled browsers with images disabled can also access all the material. Everyone is happy!?
noscript tag). Then
the correct stylesheet for the pulled page can be set as default before the page is sent to the client.
Been very busy the past couple of weeks, so not much time for blogging…Here's a few bits and pieces from around the web…
[ Back To Top ]
Copyright © 2002-2013 Severn Solutions.