12 July 2006
My Pet Peeves of Dojo ToolKit
Is it me or is it Dojo too hard to use?
I spent around 3 to 4 hours two nights ago trying to put pull some widgets together namely datepicker, timepicker and colorpicker and boy, was that hard to figure them out.
Couple of pet peeves I have...
1. WHY WHY WHY do you load javascript libraries using ajax? I really don't feel it's necessary!!
2. Why why why aren't the ajax Iframe proxied? My work place disabled activeX for security purpose and a good one might I say. My page with dojo is completely broke.
3. Why the hell can't I simply get the value of my text using getElementById??? Why is it that everything has to be so...Dojo?
4. For god's sake, write some documentation ppl. I know it's only v0.3, but other frameworks that existed for the same amount of time, no matter how small they are, they have more documentation than Dojo.
To be fair, dojo IS very object oriented and I like how they designed their framework. It's easy to create a widget system and it makes third party author's work easier. In addition, they provide a load of components that I haven't seen elsewhere like split pane, fisheyes, timepicker, just to name a few.
However, until Dojo fixed 1, 2, and 4, I don't think I'll be using them. The time I spent researching on the timepicker was ridiculous. Anyway, complain ends here. I'll post my findings and how to use Dojo later in another post.
Comment Notification
If you would like to receive an email when updates are made to this post, please register here
Subscribe to this post's comments using
Comment Policy: No HTML allowed. URIs and line breaks are converted automatically. Your e–mail address will not show up on any public page.