Extending Flex Builder: sample code for design.xml
Thanks to everyone who came to David’s and my talk at MAX today, Extending Flex Builder. I promised to post the sample code for the part of the talk which discussed design.xml.
So here it is. This ZIP file contains two projects:
- MyLibrary is the main interesting part. It contains design.xml, a Flex manifest, and a sample component. See the slides (linked above) for an explanation of how all this stuff hooks together.
- MyFlexProject is just a simple Flex Project that has MyLibrary on its library path, so that you can see that when you open the Flex project’s main app in design view, the library’s Calculator component shows up in the “Mike’s stuff” folder of the Components view (as opposed to the default, the “Custom” folder), and that if you click on the calculator that is already in the document, the list of properties in the Properties view has been customized, with the “Layout:” property showing up there.
To reiterate, the sample by itself isn’t quite enough — you really need to see the slides (starting at slide #23) to understand the context. And, I will soon be writing an Adobe Developer Center article with much more detail.
[...] Flex Builder Extensibility API Reference (blog post Mike Morearty) [...]
Hello Mike. I am trying to build an eclipse plugin for flexbuilder that would simplify the process of unit testing projects using flexunit. However, the lack of documentation has been a problem with developing anything for flexbuilder. I have several questions related to extending flexbuilder that I could not find answers anywhere. The help inside flexbuilder itself is very limited. Is there any sort of documentation other than the one provided with flexbuilder itself?
Hi venkat, the documentation provided with Flex Builder (for the code model and the design model) is what there is.