Month: March 2009

Web 2.0 AJAX Loading Panel 2.0 Has Been Released

Enhance your site’s look and feel during AJAX requests with the fully customizable state-of-the art Web 2.0 AJAX Loading Panel without writing a single line of code!

All you have to do is to follow a few easy steps, modify a couple of properties and add the show and hide methods to your XMLHttpRequest function.

Web 2.0 AJAX Loading Panel allows you to display cool loading overlay to your webpages during your async requests to the server. The loading overlay ann message is fully customizable and can fit to any website design. The deployment and customization of the script is a matter of minutes. On this demo page you will learn how to do this.

Web 2.0 AJAX Loading Panel works under Internet Explorer 6/7/8, FireFox 2/3, Opera 9/10Beta, Chrome 1, Safari 3/4Beta and any other Gecko or WebKit browser. You may fully customize its appearance, change the corner radius of the message box, set custom opacity and loading images and tons of other cools stuff that allows the script to fit any website design.

View online demo of Web 2.0 AJAX Loading Panel

Visit the home page of Web 2.0 AJAX Loading Panel

Download Web 2.0 AJAX Loading Panel


Using the IE8 X-UA Compatibility Meta Tag Properly

Try Semtex – the new HTML5, CSS3 and JavaScript UI framework!

Internet Explorer 8 is out, with a couple of rendering modes, that will take time to handle. As you know, IE8 renders pages in standards compliance mode by default, and the X-UA compatibility tag has been a good idea of Microsoft, as it gives a chance to developers who have not optimized their websites for IE8 to put things to work with less effort.

Did you try it already? If it is something new to you, it works like that:

1. Add the following meta-tag in the head section of your webpage above any linked files (i.e, above <link>…</link> and <script>…</script> tags)

<meta http-equiv="X-UA-Compatible" content="IE=7" />

If the tag is below link or script tags, the fix will not work.

2. Reload the page, and the meta tag will force IE8 to use the rendering engine of IE7, and your webpages will look as they did before, until you find a solution for the issues you have noticed when IE8 was released.

If your pages behave as expected under IE8 then you should use the IE8 meta tag.  This will ensure that your code will continue to run properly after the next browser upgrade:

<meta http-equiv="X-UA-Compatible" content="IE=8" />

In summary, the compatibility UA-X meta tag is a good and legal trick to be comfort with your visitors.

Do not hesitate using it.

More Cool Stuff

Acid.JS 2.9 Released With 2 New Additions

Get most of the website widgets and tools I’m developing in a single package that is regularly updated. Whenever a new script or script update is available, it will be included in the download file. To stay informed and up-to-date with Acid.JS, please, subscribe to my RSS feed.

Download the latest version of Acid.JS

Acid.JS 2.8 is Out

Get most of the website widgets and tools I’m developing in a single package that is regularly updated. Whenever a new script or script update is available, it will be included in the download file. To stay informed and up-to-date with Acid.JS, please, subscribe to my RSS feed.

Download the latest version of Acid.JS

A Word About the PSD to (X)HTML Services on the Internet

“How much costs the “alt” attribue of an image? Should I use it or not? If I have 20 images per page, what is the total cost of the <img /> tags with the “alt” attribue?”

If you are a web-developer, you have certainly noticed the growing bunch of websites that provide the convenient and relatively unexpensive service of design to layout conversion, also known as psd to (x)html coding. It works like that – you create a beautiful design, and then leave it up to experts to create a beautiful code out of it, that is semantic, accessible, usable and valid in markup. Some of these companies do a really great job, however the majority provides coding that has nothing to do with the good coding practices and search engine optimization.

A cursory glance at the code of the latter reveals that:

1. Most of the layouts created by these companies have nothing to do with coding at all. Using <div> for layout instead of <table> still does not mean that the code is semantic. A <div> element does not bear any semantics if its content structure is meaningless. A navigation bar, that consists of <a> elements within a <div> is even less semantic and lousy as using <table> for the same purpose. A good navigation list requires the links to be nested within a list, and to be supplied with suitable “title” attributes.

2. 98% of the forms created by such conversion services are missing fundamental form elements such as <fieldset> and <legend>. And most of the guys creating such layouts miss the fact that a contact form is still a list, and the semantics of a list requires a list tag. The accessibility of an input element is achieved with <label>, accesskey and title attributes, which are forgotten in most of the cases.

3. Having a valid markup is fashionable, but unfortunately most of the companies that provide psd to (x)html service have somehow missed the essence and purpose of the valid markup. And yet more – most of these guys believe that if a website has successfully passed the W3C SGML validation, it is automatically search engine optimized, semantic, usable and accessible. And they are totally wrong, as writing a valid code is nothing but conforming to the formal requirements created by the W3C.

Another funny thing – a number of websites that provide conversion services additionally charge their clients for:

1. 100% valid markup. Is there a 42% valid markup? What percent of valid code is included in the base price? The markup is either valid, or not. 99% of valid markup is as invalid as 1%.
2. XHTML compliance at an additional price. What is the exact difference between HTML and XHTML? Why should I pay additional $$ to have my website coded in XHTML1.1? Should I choose XHTML1.0 Transitional, because it is cheaper? How about HTML3? I am sure that if I ask a company that charges differently according to the doctype why it is so, they will not be able to give me an adequate answer. Accoring to such logic, the cheapest website should be coded in XHTML1.1, as coding under standards compliace mode requires less browser hacks, and is much easier to utilize.
3. 100% browser compatibility is not included in the base package. Yes, if you want a website that looks good under older versions of Opera, Konqueror, Safari, Chrome, K-Meleon, NetScape or your favorite exotic browser, you should pay additional $$. A good conversion service is obliged to provide crossbrowser coding, and 100% browser compatibility should be a undisputed default.

Of course, these are cheap and lousy marketing tricks, and such guys make money from the presumed ignorance of their clients, but the fun here is that they make you buy additional stuff, that should be used by default by every developer that respects their own work and coding abilities.