As the current demand continues to focus on responsive design layout, and with the introduction of data on the move technologies that can be enabled on devices like Tablets and mobile phones, it has become much more important to have a language that can support both “Responsive Design” and “Cross Device” compatibility.
<div class="container-fluid .col-md-12" ng-if =””>
<label ng-repeat="opt in controller.optsObj" >
<input type="radio" ng-value="opt.value" ng-model="controller.ngModel">Example</label>
The example above shows how a DOM element can be customized to treat it as a different control. The type says ‘radio’, which treats an input element as a radio button. And then we have the ng-model as a directive, which acts on the data to display on the element.
Things that I liked the most about Flex:
- Two-way data binding and support in both MXML and Action Script Format.
- Modular approach, where independent modules can be made and integrated in a single container.
- Support for new frameworks like Parsley and RobotLegs that are based on the dependency injection design pattern.
- The code-behind style of coding technique, which is made possible by using MXML for Views and screen elements, and having code classes that add dynamic behavior to the controls.
- Good support of Flash Builder IDE which has several plugins that can be integrated for code management like SVN plugin.
Where I find Flex lacking:
- Bad Garbage Collection techniques and no direct way for garbage collection. The best example would be Flex module loader which has severe garbage collection issues; here, the events and objects are not cleared when a module is unloaded.
- It is a closed system when it comes to integrating other open source frameworks written in different languages.
- Poor CSS and HTML iframe integration support.
- The plugin needs to be installed in all OS to make Flash work on a browser.
- Asynchronous data handling does not work properly as it freezes the screen, since Flash works on a single thread.
- No responsive design frameworks available to fit the screen aspect ratio.
- Testing the screen element is another grey area where none of the testing frameworks support the functional and screen aspect together. Also, we do not have a standard integration testing framework.
- As its popularity decreases, there is a shortfall in online support and blogs for Flex. On the other hand, due to the growing demand of JS based libraries, we have a huge pool of online support.
A more detailed take on the comparison and important and useful finds will be discussed in my next blog.