December 1, 2006
4:16 pm

Edwin Khodabakchian and Olivier Devaux started off integrating Google Custom Search capabilities into Vulnpedia.com by using the Google JavaScript tools.

They wanted to go beyond this, and written in Experience #1: Miro, Ajaxlets and the Google Custom Search API which goes through various iterations of the project.

Miro is a light-weight template engine for applications which take advantage of Ajax. It focused only on one task: how to make it easy for developers to convert in the browser, a Javascript object or an XML DOM object into a fragment of HTML code that can later be assigned to a div using div.innerHTML. As an Ajax developer, you are forced to make these types of conversion 1) each time you want to dynamically change in the client a part of your document (example: sort a list of rows) or 2) each time you have made an async call to the server using HTTPRequest or <script...> and want to present and display the result to the user. The goal is to get rid of htmlFragment += "some <a href=\"" + var1 +"\"> which is very painful to generate and even more painful to maintain.
Continue for more info....

ajaxian

Miro, light-weight, JavaScript, Rendering Engine

Loading

Contextual Related Posts:

No followup yet

Leave a Response

Comment Preview
« Send Me a PicGoogle Spreadsheets API »
Feed Icon

Subscribe via RSS or email: