Skip to main content
Participant
March 24, 2008
Question

Most efficient setup for testing a custom Flex SDK?

  • March 24, 2008
  • 4 replies
  • 591 views
Hello,

I am experimenting with the Flex SDK by adding an extension to the MXML compiler. With the help of the documentation setting up Eclipse & Ant for developing and building the SDK was easy kudos! I successfully added my experimental SDK to Flex Builder and I am able to compile my projects with it.

The problem I have is, that changes to MXMLC are not immediately reflected in Flex Builder. Cleaning or closing and re-opening my Flex project is not sufficient. Only after restarting Flex Builder, I see the changes I made to the SDK.

I am wondering, what's the most efficient way to test a custom Flex SDK?

Regards,
Daniel
This topic has been closed for replies.

4 replies

Participant
March 27, 2008
Thank you, Mike. I will be following the request.

Regards,
Daniel
Participating Frequently
March 24, 2008
Great -- I've added a comment, and moved your enhancement request from Community status to New. (That doesn't mean it will necessarily be fixed; it just means it does not require some votes before it will be considered for fixing.) You can put a "watch" on the enhancement request if you want to monitor its progress.

Thanks for the feedback! - Mike
Participant
March 24, 2008
Hi Mike, thanks for the quick response and for the workaround.
I've followed your advice and issued an enhancement request.
You can find it at

https://bugs.adobe.com/jira/browse/FB-12299

Best regards,
Daniel
Participating Frequently
March 24, 2008
Hi Daniel, that's a good question. Flex Builder only loads each compiler once, which makes sense for most users, since most users aren't modifying their compiler, but unfortunately that's not the best workflow for users like you.

There is a trick you can do, but it isn't really much better than exiting and relaunching the IDE -- in fact, it may be worse. If you go to the Flex Builder preferences, and change the path of the SDK to point to some other SDK, that forces Flex Builder to reload the compiler. So for your case, you could change it to point to a different location, and then change it back again to point at the original location.

But this has a number of drawbacks:

(1) Flex Builder won't let you point at any old directory -- the "OK" button will only be enabled if you are pointing at a valid dir. So you can't type something short like "C:\" (or "/" on the Mac) and be done with it.
(2) Once you change it, all projects that use that SDK will automatically recompile. For this hack, that's not desirable, because the new SDK is just a temporary one to force a reload of the compiler.
(3) It would be easy to lose track of whether you had accidentally changed it to point to the wrong place.

For those reasons, I think your best option for now is to shut down Flex Builder.

Could you please log an enhancement request at http://bugs.adobe.com/flex, to allow Flex Builder to either automatically or manually reload the compiler?

- Mike Morearty, Adobe Flex Builder team