There were two ways to use it:
Developing a Flex Builder plugin required a hybrid skillset: knowledge of Java (for the Eclipse extension points) and deep familiarity with the Flex compiler internals. Here are the core components: flex builder plugin
If you're looking to develop Flex applications today, it's recommended to explore current development tools and strategies, possibly transitioning to newer technologies if Flex no longer meets your project needs. There were two ways to use it: Developing
The Flex Builder plugin was a niche within a niche—an extension mechanism for an IDE that was itself a niche tool for a framework that ultimately lost the browser wars. But for a few years, it empowered developers to create incredibly productive, tailored environments for building data-rich enterprise applications. It was a frontier of metaprogramming, compiler hacking, and visual tooling integration. But for a few years, it empowered developers
Flex’s official build tools (Ant tasks, mxmlc ) worked, but integrating them into Hudson/Jenkins or TeamCity required custom steps. A Flex Builder plugin could export a project’s compiler settings into a build script, ensuring that “works on my machine” was no longer an excuse.
Once the plugin is installed, here is how you utilize it within Eclipse:
The most powerful (and dangerous) plugin type was the . The Flex compiler could run incrementally—only recompiling changed files. A build participant could intercept the compilation process, modify the generated intermediate representations, or inject generated ActionScript classes before the final bytecode generation. This enabled metaprogramming patterns that were impossible in standard ActionScript.
There were two ways to use it:
Developing a Flex Builder plugin required a hybrid skillset: knowledge of Java (for the Eclipse extension points) and deep familiarity with the Flex compiler internals. Here are the core components:
If you're looking to develop Flex applications today, it's recommended to explore current development tools and strategies, possibly transitioning to newer technologies if Flex no longer meets your project needs.
The Flex Builder plugin was a niche within a niche—an extension mechanism for an IDE that was itself a niche tool for a framework that ultimately lost the browser wars. But for a few years, it empowered developers to create incredibly productive, tailored environments for building data-rich enterprise applications. It was a frontier of metaprogramming, compiler hacking, and visual tooling integration.
Flex’s official build tools (Ant tasks, mxmlc ) worked, but integrating them into Hudson/Jenkins or TeamCity required custom steps. A Flex Builder plugin could export a project’s compiler settings into a build script, ensuring that “works on my machine” was no longer an excuse.
Once the plugin is installed, here is how you utilize it within Eclipse:
The most powerful (and dangerous) plugin type was the . The Flex compiler could run incrementally—only recompiling changed files. A build participant could intercept the compilation process, modify the generated intermediate representations, or inject generated ActionScript classes before the final bytecode generation. This enabled metaprogramming patterns that were impossible in standard ActionScript.