E4X, ActionScript 3 new “sublanguage”

Since I’ve heard the voices about the upcoming E4x in actionscript 3 I awaited this moment…
Finally ActionScript supports E4X and we can kick away the old XML object (always supported for backward compatibility)! we can stop using all the various xml2object classes created in these years, we finally have a Buy Cheap Paper Online validating parser, so we will see finally well formatted XML files from flash users 🙂
But finally we have a powerful “language” with a very strong syntax.

I’ve written a small tutorial with a quick guide  about actionscript3 and e4x basic syntax (without including Namespaces and QNames for the moment)

http://www.sephiroth.it/tutorials/flashPHP/E4X/index.php

P.s. I forgot to say that E4X is also available in the Geko1.8 browser (such as Firefox 1.5). For more info see this article: http://developer.mozilla.org/en/docs/E4X. Unfortunately E4X ins’t supported by python, neither there’s a module for it 🙁

Actionscript 3 ?

Recently Macromedia release some news about Flex 2…and what we can find in one page (you can see it here) ?
“With ActionScript 3.0, we have achieved more than simple compliance with the ECMAScript standard; Macromedia now chairs the ECMAScript committee and helps drive its evolution. ActionScript 3.0 features a compilation mode for stronger compile-time type checking that provides the benefits of languages such as Java or C#. It supports new features to streamline data manipulation, including the E4X (ECMAScript for XML) standard, which extends the language and adds XML as a native data type allowing developers to more naturally interact with and manipulate XML. It adds regular expressions support for better text parsing and processing. It sheds some of the ad hoc event handling schemes in the old virtual machine in favor of a unified model based on the W3C DOM Events standard. And it has significantly updated APIs aimed at the application developer audience.
For a complete overview of the new capabilities, stay tuned as we release an overview of ActionScript 3.0 and the Flash Player 8.5 alpha.”

It seems that on 17th October we’ll have a public preview of Flash Player 8.5…I’m curious a lot!
http://www.macromedia.com/devnet/…/flex2_intro.html

Will Flash 8 support E4X?

An unintentionally mail posted in the Flex mailing list talks about one of the new Flex 2.0 features, the support of E4X.
This means that probably the new flash player will support it also… This should be a great step over the old “DOM” flash support.. in this case XML entities will be threated as builtins objects Read more about ECMAScript for XML (E4X) Specification: http://www.ecma-international.org/publications/standards/Ecma-357.htm

see the original post

XML2Object revisited

Dissertation Using Qualitative Research Methods An Special Writing Paper XML2Object revisited class.
Basically it works in the same ways as the previius one, but now in the parseXML method it can be defined a 2nd parameter which will tell to the parser to put all xml nodes into arrays. In this way all variables created into the returned object will be stored into array. for example:

Umi Thesis Purchase import it.sephiroth.XMLObject; myxml.onLoad = function(){ var data = new XMLObject().parseXML( this, true ); }

How To Start A College Admissions Essay Hook The second addition to this class is the parseObject method, which will convert any object into an xml. for example, this code:

import it.sephiroth.XMLObject; myobject = { attributes : { name : "custom object", type : 1 }, item : [ { name : "Varese", code : "VA" }, { name : "Milano", code : "MI" } ], channel : { name : "City", country : "Italy" } } data = new XMLObject().parseObject(myobject,"TEST");

will produce this xml string:

<?xml version="1.0"?> <TEST type="1" name="custom object"> <item> <name>Varese</name> <code>VA</code> </item> <item> <name>Milano</name> <code>MI</code> </item> <channel> <name>City</name> <country>Italy</country> </channel> </TEST>

And here’s the class code:  XMLObject.as

XML2Object

How To Start My Personal Statement This class, that is just a translation of a simple set of function written for Flash MX, translates any kind of XML document into a readable Flash Object. This could be the core for projects XML oriented..
in fact i work often on xml based projects…

/** * @class it.sephiroth.XML2Object * @author Alessandro Crugnola * @version 1.0 * @description return an object with the content of the XML translated * NOTE: a node name with "-" will be replaced with "_" for flash compatibility. * for example will become FIRST_NAME * If a node has more than 1 child with the same name, an array is created with the children contents * The object created will have this structure: * - obj { * nodeName : { * attributes : an object containing the node attributes * data : an object containing the node contents * } * @usage data = new XML2Object().parseXML( anXML); */ //import utils.string class it.sephiroth.XML2Object extends XML { private var oResult:Object = new Object (); private var oXML:XML; /** * @method get xml * @description return the xml passed in the parseXML method * @usage theXML = XML2Object.xml */ public function get xml():XML{ return oXML } /** * @method public parseXML * @description return the parsed Object * @usage XML2Object.parseXML( theXMLtoParse ); * @param sFile XML * @returns an Object with the contents of the passed XML */ public function parseXML (sFile:XML):Object { this.oResult = new Object (); this.oXML = sFile; this.oResult = this.translateXML(); return this.oResult; } /** * @method private translateXML * @description core of the XML2Object class */ private function translateXML (from, path, name, position) { var xmlName:String; var nodes, node, old_path; if (path == undefined) { path = this; name = "oResult"; } path = path[name]; if (from == undefined) { from = new XML (this.xml); from.ignoreWhite = true; } if (from.hasChildNodes ()) { nodes = from.childNodes; if (position != undefined) { var old_path = path; path = path[position]; } while (nodes.length > 0) { node = nodes.shift (); xmlName = node.nodeName.split("-").join("_"); if (xmlName != undefined) { var __obj__ = new Object (); __obj__.attributes = node.attributes; __obj__.data = node.firstChild.nodeValue; if (position != undefined) { var old_path = path; } if (path[xmlName] != undefined) { if (path[xmlName].__proto__ == Array.prototype) { path[xmlName].push (__obj__); name = node.nodeName; position = path[xmlName].length - 1; } else { var copyObj = path[xmlName]; path[xmlName] = new Array (); path[xmlName].push (copyObj); path[xmlName].push (__obj__); name = xmlName; position = path[xmlName].length - 1; } } else { path[xmlName] = __obj__; name = xmlName; position = undefined; } } if (node.hasChildNodes ()) { this.translateXML (node, path, name, position); } } } return this.oResult; } }

An Example usage with this file:
http://www.sephiroth.it/tutorials/flashPHP/indice.xml

import it.sephiroth.XML2Object;
var oXML:XML = new XML ();
var sXML:String = "indice.xml";
oXML.ignoreWhite = true;
function xmlLoaded (success:Boolean) {
        if (success) {
                trace (success);
                _root.ObjFromXML = new XML2Object ().parseXML (this);
                delete this
        }
}
oXML.onLoad = xmlLoaded;
oXML.load (sXML);

A PHP domxml class in flash style!

Some days ago Daniele, a friend of mine, point my attention to an opensource project hosted on sourceforge that is very interesting for PHP/Flash guys 🙂
This module permit to do an xml parsing, in PHP, using a dom xml in the same way we already do in flash.

Here a little example i made using this class:

<?
// include the php module
include('lib.xml.inc.php');
// load an external xml source
$test = new XML('test.xml');

// make a simple parsing, in AS style ;)
$childs = $test->firstChild->childNodes;
for($a = 0; $a < count($childs); $a++){	
echo "nodeName " . $childs[$a]->nodeName . "<br />";	
echo "nodeValue " . $childs[$a]->firstChild->nodeValue . "<br />";
}
?>

as you can see, we’re already familiar with firstChild, nodeName, nodeValue… etc..
I always hate the PHP SAX parser, and always always prefer a dom xml parser, much more simple to create and to read.