/*
* display flash message
*/
function displayStatusMessage(status, msg, timeout) {
var msg = swapDOM(’statusmessage’, DIV({’id’: ’statusmessage’},
DIV({’class’: status}, msg)));
if (timeout) {
msg.hidecb = callLater(timeout, swapDOM, msg,
DIV({’id’: ’statusmessage’}, null));
}
connect(msg, ‘onclick’,
function(e) {
var msg = e.src();
if (msg.hidecb) {
msg.hidecb.cancel();
}
disconnect(msg);
swapDOM(msg, DIV({’id’: ’statusmessage’}, null));
}
);
}

Please help the Message Box Seems Preety cool and i would like to use it in my web Pages

Thanks

Thanks for pointing out the typos. As you can see I modified this from the project I’m currently doing, so I changed the names to anonymize it a bit… it seems I missed a few ;)

As for using jsonify, yes it is a bit superfluous now, but previously there were some issues with passing numbers that weren’t integers. SQLObject was returning long ints for some ID’s. Basically I put the jsonfiy bit in to make sure that if I (or other people) were to pass more info than just a string that json.write wouldn’t barf.

I think this has been fixed recently, but I’ve left it there as a safety net.

Also I’m not sure why you need the call to jsonify within the json.write() within the controller code. I’m running tg0.8 and don’t have a jsonify - but the json.write seems to do a reasonable job anyway…

Many thanks for the write-up.

Ideally you’d be using an API instead of string mangling to generate the JSON document. That way formatting it correctly is someone else’s problem and it’s easier to test that way.

I also have a feeling that your use of Kid interpolation in the script tag is going to have edge cases. You really shouldn’t do that either.. what I do is I make a hidden input field with the value as the data, and just grab it out from the script. That way, you don’t have any generated code at all and the escaping behavior is definitely already correct since it’d be normal HTML attribute value escaping.