Some week ago for a project I was looking for a flex dockbar component. I found some but, the missing and most requested feature from users (and me too) was the ability to add items to the dockbar simply adding a mxml node so that click and rollover handlers, data bindings etc. could be easily implemented:
<DockBar>
<Item click="doSomething()" rollOver="doOver" />
<Item click="doSomethingElse()" rollOver="doOver" toolTip="click me" />
</DockBar>
I could not find anything similar, so I wrote this component.
I did zillions of experiments like this in the past, but I tried to do it easy to set up, and tried to use the less code possible.
I found suprisingly easy to build it upon the HBox and Image components. Maybe not the most sofisticated implementation but so damn simple…
With some good ideas flex can be really easy to code.
See it moving (just move the mouse to the last 20px on the bottom):
Example #1 - Basic implementation
Example #2 - Basic implementation applied to a ViewStack
Example #3 - Tooltip, handcursor, rollover effects etc.
I need a component to place at the bottom of the screen so I hardcoded some params to place it but can be very easily tweaked.
Every example has view source enabled so just right click on it to view the code.
Here’s the code from example #1:
<local:DockBar id="dockbar" horizontalCenter="0" bottom="0" width="100%" height="100" minSize="32" maxSize="80">
<mx:Label visible="false" id="menuLabel" text="Menu" bottom="0" horizontalCenter="0" fontSize="24" color="#ffffff" alpha=".75" />
<mx:Canvas id="activationArea" width="100%" height="20" bottom="{-activationArea.height+20}" backgroundColor="#000000" backgroundAlpha="0" rollOver="dockbar.open()" />
<mx:HBox id="innerCanvas" bottom="{-innerCanvas.height+20}" paddingLeft="{dockbar.minSize}" horizontalCenter="0"
backgroundColor="#333333" backgroundAlpha=".4" hideEffect="WipeDown" showEffect="WipeUp">
<mx:Image click="clicked(1)" source="{icon1}" />
<mx:Image click="clicked(2)" source="{icon2}" />
<mx:Image click="clicked(3)" source="{icon3}" />
<mx:Image click="clicked(4)" source="{icon4}" />
<mx:Image click="clicked(5)" source="{icon5}" />
<mx:Image click="clicked(6)" source="{icon6}" />
<mx:Image click="clicked(7)" source="{icon7}" />
</mx:HBox>
</local:DockBar>Do not remove the menuLabel and the activationArea elements. They was coded inside the actionscript of the component but then I moved them out to the mxml to make them easier to customize.
The activation area is the area to rollOver for the component to be opened (here 20px high… maybe 30 or 40 would be more confortable). The height of the dockbar instead is 100px and is the area to rollOut to make the component close.
Other parameters such minSize and maxSize are quite self-explanatory and limits the size of the icons.
The icons are embedded clips from a swf file. The registration point of the icons must be at the bottom-center.
Ths icons sizes are calculated based on horizontal and vertical distance. Many values are still hardcoded but could be easily parametrized.
You can try changing the backgroundColor and backgroundAlpha of the dockBar and the activation area to better understand how does it work.
Just leave a comment if you like it.
Bye
Contact
Subscribe
November 3, 2008 
2 Comments 
). I am new to multi core cpu and I am really surprised to see that now the browser vs IDE situation totally changed. Now I can do 51 fps in the browser (Opera 9.23) and 30 in the IDE… mmm strange behaviour, maybe I just need some sleep.
