Archive for the ‘technology’ Category

Reinventing the contact…

Monday, April 17th, 2006

I read that ICANN is in the final stages of creating another top-level domain called .tel. The arguments behind it are that currently there is no way to get the latest contact information so companies and individuals will buy .tel domains to provide it.

Their argumentation can be summed up in these three points. Firstly not everybody has a website with a friendly and memorable URL that can be used as source of data. Secondly people cannot be identified by phone numbers because they change. People are identified by names hence their solution is perfect.

It doesn’t take a genious to see the arguments they make are very weak. If users don’t have a website now, why would they have it after the .tel domain is available? Yes, phone numbers change, domain names change, people move, companies die. URLs are hard to remember, so are emails and phone numbers. Names and faces are hard to remember. To make things worse there are people with same names, similar URLs, phone numbers and even faces. And there can only be one identified by a unique .tel domain. How does this lessen the confusion?

The thing that made me write this is the ignorance of the development of the web. Nowadays almost every communication device is also a web browser. Web pages use HTML as the foundation and HTML has an element called ADDRESS. This is what the specification says about the element:

The ADDRESS element may be used by authors to supply contact information for a document or a major part of a document such as a form. This element often appears at the beginning or end of a document.

This means that you can already do what they want to achieve by the .tel domain by using the ADDRESS element on your web page. If you want to make the contact information even more computer readable and be able to add other information you could just use hCard microformat. It’s based on a standard contact format and can be easily imported into all recent contact management software.

Since not many people use the ‘new’ TLDs are there any reasons to have .tel?

AJAX workshop

Wednesday, April 12th, 2006

We’re preparing a workshop at Spletne urice (“Web hours” in Slovenian, a weekly meeting of web enthusiasts) that will focus on AJAX, hosted by me and another Marko. Actually we’re preparing two of them. The first one will cover the basics of asynchronous transport and data, the second one will add some DOM scripting and review some AJAX frameworks.

I’m asking you, my ’till-now-non-existent/anonymous’ readers, to come forward and suggest any AJAX frameworks and/or sites that need/want an AJAX makeover. We might use this information for the workshop and transform your site. If you want to come you can register here. The workshop will probably be held in Slovenian, but the code will be written in universally understood JavaScript so come back for the slides and a showcase of the makeover.

Firefox hates developers

Wednesday, April 12th, 2006

A few days ago I noticed that Firefox is not making any requests to cached pages. I was a Mozilla Suite user until a month ago when I finally switched. Now I’m seriouslly thinking about switching back.

I am a developer so seeing what request are being made to a server is of utmost importance. Mozilla had a setting which told it that it should always do a request, even if the content is already in cache. This resulted in many 304 responses. I know it causes more traffic – the default setting is something more network friendly.

Firefox removed this great feature. It’s even worse – if you set the size of cache to 0 it still caches stuff and does not make request to the server. If I knew I never would have switched. I’m downloading Seamonkey…

Why I don’t like widgets

Sunday, April 9th, 2006

The reason is really simple – they’re bloated. Widgets is another word for a huge javascript that does what you want/need and a whole other stuff somebody needed or maybe just the developer thought somebody would someday need. Usually the javascript is so ‘complex’ that you can’t just remove the stuff you don’t need – it’d be faster if you wrote your own.

There is another reason that goes beyond javascript. Most widgets don’t exploit the technology and go about reinventing the wheel which results in crappy/invalid HTML, problems with data persistance and a low level of pluggability. Some actually do use an API but I think that’s overkill.

It’s funny what wikipedia says about widgetsclearly, they represent any purely mercantile commodity that has no artistic or spiritual value. When I first started writing the SortedTable I wanted to accomplish the contrary. I tried to write something that would exploit the advantages of valid XHTML and the fact that you can nowadays rely on DOM functionality of the browser. I did it for me and not for money (and released it under CC license).

The problem is I got many feature requests, that could simply be accomplished via some DOM scripting and using the built-in event handlers. I decided to keep the script simple and display the possibilities through samples. What needs to be done next is the reimplementation of the sort function which is a bit slow – I already have an old implementation of Quicksort in javascript that is going to come in handy for this one.

Anyway, a new version is out. This is the changelist:

  • corrected a weird error that broke some sorts in ie6
  • added the possibility for a nonsortable column via class=”nosort” on the th cell
  • added the possibility to ‘regroup’ tbody elements if there’s more than one (for whatever reason)
  • added additional hook to put your custom javascript on (onsort)