Dynamic code for Javascript ...

I went with dynamic code instead. Unlike on the server side, it’s a very bad idea to load tons of javascript classes into a browser. I did something to this effect:

var someSQLObj = Class.create();
someSQLObj.prototype = {
objName  : ’someSQLobject’,
errMsg   : ‘Object could not be loaded’,
errMsgUpdate   : ‘Could not update’,
data     : null,
initialize: function(id){
var err = this.errMsg;
this.objName = id;
new Ajax.Request(’/autoclassajax.php?action=getObject&SQLObj=’ + this.objName,
{
method:’get’,
onSuccess: function(transport){
var response = transport.responseJSON || err;
this.loadData(response);
},
onFailure: function(){ alert(err);  }
});
},
loadData : function(data){
this.data = data;
// if the HTTP request is good, it should be the SQL object as a JS object
alert(this.data);
},
getParam(param) {
var prm = ”;
eval(’prm = this.data.’ + param + ‘;’);
return prm;
},
setParam(param) {
eval(’this.data.’ + param + ‘ = prm;’);
},
save: function() {
var err = this.errMsgUpdate;
new Ajax.Request(’/autoclassajax.php?action=setObject&SQLObj=’ + this.objName + ‘&jsonData=’ + escape(Object.toJSON(this.data)),
{
method:’get’,
onSuccess: function(transport){
var response = transport.responseText || “no response text”;
#alert(”Success! ” + response);
},
onFailure: function(){ alert(err);  }
});
},
};

Roughly anyway.  At any rate, I have reduced the SQL generator robot to only generate PHP classes and connector bindings, then I am loading the objects into JS dynamically, and producing the client side div.innerHTML code on the fly. The less Javascript code the better. It’s a performance issue.

 View Full Story.