Thinking about it, if really the purpose of Voting is to allow the people to choose whom they want as their leader (which I believe is the case), then I think our present voting system might not be the best approach to achieving that desired result.
Not that the present voting system is flawed or something of that nature, its just that with our present technological advancement I believe there is a much better system for distilling the leader of choice from the populace.
I was just thinking the other day; Instead of a system that operates by people casting a vote, why not have one that operates in such a way that people lists in other of preference, whom they would want as a leader. Then aggregating the entire list, the leader of choice will be determined.
I feel such a method of sampling will return a more accurate picture.
The question we should ask ourselves is this: why should the voting system be set up in such a way that it is “vote for one, eliminate the others”. What is stopping us from having a voting system that is modeled in such a way that sampling takes a preference-listing fashion?
Of course the weight of each preference will have to be different for this method to be sensible. The weight will have to be determined by some statistical principle.
I feel that with the level of sophistication we have achieved in software/computing and other technological achievement, this idea is not only visible, it an idea that we should start working towards. Nothing is stopping us from rethinking our voting system.
Let me know what you think.
Monday, April 16, 2007
Wednesday, April 11, 2007
Understanding layout with CSS
If you find yourself banging your head against the wall when using CSS, strictly for your layouts, then I can bet the London Bridge that you have not yet acquainted yourself with concepts like normal flow, box model, and how these come into play when using float and positioning.
I wasn’t able to really use CSS for layouts myself until I took some time out to try and get a handle on these concepts. Before then it was more of trial and error.
The normal flow explains the default flow (positioning) of your XHTML elements.
The Box model explains how the browser renders individual XHTML elements
While float and positioning allows you to specify the position of XHTML elements outside the normal flow.
I should be able to, one of these days, sit down and write a comprehensive tutorial on these concepts, but while I wait for that time, I suggest you rather Google the web for tutorials already out there.
I wasn’t able to really use CSS for layouts myself until I took some time out to try and get a handle on these concepts. Before then it was more of trial and error.
The normal flow explains the default flow (positioning) of your XHTML elements.
The Box model explains how the browser renders individual XHTML elements
While float and positioning allows you to specify the position of XHTML elements outside the normal flow.
I should be able to, one of these days, sit down and write a comprehensive tutorial on these concepts, but while I wait for that time, I suggest you rather Google the web for tutorials already out there.
Thursday, March 22, 2007
Clearing the Air
Across various blogs and with discussion amongst folks, I have been observating an assortment of arguments over Ajax and its rights to be referred to as an enduring technology. Some are like it’s the magic potion we need, some see it as just good enough while some refer to it as an error.
Well, right now I’m not interested in directly saying which point of view I feel is right or wrong, I just want to correct some misunderstanding I see often times in most of these arguments:
NO1: Ajax is not a replacement for desktop applications, neither is it set to make them obsolete. Sure some applications will have to be redeployed as Ajax application to increase their value, but some will still remain as desktop app since there will be no need to Ajaxify them.
If it is understood that Ajax is a ‘design approach’ and that not every problem will require Ajax for its solution then we will stop regarding it as a panacea. Having applications like meebo, kiko, or utorrent as Ajax application makes perfect sense but that does not mean that every desktop application will have to be cloned into an Ajax application.
NO2: Ajax is not a replacement for our good-old web applications
I have encountered rants about Ajax as if it’s the messiah of web applications all developers have been waiting for. Well, this is expected. New and innovative technologies always enjoy tremendous amount of hype which, often times, is not equivalent to the productivity they really offer; so Ajax is just having its share of Buzz.
But it still boils down to understanding that there will be situation that will call for the Ajax approach while some won’t. I mean look at google maps, such an application, which requires an asynchronous communication between client and server may require Ajax. On the other hand it might be overkill or overzealousness to implement Ajax is some domain. The last time I checked, our good old google page still refreshes.
NO3: Ajax is not a HACK
Ajax, in some quarters, is referred to as a HACK. Wrong! Ajax is perfectly not a hack. I mean if Ajax is a hack then stuff like lamp should also belong to the hack club.
The principle of Ajax is simple. It is having different technologies, in their different domain, working together in a holistic approach: Javascript, whose domain is the browser, remains in the browser, the XMLHttpRequest which handles the asynchronous request does nothing more but that, XML or JSON, takes care of the data wrapping while PHP, Python, Java, or whatever server side language you choose handles the back end. So tell me where the hack is, in that set up?
NO4: Ajax is not overkill on the browser
I have heard the browser described as just a document rendering application and that it is eerie to use it in such a manner that Ajax suggests, that is, as a User Interface. Wrong!
Maybe some years back when the browser was just an application that parses HTML codes and displays it as directed, such a description as a document rendering application would have been apt; But not the browsers of today.
API’s like the DOM, BOM and things like plug-ins etc. which have crept into the browser over the years now makes it more than just a rendering application but could easily pass for a ‘maturing’ User Interface.
No 5: Libraries are not bad
Dojo, MochiKit, Script.aculo.us, AJASON, and the rest of them.
Having code libraries is not evil and neither is it new. Libraries have been in existence since time immemorial or what is STL to c++ and having libraries that prevents you from the hassles of writing a lot of code and at the same time taking care of problems that are peculiar to the Ajax architecture is not such a bad thing…at all.
Well, right now I’m not interested in directly saying which point of view I feel is right or wrong, I just want to correct some misunderstanding I see often times in most of these arguments:
NO1: Ajax is not a replacement for desktop applications, neither is it set to make them obsolete. Sure some applications will have to be redeployed as Ajax application to increase their value, but some will still remain as desktop app since there will be no need to Ajaxify them.
If it is understood that Ajax is a ‘design approach’ and that not every problem will require Ajax for its solution then we will stop regarding it as a panacea. Having applications like meebo, kiko, or utorrent as Ajax application makes perfect sense but that does not mean that every desktop application will have to be cloned into an Ajax application.
NO2: Ajax is not a replacement for our good-old web applications
I have encountered rants about Ajax as if it’s the messiah of web applications all developers have been waiting for. Well, this is expected. New and innovative technologies always enjoy tremendous amount of hype which, often times, is not equivalent to the productivity they really offer; so Ajax is just having its share of Buzz.
But it still boils down to understanding that there will be situation that will call for the Ajax approach while some won’t. I mean look at google maps, such an application, which requires an asynchronous communication between client and server may require Ajax. On the other hand it might be overkill or overzealousness to implement Ajax is some domain. The last time I checked, our good old google page still refreshes.
NO3: Ajax is not a HACK
Ajax, in some quarters, is referred to as a HACK. Wrong! Ajax is perfectly not a hack. I mean if Ajax is a hack then stuff like lamp should also belong to the hack club.
The principle of Ajax is simple. It is having different technologies, in their different domain, working together in a holistic approach: Javascript, whose domain is the browser, remains in the browser, the XMLHttpRequest which handles the asynchronous request does nothing more but that, XML or JSON, takes care of the data wrapping while PHP, Python, Java, or whatever server side language you choose handles the back end. So tell me where the hack is, in that set up?
NO4: Ajax is not overkill on the browser
I have heard the browser described as just a document rendering application and that it is eerie to use it in such a manner that Ajax suggests, that is, as a User Interface. Wrong!
Maybe some years back when the browser was just an application that parses HTML codes and displays it as directed, such a description as a document rendering application would have been apt; But not the browsers of today.
API’s like the DOM, BOM and things like plug-ins etc. which have crept into the browser over the years now makes it more than just a rendering application but could easily pass for a ‘maturing’ User Interface.
No 5: Libraries are not bad
Dojo, MochiKit, Script.aculo.us, AJASON, and the rest of them.
Having code libraries is not evil and neither is it new. Libraries have been in existence since time immemorial or what is STL to c++ and having libraries that prevents you from the hassles of writing a lot of code and at the same time taking care of problems that are peculiar to the Ajax architecture is not such a bad thing…at all.
Is YouTube Evil?

