This post originated from an RSS feed registered with Java Buzz
by dion.
Original Post: Links for 2009-03-10 [del.icio.us]
Feed Title: techno.blog(Dion)
Feed URL: http://feeds.feedburner.com/dion
Feed Description: blogging about life the universe and everything tech
Yahoo! for the future
"Where’s the glitz, though? The dazzle? What can an artist do without a canvas? We could have audio and video, and no plugin! You won’t miss my congratulatory advertisement this time. You deserve to know. And to know the joy of SQL, finally, in the browser. Forms with placeholders and validations built-in! Vectors! details! And the semantics, oh the semantics! What’s a poor old Google to do, parsing through divs and spans when it could have nav, article, and aside? Won’t somebody please think of the robots?
But let’s leave the HTML argument be, for now. We can at least agree that CSS is in a wonderful place. JSON’s little half nephew is doing all right. "
Technology Review: An Upgrade for the Web
"The next generation of HTML, the markup language that is used to build most Web content, promises to make Web applications work even better. Some proposed features of this new standard--HTML 5--are already being built into several popular browsers, offering a glimpse of an application-enabled Web." Nice work @blizzard :)
Bespin learns JavaScript
Malte is my hero: "Today I hooked up bespin to Brendan Eich's JavaScript parser written in JavaScript.
Some evil recursive tree wrestling later, we can now find out the names, line and column numbers of all functions in a JS document. I also added some logic, to look up the tree for anonymous functions to see whether they were declared in an object literal, so we can use the key as the inferred name.
The parse tree could be used for all kinds of interesting things, like outlines and even IntelliSense(TM)(R). JS being a very dynamic language this, however, only goes so far. In particular systems like Joose or even dojo's simplistic object system do not go so well with static analysis.
As a next step, I'll move the parser to a web worker (I designed the API to be async, so this should be easy) and implement a simple outline view."
Previous Topic
