AniDB:AJAX development: Difference between revisions

I've seen the basic stuff of what's going on. I've also tried to tweak the xml specification a little to single out those that are general (to all of anime community) and those that are anidb specific (I use a namespace idea so that anidb stuff like ids, ratings etc are clearly marked).

Also tried throwing in a more general resource tag so that anything can be referenced there. (one example is the anime's main image, any weblinks to external databases, official sites, additional links to images and videos etc)

As I was reading up stuff, it occured to me that if we had some ajax-ready xml api, it could be far more useful than just for ajax.

Using XSLT, what was traditionally done on server (transforming data to html) can be pushed to the client. If the data is carefully segmented into largely static ones (like basic anime info that doesn't update a lot) and more dynamic ones (like episodes and files), there is potential gain if inter-server caching can be exploited (since the xsl does not change at all, and the xmls can be chopped up such that some parts do not need to be updated that often and can be locally/isp cached).

The only shortcoming is that xsl is a pure declarative language. So to achive some dynamic formatting (e.g. say if you want every odd row in a table to have different style), may need runtime javascript.

There are some quirks though... e.g. I can't see the generated html source anymore. when I look at source, I see the xml only. dunno whether that's good or bad atm.

one nice thing about this is that the AJAX parts can be built directly on the xml so one common data format may serve the various clients (raw html, xslt, full ajax web app (see the javeline demo link I placed in the readme file))

anyway, attached a sample of what I was trying out. it consists of only a xsl and xml file. Just open the xml file in your browser and the xsl will be automatically applied. If you think this is interesting enough to the rest of the mods (regardless of whether it needs to be interested, I just thought that if they did not know yet, at least they should know that this is possible?)

btw, from the looks of things and the political reason you mentioned for not supporting ajax, I really don't know where to go start or where to go from here. If the general mood is to stick to what we have, does that mean that you and I are just working towards a closed door?

--episode list (no files yet) added. sorted on type and episode number. Episode title is chosen by <defaultlang>...</defaultlang> in the config part of xml. if the language is not found, it will take any language. If no title is found, it will display "unknown title"

--all the links on page is based on anidb.net, so any relative link still link correctly back to anidb site

I think I will take a break until there is feedback. xslt is just a middle ground, but it is probably the basis for future ajax development, as it totally separates the xml's dependency on formatting. If you are still busy, perhaps I can bring this to the forum by creating an ajax development thread?

 

http://forum.anidb.net/viewtopic.php?t=5653

 

 

Basically, the language codes are now decoded properly using xml's from ISO sources.  Whatever the language code is, be it 2 letters/3 letters etc, and whatever locale, as long as it follows the xx, xx_XX or xx-XX format, it will get decoded into language (+Locale if available).  I found that the xml file i used earlier only contains language, so it cannot decode langcodes like pt_BR : Portuguese (Brazil) properly.  Now I linked in codes from ISO-639 (language) and ISO-3166 (country) so theoretically, it can decode anything that have been seen before.

* Ups: Server throws out the xml (no html at all), which is also used for ajax.  so theoretically, when we have ajax, xslt comes for free.  the style sheet is static.  meaning can be cached etc. The xml file is also largely static (no dynamism due to user settings.  It only needs to change when anime data actually changes.)  Also allows splitting of data into domain.  e.g. the same basic anime xml used by all.  files and member only data can be sent in another separate xml to be merged on client's end.  XSLT is available on almost all modern browsers.

* Downs: There are still some browsers that don't do xslt. Also, a little hard to debug (that's a developer's problem), coz the source cannot be seen (if you look at src of a xslt generated html page, you won't see the html. you'll see the xml)

This is supposedly the real workhorse.  Unlike opening a XSLT-transformed XML (which does a one time translation), an AJAX client will be a constant webpage that dynamically updates its parts on receipt of new data.  E.g. if the user opens another anime, the ajax page will just request the required xmls and update itself.  The modern pattern is to implement XSLT/JST into it's components.  e.g. say I have a div set to contain anime episodes data.  After retrieving the xml, instead of doing the traditional parse by javascript and manually add in stuff, the modern way is to declare a template before hand (potentially stored statically as a separate file) and use a general translater engine to merge the xml/xsl.  makes client development a breeze, not to mention achieving component reuse (the xsl can be used in other pages too!)

* Ups: Rich web experience.  due to partitioning of xml data, potentially a large portion can be more static and cacheable.  meaning server only have to serve the differences. E.g. the server may serve the same anime and episode info to all people, but may send a per-user xml which contains settings, preferences and mylist stuff.  Lighten server load even further?  potentially allow even more user customization like the skinning system (server tells client which skin file you use, which can be set by you), coz now, you can change the entire layout of the page by setting a different xslt/jst file sets??

* Downs: requires javascript.  heavier on client end (but better client than server, imo).  Have to be made more robust coz there may be higher chances of computer amateurs messing stuff up on their client end (as compared to server-spoon-fed html)

This is the future.  And it is already here.  I've already highlighted the link in my mail to Fahrenheit (www.ajax.org).  It is a complete javascript-only, cross-browser development than can do most things that your typical desktop app can do.... windows, lists, trees.  you name it, it has it.  What makes it impressive is the ease with which it can be used.  cross-browser means that no need to deal with differences in browsers directly.  It really takes a lot off the mind of the developer in tinkering with javascript hacks to makes things work and allow more energy to be channeled into the important parts : Design.  What's more is that the platform is being developed/maintained continuously, so we get "upgrades" automatically when time passes without having to sink in extra manpower to keep things shiny.

* Downs: supposedly even more demanding on browser.  But from my testings on a typical 1.8 GHz AMD (single-cpu) using firefox 2, it seems to be still very light on cpu.