In a previous post, I was commiserating with an author who wrote an article about the use of typography for html websites and the restrictions that we, as graphic designers, experience. I went on complaining that technology for websites with regards to html typography hadn’t changed in 12 years. Well, if you read last week’s postings by Mick, our Director of Interactive Media, you, like me… are thrilled! Scalable Inman Flash Replacement (sIFR) is just the answer. It’s as if I called out to the Gods of typography and they heard me… just like when I was waiting and waiting for our window installer to call back, then had a dream about him building me a piano, and he called the very next day.

So, I decided to check out this new technology (this Godsend). I took about a half hour this morning and read through the documentation, the how-to-use files and sample files, and got to work. I would like to preface what I’m about to write by stating that I AM NOT A PROGRAMMER. I change what I need to change, upload what I need to upload, and save what needs to be saved. Sometimes it works and sometimes I fail miserably, but thankfully one of our very talented and personable programmers, Amy, is located two offices down from mine and always ready to help.

Basically, all that is required is setting the typeface in Flash, exporting it as a .swf file, and calling it up within the Javascript in the html page. Magically, at least for me, the type is just as I want it to look: search engine friendly, linkable, and selectable. I’m very excited to implement this new technology in future websites we design. We can now have the best of both worlds… great looking type on websites that work!

Now, I only hope someone reads my post about wanting a new SLR digital camera….

Fonts. Why did it have to be fonts. A quick recap of the my last post: Fonts need to be HTML so that search engines can see them, but web-safe fonts are very limited (to about 6) so designers cannot make things as pretty as they would like. That is until now. Introducing Scalable Inman Flash Replacement (sIFR).

As stated normally, HTML and CSS allow you to use any font but there is no guarantee that it will show up as intended because the user may not have the specified font installed in their system. sIFR on the other hand allows website headings, pull-quotes, and other elements to be styled in any font by enabling the designer to embed the font of their choice in a Flash element that displays the text.

As a result the font used does not have to be installed on the user’s machine…. but wait, if it is just flash then we’re back to the same problem of it being invisible to search engines. But No time to argue. “Throw me the idol, I’ll throw you the whip.” What happens it is uses some fancy Javascript magic, Essentially, any assigned headings (h1, h2, etc…) will be converted to Flash files with the embedded font when the website is loaded. However, any search engine spider coming through your site will still be able to read all of the page content.

sIFR requires JavaScript to be enabled and the Flash plugin installed in the reading browser. If either condition is not met, the reader’s browser will automatically display traditional CSS-based styling instead of the sIFR rendering.

sIFR is not designed for body copy text as rendering greater bodies of text with Flash place formidable demands on the computer.

Today, I will complain. My first complaint is that 15 minutes into my drive to work I realized I forgot something very important and had to turn back to pick it up, and by doing so I woke up my 3-year old. Second, in my efforts to stop using plastic water bottles, the reusable water container I filled up and placed in my car fell and spilled all over the back seat. Third, as I was stopped at a traffic light, the gentlemen in the car next to me rolled down his window to tell me that something was hanging off of my front suspension. Great. So, I pulled over and deemed it non-life threatening and off to work I went.

Now, finally at work with my morning coffee, I decide to read a brief article about the use of type for HTML websites. This should have cheered me up since I’m such a font fanatic. It turns out that the article was one long complaint regarding designing accessible websites and the font choices designers are forced to use. How appropriate for today. I quite enjoyed reading this article as I have often struggled with wanting each DDA-designed website to look stunning, sexy, and load quickly with lots of searchable HTML text, but knowing that we are restricted to a handful of fonts that will show correctly on different browsers and multiple platforms. The writer of the article pointed out that great advances in technology for web typography have not surfaced for 12 years. Well, that is definitely a valid complaint. These restrictions can definitely pose a problem, but fortunately DDA’s degreed and experienced graphic designers work hard to find a balance between beautiful, user-friendly designs that can also be search engine optimized to perform well on search engines like Google.

So, Arial, Courier, Georgia, Times, Verdana, Tahoma and Trebuchet, the spotlight will still shine on you as for the time being (and hopefully not for another 12 years) you will be the font of choice for HTML-based websites.

ColdFusion has all the built-in protocols and tools for the deployment of Dynamic Web Development Applications. The specification of the language embodies all the properties of a web application that need to be manageable. The performance of the ColdFusion Technology is optimal for the development of any small departmental applications or to a rich and highly scalable application. ColdFusion Markup Language (CFML), made it possible for a programmer to write Dynamic Application in ColdFusion and render the code into Hypertext Markup Languages (HTML), in which any computer can execute the HTML code through the Internet browser. The major issue with web programming is browser compatibility issue. Although there is a standardized HTML syntax and JavaScript language, some browsers do support component of these languages. The issue with the programmer is always try to find if a browser supports JavaScript language and if not, have the application solely depend on HTML code. Sometimes the issue could be cascading style Sheet (CSS) where the browser may not support certain syntaxes. The programmer most likely spent most of the time trying to find a common set of instruction or code syntax between all the browsers that currently exist.