Hi,
I won't go into the gory details, but despite backups and version control
systems, the source files for a very important application were trashed.
The files are not recoverable from version control.
After much work with file recovery tools, most of the original files were
restored. But many
I assume this was a Flex app with MXML files?
BTW, I don't think the de-compilers will resurrect local variable names.
I would suggest starting from both ends and working towards the middle. If you
use the -keep-generated-actionscript option in the MXMLC compiler, it should
create a folder
Hi Alex,
Yes, it was a fairly standard, though large, Flex 3.6 application. Some of
the decompilers seem able to resurrect .mxml files (but not mine, clearly);
I understand there's a problem with local variable names.
I never kept the generated actionscript files because (obviously
incorrectly)
On 2/19/2014 10:59 AM, Alex Harui wrote:
I would suggest starting from both ends and working towards the middle.
If you use the -keep-generated-actionscript option in the MXMLC
compiler, it should create a folder called generated in the output
folder. Comparing that to what the decompiler
Check the doc. There is either a keep=true flag or you can add
{code}
arg line=-keep-generated-actionscript /
{code}
From: Barry Gold barrydg...@ca.rr.commailto:barrydg...@ca.rr.com
Reply-To: flexcoders@yahoogroups.commailto:flexcoders@yahoogroups.com
It is painful but theoretically possible to reconstruct MXML from the generated
AS.
It is also possible to get MXMLC to build a SWF from the generated AS, but
there are some downstream issues: If you ever change this code and it requires
changes to generated code like CSS, the compiler will
Hi Alex,
Yes, I think you're right. Not a pretty process, but most likely the best
bet. Thanks for the suggestion.
On Wed, Feb 19, 2014 at 6:47 PM, Alex Harui aha...@adobe.com wrote:
It is painful but theoretically possible to reconstruct MXML from the
generated AS.
It is also possible
7 matches
Mail list logo
