Developing Flex components

  • user warning: Table 'variable' is marked as crashed and should be repaired query: UPDATE variable SET value = 's:1:\"1\";' WHERE name = 'image_gallery_nav_vocabulary' in /var/www/vinetoolkit.org/includes/bootstrap.inc on line 609.
  • user warning: Table 'variable' is marked as crashed and should be repaired query: UPDATE variable SET value = 'a:1:{i:0;s:13:\"primary-links\";}' WHERE name = 'menu_expanded' in /var/www/vinetoolkit.org/includes/bootstrap.inc on line 609.

All components in Vine are based on Adobe Flex technology. In the past we evaluated other solutions starting from pure jsp pages, tapestry and jsf frameworks, looking at some new and nifty looking ones ( Echo 2 ) and ending up with our own UI framework - Sportlets. What we learned is that with the old fashion HTML and Java Script approach it's very hard to manage crossbrowser compatibility issues and it's almost impossible to create and maintain a product which could be deployed into other heavily featured (ui-wise) environments ( eg. Liferay ).

Currently Flex 4 is used as primary UI platform for the Vine Toolkit. It has been adopted along with the open source data services - BlazeDs. In this section we will describe several scenarios of creating Flex components with the custom add ons provided by the Vine Toolkit.