An AJAX option to remember

I always forget how useful is the “$(<selector>).load(‘url’, {para: meter});” function on jQuery.

It is really a problem solver when loading HTML structures.  I am converting some old code where I got HTML fragments to replace some existing content on the page and using the usual process, I’d have to do the AJAX query, call a callback procedure and then there I’d replace the contents of the section / div / whatever I wanted.

With jQuery.load I can do that on a single call and in a more effective way.

Silly thing and so simple that I always keep forgetting about it.

Dojo: Still not ready for business applications

I felt in love with Dojo.  I loved the way it interacted with my existing code and its compatibility with MochiKit (that I am currently using).

Unfortunately, I can’t migrate some business applications to it because Opera isn’t supported.

I did test a very simple website using Dojo 1.1.1 from AOL CDN where I implemented just some layout Dijit widgets and an accordion pane, but it wasn’t rendered correctly on Opera.

What happened?  I had to move back and remove Dojo from the code.  I’ll keep on looking at it, but for now I’ll have to search other JavaScript frameworks (jQuery and YUI come to my mind) to implement my applications.

As I said, too bad because I was really liking Dojo.

Accessibility when developing for the web

There are two concerns when speaking about accessibility: accessibility for disabled people and accessibility for “disabled” browsers.

I’m talking, on this post, about the second category.

So, is this really something that is needed nowadays?  Even the browser on my mobile phone has JavaScript support (though it doesn’t have Flash support) and can run a complex dynamic website without any special change or anything designed to be used on mobile browsers (be them Blackberries, iPhones or other mobile phones).

Some recommendations are to degrade the design when JavaScript is disabled, but the vast majority of users has no idea how to disable JavaScript on their browsers.  If some IT guy from a company does that, should you really be worried with this person accessing your website?  Of course, you are reducing the market for your product, but how many people are excluded?  Are they people that would “buy” some service from the website?  Is this amount of people worth the extra investment that it takes to design a website to degrade and to be pleasant when used fully dynamically?

It is something different — and getting popular

One of my clients is amazed at how one of our websites is getting attention from people from all over the world.

He’s been mentioning about somebody in Atlanta that has been using the site for two weekends in a row, using the site for two consecutive days last weekend.  “And the website is only in Portuguese!” he says.

We have both created a tool to work with curve fitting using R as the software base for the curve fitting algorithm.  It is still just a concept, but we have already decided on expanding that to include other algorithms besides linear fitting.  And we’re willing to make adjustment to points according to the equation from the curve.

Simple, yet efficient.

Of course, for the next version I’ll sneak in an English translation.  I still haven’t tried implementing any I18Nization with R (I’ll probably need to convert from lazystrings to Unicode before passing the string to R, though…), but it should work fine.