modisposition

I am not sure I read the entire recent " war " in the PHP general mailing list about the best PHP Template Engine Option but, generally speaking, this argument is truly loads of solutions and controversial opinions. Here I am with mine. PHP 5 And In Core DOM, XML and XSLT Apparently, all these " Smarty adorers " did not consider that PHP 5 introduced a lot of core classes to work over DOM, XML, and transform them via XSL files. Nothing to do, they prefer to move an entire template application rather than use the best native, fast, in core, solution . Here a couple of reasons to generally prefer XML and XSL Transformations rather than whatever engine, specially those written in PHP itself, a not that fast interpreted programming language. Think Portable Apparently developers like to be stuck forever in a single programming language , something I cannot even try to consider, since Information Technology means Flexibility and Updates . An extremely valid point to cho...

I have updated my lightweight JXON library right now, lightly improving them, and adding a consistent documentation for each method as well. At this point, the last thing I could do about JXON, is to talk about what exactly is, and what is not at all. JXON IS An intermediate, well defined, layer between native JavaScript variables, and a generic page content (their representation inside the layout) A fast and cross-browser JS to XML, and vice-versa, parser A human comprehensive way to represent JavaScript Object Notation via XML using a natural, lightweight, and unambiguous, schema, that will make XSL files creation, manipulation, and maintenance, more clear and natural than ever, working over both XPath, and semantic data types nodes with optional keys for object members A simple and crossbrowser global object, with few methods to transform JavaScript raw data into a valid (x)HTML layout page, or portion An advanced, XSLT based, enterprise ready way to represent d...

It seems to be the time to talk about JavaScript template engines , and DocumentFragments , so here I am with my last idea: a JavaScript XML Object Notation transformer . Introduction There are a lot of ways to interact between the client, and the server, in a W3 friendly way, such Ajax, the classic remote scripting, Comet, and last, but not least, and probably first of all, XML . The latter " protocol " is one of the most flexible, compatible, and cross platform one you can find in the IT sector, in a word: universal. Over XML we are loaded of different standards to transport every kind of data, which one should be compatible with browsers, parsers, and preferably with JavaScript DOM implementation as well. One of the main limitations I have spotted about XML to JavaScript and vice-versa conversion, is the data type, usually lost, and the prolixity of JavaScript data representation. JSON is great, but whtat's up if we destroy its nature? The JavaScript Object Notation m...