Hi Martin, It's awesome the work you all have accomplished : ). I would like to know if there's plans to complete the AS3 grammar and choose between AS2 and AS3, as many of us now go the new AS3 way.
If there's plan to make some AS3/Flex work in the future I'd like to join again. Nowadays I'm very busy but I 'd like to know if you have plans so I have that in mind for the future. As I said,...awesome work guys! :) C. 2007/3/11, Martin Wood-Mitrovski <[EMAIL PROTECTED]>:
> ASDT seems to be not in development anymore. Are there any attempts? I > think AS2.0 is still widely used and more than AS3.0. I am able to > code in Java, but I have no experience in Eclipse Plugin Development > so far. Is there anyone interested in further development of ASDT? There is a refactoring plugin in SVN which was developed some time ago which can do class name refactoring (although i havent personally tried it yet) also you'll be pleased to know that for the past month or so there has been development work on ASDT :) If you are interested on helping out with ASDT in any way that would be great. You dont need to know anything about eclipse plugin development as its fairly easy to pick up, there is plenty of documentation and those of us who are developing can always point you in the right direction. Just so you and others know what is happening i'll give a summary of what we have done recently and what we are doing :) The biggest task at the moment is to move from the old parser and AS model to our new parser and model. Martin Schnabel has created a completely new AS2 parser with ANTLR3 which now provides us with nice things like error recovery when parsing (i.e. things like missing semicolons dont break parsing) and also optimised parsing for just type headers (imports and declaration) and type signatures (properties and method signatures, doesnt parse method bodies) to go with the full blow parser. Also it can generate code as well as parse it so implementing refactoring and similar functionality is now possible. :) The new parser and AS model are pretty much complete, what we are doing (and would be great to have help with) is creating the type management and caching system, and then re-factoring the existing code to use the new system. Things like code completion, new class / interface wizards, open declaration action, outline view, build manager etc.. whic all rely on the old parser and model to some extent. Of course Aside from this there is a new logger which uses a console view instead of the old table style with different colours for different log levels and my personal favourite feature which is hyperlinked log statements, where you can click on a log statement and jump to the log statement in the actionscript file. The viewer now has a template and properties so you can change the background colour and pass in flashvars when testing your movie, it also auto-refreshes if the swf changes. There is a new classpath manager which is now pretty much the same as the JDT build path management UI minus the library tab. We now have a build manager so you can finally build swfs without using ANT or Flashout. You can have multiple targets per project and the targets are rebuilt automatically when the project changes, so once the swf is created you can leave it open in a viewer, then when the source changes, the swf is rebuilt and the viewer automatically reloads the swf (which is another of my favourite features) Hopefully we can put out a new release soon but it would be great to get some more active involvement so we can get there quicker. If you want to join in just let me know your sourceforge username and i'll add you to the team. Martin _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
-- ::| Carlos Rovira ::| http://www.carlosrovira.com ::| http://www.madeinflex.com
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
