modisposition

Update Before other silly flame/blame will start, I have already twitted that my next laptop will be a netbook. Here the related tweet . let me summarize the story: at that time I had a girlfriend with an iPhone so I though why on earth shouldn't I buy an Android instead? If I need some test online I'll have both to test it , and I've rarely been that wrong. Wanna Develop for iPhone? Buy a Mac As marketing strategy sounds " cool " except I do not want to develop iPhone application, the present and the future is online, why on earth should I learn another programming language from the scratch, Objective-C, to develop something that will be relatively soon replaceable via WebKit and a good host? Wanna Develop Web for iPhone? Buy a Mac Again!!! Unbelievable, there is not such a thing: online iPhone tester , everything I found Googling was about a silly image with an iframe just to test the iPhone size ... are you kidding me ? It's like put IE inside an iframe ins...

I am proud to announce my last Web 2.Next creation, Formaldehyde , the most simple, lightweight, scalable, and complete (for its simplicity) Ajax and PHP Error Debugger. I described everything in its dedicated Google Code Project Page , but just to summarize without many other words, this is the common deployment situation : while this is what's up with a single formaldehyde.php file inclusion: I hope you will like it, can't wait for some comment :geek:

A common pattern to develop JavaScript libraries is to use different behaviours inside methods, and based on browser, or browser plus its version. For about 80% of cases, these behaviours are Internet Explorer dedicated. This approach is good enough, otherwise we could not have a wide variety of libraries to choose, but is this way to develop libraries the best one? These are some pro concepts: libraries could be usually merged into a single file, so we can add only one script tag, and for every browser libraries maintenance or improvements are focused into one, or more, constructor, function, or method The expected result is, usually, a method that is capable to understand which browser is running them, and what to do for that specific case. // common libraries development pattern function myGorgeusLib(){}; myGorgeusLib.prototype.sayHello = function(){ if(self.attachEvent) attachEvent("onload", function(){alert("Hello")}); else if(self.addEventLis...