21
edits
AniDB:AJAX development: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 111: | Line 111: | ||
[''sphere - I'm not sure about load tolerance too. This has to be tested if we ever moved there. What attracts me here isn't just the set of features (for which there are many libraries which can do very sophisticated stuff). Rather, it is the ease and intuitive way whereby a 'template' is declared. And these templates are potentially reusable by other people. e.g. From a single AJAX DOM, I could have one template that generates the basic anime info, another that generates the episode list. These two templates can be used on other pages as well to provide the exact view by linking in the template content which can be stored statically somewhere. The typical page designer just do things like 1. create a div, 2. load an xml and a compatibe xsl, 3. call some javascript function to render the page. Similar to styles, these template files can be customized and 'shared' between users.''] | [''sphere - I'm not sure about load tolerance too. This has to be tested if we ever moved there. What attracts me here isn't just the set of features (for which there are many libraries which can do very sophisticated stuff). Rather, it is the ease and intuitive way whereby a 'template' is declared. And these templates are potentially reusable by other people. e.g. From a single AJAX DOM, I could have one template that generates the basic anime info, another that generates the episode list. These two templates can be used on other pages as well to provide the exact view by linking in the template content which can be stored statically somewhere. The typical page designer just do things like 1. create a div, 2. load an xml and a compatibe xsl, 3. call some javascript function to render the page. Similar to styles, these template files can be customized and 'shared' between users.''] | ||
Sphere | ==== Multilingual support ==== | ||
[Sphere] Added this as afterthought. I tried fooling around with the basic anime info xslt and managed to add in translation time multilingual support. basically I created a very simple string table in another xml that specifies a language and a list of key-value pairs that denotes a key in some default language (english in this case) and a translated value. | |||
<nowiki> | |||
<presentation> | |||
<animeinfo> | |||
<stringtable lang="xx"> | |||
<string id="1"><key>main</key> | |||
<value>niam</value></string> | |||
<string><key>search</key> | |||
<value>hcraes</value></string> | |||
<string><key>calander</key> | |||
<value>rednalac</value></string> | |||
</stringtable> | |||
</animeinfo> | |||
</presentation> | |||
</nowiki> | |||
== Comments, propositions and whatever else == | == Comments, propositions and whatever else == | ||