InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

New asDox Release Helps ActionScript 3 Code Generation

Posted by Moxie Zhang on May 14, 2008

Sections
Development
Topics
Rich Internet Apps ,
Java
Tags
Python

Last week Michael Ramirez released asDox 1.0 Alpha 2, an ActionScript 3 parser written in Python. It is based on qDox for Java. The parser skims the source files only looking for things of interest, such as class/interface definitions, import statements, JavaDoc tags and member declarations. InfoQ spoke with Ramirez to gain additional insight.

Ramirez explained the motivation for developing an ActionScript parser in Python, recalling:

I decided to develop asDox, because I felt ActionScript 3 needed a code generation tool similar to qDox. I choose Python, because of the PyParsing module. I found PyParsing very easy to use, and it made developing an ActionScript 3 parser fun.

An end product is the goal, but it will probably be a while before I can release one. The asDox is a tool to increase your productivity as a developer via code generation. For example, you might develop a collection of ActionScript 3 classes and use asDox to automatically generate the PHP back-end code.

On the relationship between asDox and Adobe’s ASDoc , which is now part of Flex Builder, Ramirez says:

AsDoc is a tool used to generate API documentation by parsing JavaDoc tags embedded in ActionScript 3 source files. asDox is a tool that parses not only JavaDoc tags, but also packages, classes, variables and methods. It provides the developer with more information about his or her ActionScript 3 source files. When combined with a template engine, it can be a very powerful tool in code generation.

Ramirez went on to explain how much he adapted from qDox and the improvement he made in asDox implementation, pointing out, “The Alpha 1 release of asDox had an API that very closely matched that of qDox. This made asDox harder to use for Python developers. After the publication of Python Is Not Java, the last release has been completely reworked to be more Python friendly.”

The development of asDox was not painless. As Ramirez notes, “The biggest challenge in developing asDox was writing the ActionScript 3 parser. ActionScript 3 is a very difficult language to parse, because it's not very forgiving in terms of syntax.

Nevertheless, Ramirez plans to forge ahead with his work. He says, “I plan to develop an Adobe Air desktop application for asDox. But, right now my primary focus is on getting asDox to a 1.0.0 release. I am really counting on feedback from the community to make this tool better.”

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.