The recent $1bn threat coming on Youtube from viacom is no longer hot news.
And I am hearing that Youtube has gone on some recent video deleting binge.
I’m just crossing my fingers waiting to see where this will lead to.
Personally I think the whole 'new media'/'social-network-sharing' movement is cool. I’m not totally against it. But I think if a business model blatantly aids, copyright infringement without putting in place machinery to curtail it, then maybe such a model is evil.
I’m not hoping to see another napster episode. Instead I hope stakeholders would parley up to find mutual benefits that can be derived from sites like Youtube. Cue should be taken from the BBC-Youtube agreement .
Tuesday, February 27, 2007
Keeping the spiders off
For whatever reason you might have, you may want to prevent portions of your website from being indexed by Google or any search engine for that matter. It might be a matter of choice or maybe it makes no sense to have that portion of your site in any search engine’s database. Anyway, keeping spiders off contents of your site is something you can easily do. Here are two methods to it:
First method is the robots.txt file way. The robots.txt is the first file that a search engine visits on your site. With the robots.txt file, you can instruct a search engine to index or not to index your site. Like someone aptly put it, the robots.txt file is like a snooty nightclub bouncer with a velvet rope, it decides which search engines enters your pages.
The robots.txt is just your regular text file that you will have to put in the root directory of your site. A typical one looks like this:
Which tells Google’s spider, googlebot, not to index the confidential files,private directory, and constitution directories. It also disallow all spiders (indicated with the wild card asterisk) from the /cgi-scriots/ directory.
It is worthy to note that compliance to the robots.txt instruction is strictly by choice and not compulsion. A search engine might decide to ignore the robots.txt file, but most renowned search engines do actually obey the robots.txt file.
The second method involves you putting a specific meta tag into the page you want to exclude from a search engines index. It takes the following form:
<meta name= “robots” content= “noindex, nofollow”/>
This will prevent search engine’s robots from indexing content or following links from the page.
Robots.txt
First method is the robots.txt file way. The robots.txt is the first file that a search engine visits on your site. With the robots.txt file, you can instruct a search engine to index or not to index your site. Like someone aptly put it, the robots.txt file is like a snooty nightclub bouncer with a velvet rope, it decides which search engines enters your pages.
The robots.txt is just your regular text file that you will have to put in the root directory of your site. A typical one looks like this:
User-agent: googlebot
Disallow : /confidential files/
Disallow: /private directory/
Disallow: /constitution/
User-agent : *
Disallow: /cgi-scripts/Which tells Google’s spider, googlebot, not to index the confidential files,private directory, and constitution directories. It also disallow all spiders (indicated with the wild card asterisk) from the /cgi-scriots/ directory.
It is worthy to note that compliance to the robots.txt instruction is strictly by choice and not compulsion. A search engine might decide to ignore the robots.txt file, but most renowned search engines do actually obey the robots.txt file.
Robots Meta Tag
The second method involves you putting a specific meta tag into the page you want to exclude from a search engines index. It takes the following form:
<meta name= “robots” content= “noindex, nofollow”/>
This will prevent search engine’s robots from indexing content or following links from the page.
Monday, January 22, 2007
Workshop at EMDI

