This project is not designed to convert anything to Java. It is designed to make ActionScript classes available to Java so that something can be done with them (like to output documentation, or to write an ActionScript editor with code completion).
However, if you were to write a project to convert code from one language to another similar language, this tool would be invaluable in the "parse" step. The conversion and output steps would be up to you. As far as the parsing of AS3 goes, I've definitely thought about it. The entire project is coded to interfaces, so you could theoretically drop in any similar OO language. You might have to add some additional code elements to accommodate namespaces and the new access modifiers, but all in all it wouldn't be too big a job. Scott On 03/08/06, jim <[EMAIL PROTECTED]> wrote: > I don't suppose you are going to make an AS3 version? I have a project that > I am building in AS3 that will need porting to Java once completed & > something like this will help me out a lot. > > Jim > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Scott Hyndman > Sent: 03 August 2006 19:30 > To: Open Source Flash Mailing List > Subject: Re: [osflash] ASPOJO Released > > > What does this mean? Does it mean it takes text files that contain > > actionscript classes (I presume headers and not code) and converts > > them into the same in java? If it is doing full code conversion boy > > did you undersell! > > Nope, not conversion. It could certainly be used to accomplish > something like this though. > > > Presuming its just headers, why would I need to do this? I actually > > have some code that I would love to convert to java but it doesnt > > sound like this is what its for. What would be a use case. (I'm sure > > there are good ones, but knowing what your intent was will help me > > understand its usefullness). > > What ASPOJO does is takes ActionScript class files and transforms them > into POJOs representing the AS types, allowing them to be easily > handled by Java. > > So, here are some ideas for how this could be used: > > -Code documentation (since all method interfaces and comments are > available in the POJOs) > -Java-based bi-directional UML software for AS > -A pre-processing step for fairly complex transformations > > I actually built this for use with the ActionStep Interface Builder (a > work in progress). AIB is written in ActionStep, but requires a bridge > to the filesystem and an understanding of existing ActionScript > classes so you can use your own classes with ActionStep. To accomplish > this I've been writing a Java sidekick. > > This sidekick is required to extract metadata from ActionScript files > (provided in the form of JavaDoc tags). This metadata is important for > the editor to identify certain methods and fields as different (like > data-bindable or able to establish event connections). > > If you still don't understand, check it out and took a quick look at > the org.aspojo.common package. I think you'd understand what I'm > talking about. > > Scott > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
