Attaching keyboard events to alternative browser objects

It took me way too long to find out why I could not listen to keyboard events for DOM objects other than the window, form objects, or links. All you have to do is give the div or any other DOM element a tabindex. Below is an example using the prototype framework.

1. var myDiv = new Element('div' { 'tabindex': '0' })


2. myDiv.observe('keypress', function(e) {


3.   var code;


4.   if (!e) var e = window.event;


5.   if (e.keyCode) code = e.keyCode;


6.   else if (e.which) code = e.which;


7.   alert(String.fromCharCode(code));


8. });

Saving Javascript Objects to an SQL Database

Why create intermediate files when you can just store everything in a database? With the ability to store information on local databases like SQ lite and SQL servers being given away like candy from every web hosting service why not use their convenience and security for your websites.

I am going to post some code I wrote to directly save javascript objects to an SQLite database using Google gears. It's an example of writing a single method to save any type of object and I think changes the way we think about saving objects. Correct me if I am wrong, but this seems to be the least amount of code from any programming language for saving objects to an SQL database.

1. function addSQLite(obj, table) {


2. query = "INSERT INTO " + table + " VALUES (";


3. z = 0;


4. for(x in obj) {


5. switch (typeof(obj[x])) {




7. case 'string':


8. if(z>0) query += ",";


9. query += "'" + obj[x] + "'"


10. break;




12. case 'number':


13. if(z>0) query += ",";


14. query += obj[x];


15. break;


16. }


17. z++;


18. }


19. query += ")"


20. db.execute(query);


21. }

This basically just puts a string together based on any objects properties. All you would have to do it make sure there is a table in the database with the same properties and you have yourself an incredibly versitale SQL function.