Thursday the 18th saw me at Akure, where I was invited to teach on web designing, alongside kazar, at a workshop organized by EMDI.
It was an eventful experience for me since that will be the first time I will be visiting Akure.
I talked on the history of HTML and how it evolved to XHTML and where CSS fits in the picture. I made mention of the need for standardization and why we have bodies like W3C.
I later introduced the class to the vocabulary of HTML explaining the concept of tagging letting them write tags using MSnotepad. And later I introduced them to Dreamweaver, their excitement was another factor that made the whole workshop a rewarding experience for me.
The workshop’s tight schedule didn’t allow me time away for some sight seeing and picture taking; something I would have love to do.
It was fun and I even got to learn some new nifty tricks I could do with Dreamweaver while preparing for the workshop.
Friday, January 12, 2007
Introducing iphone

Imagine a smart phone that doesn’t have key pads…
But how do you compose your Sms then?
You punch on the screen’s virtual key pad.
Imagine a phone where you can pan content like you do your pdf documents…
Imagine a phone that allows you to maximize your view of an image on a web page by just finger clicking it…
Imagine a phone whose display turns vertical if the phone is held vertical and if the phone is held horizontal, your display adjusts accordingly…
These are just part of the features of Apple’s new product called iphone. A smart phone that introducing a lot of innovation in the area of user-interface and usability.
What exactly is the iphone? Apple’s site says…
iPhone combines three products — a revolutionary mobile phone, a widescreen iPod with touch controls, and a breakthrough Internet communications device with desktop-class email, web browsing, maps, and searching — into one small and lightweight handheld device. iPhone also introduces an entirely new user interface based on a large multi-touch display and pioneering new software, letting you control everything with just your fingers. So it ushers in an era of software power and sophistication never before seen in a mobile device, completely redefining what you can do on a mobile phone.
Personally, I think the coolest part of the iphone is its user interface. Smart phones are not new but iphone’s user interface is sure a revolution. Apple is trying to reinvent how we interact with the phone and I think iphone is impressive enough.
Head for Apple’s site to get a glimpse of what the iphone can do.
Subscribe to:
Posts (Atom)