This morning before going to work I had a little chat with a friend of mine.
me:
morning
what’s your opinion about javascript?
friend:
Necessary evil.
me:
hmm ok you’re on the same line as sans
http://isc.sans.org/diary.html?storyid=2457&rss
friend:
http is too dumb to do what people want to do.
And javascript is better than java.
And it’s more cross platform. But it’s tough to write and easy to hide evil.
me:
i am “discovering” javascript the last months
(i know, 10 years late)
i think it rocks.
makes me totally reconsider the way webpages could work
building a part now where ppl can make teams, by drag and dropping members
without a single page refresh.
friend:
Right.
Welcome to web 2.0.
Well, we’re on 3.0
But you can join 2.0
me:
yh i heard the 3.0 for the first time this week
what’s 3.0 btw?
no internet? borg?
friend @ 7:15
It’s nonsense.
Like 2.0
me @ 07:15
like 2.0 is
gmta, rofl
Update
Another friend pointed me (after reading the above> to this userfriendly cartoon…
Posted by:
Merlijn on Friday, 16 of March , 2007 at 08:36
Tags:
javascript,
web 2.0 Categories:
BOFH
Comments:
be the first (opens in a pop-up window)
Add this post to
del.icio.us or
digg it
Apple released a public beta of Dashcode to ADC members (including the free accounts). I have to say I am deeply impressed.
It has still some quirks, but it is stable and has stunning features.
I started this week to play around with it and I can assure you it’s fun.
Implementing a Scrollarea gave some problems for me tho.
(I admit, has a lot to do with my JS n00bness…but hey…)
If you you update the content of your scrollarea, don’t forget to refresh it…
example:
if (logstatus == 0) {
loginhoud = logcall.outputString;
content.innerHTML = loginhoud;
document.getElementById("scrollArea").object.refresh();
}
else {
content.innerHTML = "Problem fetching server data...";
}
I think this is missing in the documentation…(yup, reporting it to Apple as well).
Posted by:
Merlijn on Wednesday, 10 of January , 2007 at 08:39
Tags:
Apple,
dashcode,
javascript,
safari Categories:
Apple,
Coding,
OS X
Comments:
be the first (opens in a pop-up window)
Add this post to
del.icio.us or
digg it
Mental note to myself:
When making a POST request with XMLHttprequest and Safari(v2.0.4), always generate some content for the browser.
If not, the status will always be undefined.
example:
if (!$mysqli->query($insert)) {
trigger_error("error writing data: ".$insert);
exit;
}
else {
echo "0";
}
This costed me some hours pulling my hair….
The following javascript works like a charm when you return a “0″ at the end of the php file called with POST. If you don’t return anything, Safari will decide that the HTTP headers are undefined and thus call the error handler.
KwAjax.ContentLoader.onReadyState=function(){
var req=this.req;
var ready=req.readyState;
if (ready==KwAjax.READY_STATE_COMPLETE){
var httpStatus=req.status;
if (httpStatus == 200 || httpStatus == 0) {
this.onload.call(this);
}
else {
this.onerror.call(this);
}
}
}
Posted by:
Merlijn on Friday, 15 of December , 2006 at 13:03
Tags:
AJAX,
javascript,
safari,
XMLHttprequest Categories:
Coding,
OS X
Comments:
be the first (opens in a pop-up window)
Add this post to
del.icio.us or
digg it