Easily. In fact, the entire system is built to be extended (for custom component handling), and the hardcoded functionality can easily be removed.
It works on the concept of tag handlers. When a tag is hit, the appropriate handler is fetched and it handles the tag parsing. A handler just implements a basic interface (ASTagHandler), that defines how a tag is parsed, and how child objects are added to the tag. I borrowed this idea from the way ASP.NET config files work. The only tags that are hardcoded into the system are "include" (for bringing in external asml files), "objects", "theme" and "connectors", and even those can be stripped out quite easily. Take a look at the org.actionstep.asml namespace. It's all in there, and is filled with comments so you'll be able to figure out its inner workings. Scott -----Original Message----- From: [EMAIL PROTECTED] on behalf of Philippe Sent: Sat 11/5/2005 3:47 PM To: Open Source Flash Mailing List Cc: Subject: [osflash] mxml on client In my experience, run-time UI rendering from XML is not slow -- it can be greatly optimized. I did some years ago a (closed source) AS1 MXML-like renderer with CSS support: it handles very complex layouts without problems. I'm happy to hear that there's some work on an AS2 runtime MXML renderer! I will consider joining this project :) However ASML can become a very good alternative and I was wondering if it could be used not only for ActionStep. Scott? _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
<<winmail.dat>>
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
