Runtime-Shared-Libraries are a nice little thing when it comes to load data within application at runtime. The benefit is mostly the increasing filesize. But another nice feature of using compiled swf's as a library instead of loading raw assets is the compression of the swf-format.
The Canvas arranges its child components to their desired size regarding to their minimum and maximum size. It is possible to add an CanvasConstraint while adding a component to a Canvas. This constraint is an encapsulation of values used in an absolute layout (top, left, right, bottom) like in CSS.
There are several possibilities to create swc libraries or assets. You can use embed tags wihing as-classes to force the compiler to include assets directly into your physical swf or you can use the flash IDE to link your assets in the library and publish them afterwards or at least use the flex oem compiler to compile your assets from the console.
There is a catch with all of these possibilities (in my opinion). The flash IDE is not open source, I always forget the syntax of the embed tags and using the console is failure prone.
An Vbox arranges its child components vertically according to their desired size. If the size is is declared in percentage values, it will set the components bounds percentaged to the space left filled by fixed size components.
NOTE: percentaged values of child components are just handled if the desired size of the HBox was set explicitly.
An Hbox arranges its child components horizontally according to their desired size. If the size is is declared in percentage values, it will set the components bounds percentaged to the space left filled by fixed size components.
NOTE: percentaged values of child components are just handled if the desired size of the HBox was set explicitly.
After talking with some users about the usability of the AS3-Layout-Framework, I realized that the dynamic layout approach (layout strategies totally independent from containers) seemed to be a bit confusing or too complicated.
To prevent this issue, I choose the approach of concrete containers like in C#. Now, every container has its own layout strategy implemented. F.e. an HBox can layout its child components horizontal and a FlowBox can also align them in a specific way.
With regard to a gui-system on top, this approach has its advantages (first of all simplicity).
During the next days, I will adapt the old class diagrams and update the repository.
The source code is available here
For those readers who are not familiar with the architecture of the AS3-Layout-Framework, here is a short introduction.
Which base class should you use?
The answer is very simple. If the needed component has no subcomponents, use Component. If other components should be added and also be laid out, use Container instead.
A FlowBox arranges IUIComponents in a row/column until no more IUIComponents fit in that row/column. The IUIComponents will be arranged to their desired size.
In addition the FlowBox offers the possibility to choose different alignment and flow settings which are also modifiable at runtime.
The new AS3-Layout-Framework is now available in the addicted2flash library.
The architecture is straight forward and easy to understand (hopefully). It is basically constructed on top of two abstract interfaces named IComponent and IContainer. The main difference between them is the possiblity to add components.
Very often it is necessary to use an obervable-pattern in its basic structure, which means that the observable notifies registered observers after its internal state has changed.
This implementation concept is very static and has the side effect that the observers are notified every time the model has changed regardless of which change they are interested in.
In this case it is recommended to use a more dynamic approach like an specific observable.
But if you only have one value in the model which changes, the MicroObservable structure could be very useful.
