flex component compiler parameters

today i need to build a flex swc, so create a new flex lib project and put

compc -source-path . -output bin/MySwc.swc -namespace http://www.mynamespace.com myManifest.xml -include-namespaces http://mynamespace.com

if compile form flex builder, use -namespace http://www.mynamespace.com myManifest.xml -include-namespaces http://mynamespace.com

the myManifest.xml will looks similiar as ( from adobe help sample)

<?xml version="1.0"?>

<!-- SimpleManifest.xml -->
<componentPackage>
    <component id="MyButton" class="MyButton"/>

    <component id="MyOtherButton" class="MyOtherButton"/>
</componentPackage>

then in another felx project you want to use the lib

<?xml version="1.0"?>

<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" xmlns:myns="http://mynamespace.com">
    <myns:MyButton/>

    <myns:MyOtherButton/>
</mx:Application>

Team Project Set

source:
http://nwebb.co.uk/blog/?p=80

== quote ==
Someone I work with has just pointed out the very handy "Team Project Set" option in FlexBuilder (i.e. Eclipse).

We have several Flex Library Projects which work in tandem with our main Flex project. All of these projects are required in order for our main app to compile. All projects are (of course) checked in to SubVersion :]
Now let's say someone new joins the company, or my colleague (who is currently miles away in Berlin) wants to mimic what I have in my FlexBuilder workspace. The easiest option is to create a project set for him.

I can right-click in the Navigator pane of FlexBuilder and select Export -> Team Project Set, then select of all the projects in my workspace which I want to be included in this set and generate a "project set file" (this has a .psf extension).

Now I can send the .psf to whoever wants it. Whoever receives the file (preferably) sets up a brand new workspace first, and then imports the .psf by right-clicking in the Nav pane of Flexbuilder and choosing Import -> Team Project Set

The correct versions of the relevant projects are all checked out of svn/imported in to FlexBuilder for them. Nice.

right click css and compile to swf in FB

source :http://nwebb.co.uk/blog/?p=81

This evening I thought I'd take a look at some of the code behind the fantastic Adobe Flex Store sample application.

If you try to compile the app you may initially get an error because two files are missing (beige.swf and blue.swf) . Never fear, in the readme file it tells you that you can generate the swfs by right-clicking on the corresponding css files and choosing "compile css to swf". I never knew you could do that!

Flex Builder editor cheat sheet

http://davidzuckerman.com/adobe/2006/10/27/flex-builder-editor-cheat-sheet/
To dismiss the surrounding containers:
Press the F4 key again.

So first off, thank you everyone who came to see my talk at MAX, and thanks to everyone for all the great feedback about Flex Builder! One of the comments I heard the most though, was “Wow, I didn’t know you could do that in FlexBuilder?!?!?” so here’s a cheat sheet of cool editor features (in no real order).

1.) Open type (Ctrl-Shift-T)* - this lets you browse all the types (AS classes/interfaces, MXML files) in your project and quickly open them.

2.) Goto Definition (F3/Ctrl-click on identifier)* - quickly jump to the definition of an identifier (type/variable/function).

3.) Quick Outliner (Ctrl-O)* - get the outline view as a pop-up window, with the added ability to type and filter down to the function/member variable that you’re looking for.

4.) Context sensitive help (F1 on an identifier/tag) - for an MXML tag, function or class/interface, show the help entry for that item in the Eclipse Help Panel.

5.) Open context sensitive help (Shift-F2 on an identifier) - for an MXML tag, function or class/interface, show the help entry for that item in the integrated Help browser. This will most likely open a new browser window.

6.) Jump to matching brace (Ctrl-Shift+P)* - jumps to the matching brace if your cursor is to the left or right of a given balanced brace.

7.) Hover over an identifier - when you put your mouse over a variable, we display its type. When you hover over a function, we display its return type (if it has one).

8.) Add CDATA block (Ctrl-Shift-C) in MXML - wraps a given selection in a CDATA block

9.) Event type hinting (Ctrl-space) - addEventListener( will display all the events that are relevant targets for a listener function.

10.) Fold all functions/ASDoc comments/comments in ActionScript - With folding enabled, right-click on the vertical gutter, drill down to “Folding”

11.) Organize imports (Ctrl + Shift + O)* - Sorts the imports in ActionScript files, removes duplicates and consolidates when needed

Okay, that’s a small list. Enjoy!

Oh yeah, I’ll post some slides and code examples from my presentation in the next couple days
* - same functionality as the JDT