Category: MooTools

Clientcide: New Form Validators and Documented Beta Code

Aaron Newton has released some new form validators (with help from contributor Chafik Barbar) and documentation for his beta code. Everyone has to deal with form validators one way or another. I\’ve posted on one from MooTools.Floor, but this is a different way of doing things. Continue reading Clientcide: New Form Validators and Documented Beta Code

Run Javascript Functions Without using \’domready\’ Event

I don\’t really like using the \’domready\’ event. The idea of adding another event to the window object just bugs me. So here\’s the alternative. In short, an array is created, functions you want to run are added to the array, and when the page reaches the bottom the functions in the array are run. Continue reading Run Javascript Functions Without using \’domready\’ Event

What I Learned About Multi-threading in JavaScript

There\’s no such thing. Correct me if I\’m wrong, but multi-threading in javascript does not exist. But we can simulate it, as is discussed by James Edwards. How does it work?

It all hinges on the use of asynchronous timers. When we run repetitive code inside an asynchronous timer, we’re giving the browser’s script interpreter time to process each iteration.

Continue reading What I Learned About Multi-threading in JavaScript

MooTools.Floor Does Form Validation Right!

We\’ve all dealt with form validation one way or another and I didn\’t find one to my liking. I was mulling over the idea of writing my own for a while and then I read Ajaxian\’s blog today about a really awesome MooTools form validation class from MooTools.Floor. MooTools.Floor actually announced their FormCheck v1.4 form validation class in July 25, 2008. Continue reading MooTools.Floor Does Form Validation Right!

Moo-Comet aka MooTools Request.Comet

Ever heard of Comet? I heard it long ago when it just started out in Ajaxian\’s post. They described it best:

Alex Russell has coined a term for a flavour of Ajax that’s been getting more attention of late. Comet describes applications where the server keeps pushing – or streaming – data to the client, instead of having the browser keep polling the server for fresh content.

Correct me if I\’m wrong but I think the Dojo framework may have been the first to support Comet. Some of the uses I know of is chat and stock ticker updates but I\’m sure there are tons of uses.

Now, when I learned about Comet, I was using MooTools 1.0/1.11. I was really interested in trying out this new tech and was trying to learn as much as I could. I knew that MooTools didn\’t have a Request.Comet so I looked into building one. Long story short, I wasn\’t successful because other projects took up my time, but my curiosity never went away.

Doing a search for Moo-Comet has led me to Benjamin Hutchins and his Request.Comet example. He has a MooTools 1.2 and 1.1 version of Request.Comet.

His code us up on Google Code for all the world to see. Great job, Ben! I can call you Ben, right?

MooTools Delete Key

David Walsh has kept us informed in his post about the delete key event.

To detect the delete key, this does not work because \’delete\’ is a reserved word in javascript:

var isdel = Event.Keys.delete;

So here is the proper way:

var isdel = Event.Keys[\'delete\'];

He put it best:

As flexible as Moo’s language is, you can’t get around the reserved words!

Great job on keeping the MooTools community well informed, David!

MooTools 1.2.1 hits the web!

If you haven\’t found out already, MooTools 1.2.1 is now available. The MooTools dev team has stated that it won\’t break any of your MooTools 1.2 code! It\’s also working with Safari 2 again. Congratulations to the team for a job well done!

You can check out the changelog for a list of changes.

Go and update your copy.

Now with 1.2.1 out, the dev team will be working on 1.2.2 and 1.3. You can get all the info straight from the horses.. err.. cows.. mouth, you know what I mean.