: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means waiting times in the issue tracker are very long and mostly depend on community. Sorry for the inconvenience.
State: new new: Initial state. As long as issue is in this state, the work on the issue has not yet begun. opened: Opened state means developer started working on the issue. Feature/Fix will probably be in the next release. postponed: This means developer is not working on it now, for some reason it cannot be implemented now. Issue may be opened again in the future. upgraded: Issue is in upgraded state when developer made changes to the program and new version was released. closed: This means the user is satisfied with issue results and no more changes are needed. invalid: These issues cannot be solved. ignored: Developer decided to take no action on this issue. returned: Program changes were made but user is not satisfied and returned the issue.
My little suggestion is source output changes. Currently our decompiler working with RAW
output, i.e. just put "all*.as" files into directory or output as FLA files. Hmm how about
feature, similar to ILSpy, NetReflectors - output sources with creation project files?
Just for example, we have a FLEX4 flash application. Why not create project for
FlashDevelop or InteliJ IDEA?
On my vision that will be great feature for JPEXS and much more easy, instead of manual
assembly decompiled sources into project on FD or Idea. FLA export is great feature, but
on some cases, we need working with FlashDevelop.
That is just my suggestion, but i will be really happy if that is "make a point of
interest" for developers and be implemented in future.
Here the little "artwork" for it attached.
Thanks for the idea.
It is possible to implement. We don't know how these projects should look like. I don't
know FlashDevelop and never thought InteliJ knows ActionScript. We must study structure of
these project formats and then implement the conversion. I guess both of these are based
on XML so it could be not so hard.
I can't give you any exact dates when we will implement it since our issue tracker is
already pretty full.
Thanks for reading.
Yeah, them both based on XML and not hard to implement at all due to simple project files
Yeah, fix current problems is a right way instead implement a new features when we have a
some issues with current things. Those feature - is a great thing for future releases and
long-range TODO thing.
Also if you got any troubles with FlashDevelop or InteliJ projects i'll be happy to help
with that (+tests, explain - "how to" and etc.). Just hire me on that issue (i'm
subscribed and check e-mails daily) ;)