Search posterous

Search all posts and users. Type a name, type a favorite song title, whatever! See what comes up.
  

More posterous blogs











More recommended blogs »

Here are posterous posts filed under flex...

nikan says...

[freelance] Flex / actionscript developer at 7 Layers

Posted:

Location: Αθήνα
URL: http://www.7layers.gr

Description:

Επιθυμούμε τη συνεργασία με προγραμματιστές flex / actionscript.

Ο τρόπος συνεργασίας είναι ευέλικτος (freelance, part time, full time). Αναζητούμε αποτέλεσμα και όχι τύπους.

Apply to this job

Filed under: flex

nikan says...

[full-time] Linux System Administrator at HyperHosting

Posted:

Location: Αλιμος
URL: http://www.hyperhosting.gr

Description:

Η HyperHosting αναζητά System Administrator για την συντήρηση και διαχείριση του server farm της. Ο υποψήφιος θα φροντίζει για τη σωστή λειτουργία και έλεγχο ασφαλείας των hosting server, για την εγκατάσταση και υποστήριξη νέων dedicated server πελατών καθώς και για την αποκατάσταση τυχόν προβλημάτων αστάθειας που ενδέχεται να παρουσιαστούν.

Apply to this job

[freelance] Flex / actionscript developer at 7 Layers

Posted:

Location: Αθήνα
URL: http://www.7layers.gr

Description:

Επιθυμούμε τη συνεργασία με προγραμματιστές flex / actionscript.

Ο τρόπος συνεργασίας είναι ευέλικτος (freelance, part time, full time). Αναζητούμε αποτέλεσμα και όχι τύπους.

Apply to this job

Filed under: flex

dozza says...

This tutorial is inspired by the book Flex 3 Cookbook  

A quick tip to ensure components render in your Flex application, only when needed for display. You work with the creationPolicy property of the Container class. 

By default, Flex creates components only when they are displayed in the mxml, which infers the creationPolicy is set to auto.  You can either leave it at default, or use:
  • none - no components created.
  • all - all components will be created, and queued, based on their creationIndex

To illustrate this, the chapter shows a ComboBox sample snippet: 

...
<mx:Script> 
[![CDATA[

   private function changeViewStackCreation(): void {
    viewStack.creationPolicy = all;
viewStack.createComponentsFromDescriptors(true);
  }
..

You can find more by buying this book for only £24.54

Filed under: Flex

Ame says...

Designed and developed user interface and visualization for statistics on RNA structure patterns. July 2009 - present.

         
Click here to download:
RNA_Structural_Statistics_Brow.zip (774 KB)

Filed under: flex

riduidel says...

Pour mon nouveau boulot, je suis amené à faire du Flex. Je ne le prends pas trop mal, dans la mesure où ça me permet (en théorie) d'implémenter un point essentiel des méthodes pour rester un développeur "on the edge".
Là où c'est moins bien, c'est que tant qu'à faire, j'aurais préféré travailler sur un langage qui ne fasse pas semblant.
Prenez l'IDE, par exemple. La toute dernière version de Flash Builder est en fait un packaging d'Eclipse dédié aux développeurs Flash (comme peut l'être, je ne sais pas moi, Eclipse for C, Pulsar, ...). En un sens, c'est très bien, parce qu'en tant que développeur Java, je ne suis pas vraiment surpris. Sauf quand ils décident de me livrer sans mon consentement une version française. Ou que le seul refactoring disponible soit le renommage de fichiers (alors que faire des refactorings dans un langage dynamique, même si c'est plus difficile, c'est possible). Ou que les erreurs de compilation me font revenir quinze ans en arrière, avec des codes aabscons suivis de messages encore moins clairs (pour l'anecdote, il m'a fallu hier à peu près l'après-midi pour trouver qu'un test ne fonctionnait pas à cause d'un simple problème de déclaration de constructeur). Ou qu'une application mxml contenant les tests doive se trouver dans le dossier src (ce qui est super pratique pour séparer les tests et le code source de ma bibliothèque, tiens, imaginez comme maven est content).
Et si l'IDE infâme ne vous suffit pas, prenez les bibliothèques de test unitaire. En Java, je connais bien jUnit, et un peu TestNG. Elles sont plutôt documentées et facilement intégrées dans l'IDE. Bon, en Flex, il y a quoi ? flexunit ? funit ? asUnit ? bon, eh bien je vous mets au défi de trouver une doc claire et complète pour ces différentes bibliothèques; Attention, je ne parle pas d'un tutorial écrit pour faire comme tout le monde et présentant un exemple bidon même pas intégré à l'IDE, mais bien de l'exemple complet qui me permet à la fin de lancer mes tests dans l'IDE. Cherchez pas, vous ne trouverez rien. Parce que ces trucs sont codés à la va-vite et que leurs auteurs ne semblent pas se soucier de l'industrialsiation de ces tests unitaires.
Et pour finir avec l'industrialisation, parlons un peu des flexmojos. C'est une super-idée de vouloir intégrer la compilation Flex à maven pour montrer comme l'outil est extensible. Mais c'est aussi une terriblement moins bonne idée que de fournir une dépendance flexmojos-unittest-support qui contienne les trois bibliothèques sus-mentionnées (dont les classes de bases de test unitaire s'appellent toutes ... TestCase ... merci pour les problèmes d'import) sans jamais expliquer comment éviter cette dépendance (mis à part, quand on connait maven, en allanrt faire un tour dans le pom de cette dépendance pour trouver les dépendances initiales et leurs versions respectives).
Bref, Flex, c'est quand même vachement moins bien que Java. Et c'est là que je comprend les éternels regrets des vrais développeurs Java, qui voient Sun lancer des idées du bout du petit doigt et ne pas les soutenir (au hasard, JavaFX) alors qu'avec un bon soutien, cette techno a les moyens de botter cent fois les fesses à ce Flex, qui n'est rien d'autre qu'un javascript vaguement rabhillé.

Filed under: flex

Matt says...

Adobe Flex 4 Training for ColdFusion Developers

A free full-day, hands-on training session, where attendees can learn how to build their first Flex application using the latest Flash Builder 4 beta software. This training is designed to help experienced ColdFusion developers get started in understanding how to add rich UI to existing and new ColdFusion applications.

Great opportunity for FREE Flex training at Fig Leaf in DC! Seating is limited so if you're interested, register right away.

Filed under: Flex

dozza says...

Cairngorm 3 was announced as being available last month, with an increase in functionality scope, and some nice draft documents to keep us busy for a while. Adobe Technical Services decided to split the implementation into three specific parts : 
  • Guidelines explaining the motivation
  • Tools to adhere to this guideline framework.
  • Libraries to extend existing architectural framework and solve existing problems.

I am going to discuss the latter in brief, the Libraries to extend existing architectural framework. 

#1 Observer Library
The Cairngorm Observer library provides a set of non-visual components for declaration in MXML that observe other objects, react to changes in some way and execute view behavior. These components can help to reduce the amount of Script-block logic required in MXML components.

We find ourselves when working with Cairngorm, having to find ways to observe and react ot changes in a model object. I have been using mx.binding.utils.ChangeWatcher but with this new library,but for a simple MXML way of binding, we normally do something like:

<mx:TextInput text="{ model.firstName }"/>

 

Sometimes though, such a property might not exist and a developer needs to call a method defined on a view component, so enter Observe

<cg:Observe      source="{ model.firstName }"      handler="runEffectFunction"/>
..
<cg:ObserveValue      source="{ model.firstName }" value="{ Name.SARA }"       handler="runEffectFunction"/>

The second, ObserveValue tag only calls the method handler if the value of the property equals the source, so if the name equals SARA, the observer will be triggered.

Observer and ObserveValue can only listen to bindable properties of models. The EventListener tag adds the ability to listen to events that a model dispatches as the following examples shows:

<observer:EventListener      source="{ model }"     type="{ Person.UPDATE_EVENT }"     handler="runEffectFunction"/>

#2 Popup Library
The Cairngorm Popup library is a small Flex library for opening and closing popups. Instead of using the PopUpManager directly and writing script-block logic to manage their creation and removal, a pair of simple MXML tags are available for declaring within view components. Here's the "Hello World" of declarative popups:

This simple library is simple in that its in charge of opening and closing popup windows, based on whether the open property is set to true or not, or if you decide to work with the dispatched EVENT.CLOSE event to be handled elsewhere.

<popup:PopUpWrapper open="{model.openPopUp}">    <mx:Label text="Hello World"/> </popup:PopUpWrapper>
...

<popup:PopUpWrapper     
 open="{model.openPopUp}"     
 center="true"     
 modal="false"     
 childList="{PopUpManagerChildList.POPUP}"     
 opening="openingHandler()"     
 opened="openedHandler()"     
 closing="closingHandler()"     
 closed="closedHandler()">     
 <mx:Label text="Hello World!"/> 
<popup:PopUpWrapper>

Therefore, this clean and easy approach aims to remove duplicity of code whilst controlling the appearance of the window through bindings.

#3 Task Library
Events are fundamental to Flex. Every component in the SDK dispatches an assortment of them, while application developers regularly create their own to represent user gestures and other significant occurrences. With so many events being dispatched and handled, coordination can become challenging. A class may assume too many responsibilities, such as initiating an asynchronous service call, handling the result, then triggering a subsequent service call and handling that result also. 

A general task-processing library has been introduced to ensure the asynchronous sequencing of tasks are performed orderly, whether concurrently or queued according to dependencies, with indicative events to portray the progress to higher-level components.

#4 Validation Library
The Cairngorm Validation library is designed to simplify validation of user input and other data. Instead of declaring validators individually in MXML and coordinating them manually, a group of validators can be defined using the ValidatorGroup component. The validity of the whole group can then be determined as one. Validator groups can be detached from the view and applied to other layers of an application, such as a domain model. Additional components are provided for observing validation rules and updating view components to highlight validation errors.

<validators:ValidatorGroup id="validatorGroup">
        <validators:validators>

            <mx:StringValidator id="firstnameValidator"
                source="{ firstnameInput }"
                required="true"
                minLength="3"
                property="text"
                triggerEvent="change"/>

            <mx:StringValidator id="lastnameValidator"
                source="{ lastnameInput }"
                enabled="{ lastnameValidatorEnableFlag }"
                required="true"
                minLength="2"
                property="text"
                triggerEvent="change"/>

        </validators:validators>

For more information on each of the libraries, whether you are after more comprehensive technical descriptions, or usage examples, you can visit the official web location.

Filed under: Flex

Filed under: Flex

Matt says...

Presenter: Scott Davis

  • Flex plugin for Grails isn't a simple plugin like the YUI plugin
    • technologies are too different from one another to fully integrate
  • What's Flex?
    • free open source framework, but Flex Builder costs
    • lots of technologies floating around
      • some free of cost, some free and open source, some for pay
  • we are living in the era of the RIA
    • poorly defined
    • involves flex, air, silverlight, openlaszlo, ajax, java fx
      • java fx is applets redux--that's how they're deployed
        • some nice new stuff, but still 1995 technology with a new marketing plan
    • adobe has crushing lead in the ria space
    • lots of politics come into play--e.g. no flash player on iphone
      • apple converts all youtube content to quicktime to avoid having to use the flash player
  • have macromedia to thank for the ria term
    • idea was can't use same technology already in browser for rich experience
    • solution is plugins into the browser
  • plugins aren't new
    • applets introduced in 1995
    • lasting achievement of java applets is the warning asking whether or not you trust the applet
  • fast-forward to 2005
    • jesse james garret coins "AJAX" term
      • blog post discusses how web developers are envious of desktop developers
      • pointed to google suggest and google maps as examples
      • major thing is eliminating the page loads
      • amazing thing about google maps is they did it without a plugin
  • great divide (?)
    • can either have js + css + html, or can use a plugin
    • walls are starting to crumble however--hybrid development
    • apple desktop widgets
      • native part of OS but live in a different space
      • create in html, css, and js
      • use the webkit framework for rendering
      • gadgets in windows are similar
    • palm pre
      • webos
      • build apps with basic web languages
    • google chrome OS
      • OS based on chrome web browser
      • isn't a scrim on top of OS like widgets and gadgets
    • notion of pulling up a web browser to run webapps will soon be seen as rather quaint
    • Adobe AIR is one attempt to eliminate the browser from the equation
    • idea of ubiquitous web also well represented by iTunes
      • webkit browser baked in
    • future of software development -- of course it's web enabled
      • the idea of web/not web will fade into the woodwork
  • twitter example of how ecosystem can develop around an API and core data
    • twitter doesn't have to own the hardware and software

Nuts and Bolts of Flex

  • grails plugins assume you're conversant with the acronyms and technologies involved with Flex
  • flash player is where flex apps run
  • flash player revs about every year, and the new players get adopted very quickly--huge adoption rate
    • 80%+ of users are on the most recent version
    • many, many more people run old versions of java as compared to flash
  • flash player on most mobile platforms but not on iphone
  • adobe recently released tools to allow for compilation of flex apps into native iphone apps
  • flash offers similar "write once run anywhere" experience
    • java: class files run in JVM, JVM native to OS
    • flash: swf files run in Flash Player, Flash Player native to OS
    • javascript model is a bit different--still breaking differences between the browsers
      • javascript libraries get around the browser incompatibilities
      • javascript engines in the browser aren't pluggable/upgradable
  • ECMAScript -- standard with 3 major dialects: javascript, actionscript, jscript
  • js engines
    • firefox: spidermonkey
    • chrome: v8 engine
    • IE: JScript 5.8
    • flash/flex: actionscript engine
  • adobe collaborating with mozilla
    • donated actionscript virtual machine (AVM2) to the mozilla foundation
    • tamarin will be used for javascript 2
    • same javascript engine as used in flash player
    • javascript is traditionally interpreted
    • V8 and Tamarin do a lot of just-in-time compiling
    • probably be years before this is a standard
  • swf is a partially open file format
    • specs are published, but adobe retains ownership
    • everyone can read/write swf files, but spec isn't open for change
  • openlaszlo
    • because swf format is open, openlaszlo is written in lzx but generates a swf
  • flex is an sdk
    • big switch from the animation history of flash--flex is a 'business toolkit'
    • flash player is free but not open source
    • adobe dabbling with open source--tamarin, open source sdk
    • flex builder isn't even free as in beer
      • eclipse plugin
      • also plugin for intellij
  • here's what we know so far
    • jvm (jre) == flash player
    • class (JAR) == swf
    • jdk == flex sdk

Deeper Dive Into Flex

  • two key technologies: mxml and actionscript
  • mxml--tag-based like html
    • declarative, nested hierarchy of widgets
    • mxml is the html/css analog in this environment
  • actionscript
    • ecmascript dialect
      • if you know JS do you know AS? yes and no
    • first official version of AS was in Flash Player 5
    • huge maturation with AS 2, even more with AS 3
      • AS has been sliding more and more towards Java in terms of strong typing, inheritance, packages, etc.

Flex Development

  • need flex sdk
  • similar manual install process as with groovy and grails
    • set up flex home directory as an environment variable, add flex bin to path
    • mxmlc compiles mxml/AS code into swf
  • can buy Flash Builder, but isn't required for development
    • development experience isn't nearly as good without Flash Builder
  • IntelliJ has Flex capabilities as well (only in pro version)
  • Google provides SWCs to incorporate google maps into flex appss

Grails Plugins

  • four plugins
  • GraniteDS Flex Plugin--seems to be most mature and well documented
    • includes GraniteDS for data services
    • originally required JPA, not GORM
    • GORM support now in the plugin (experimental)
    • install the plugin, annotate the services and controllers
    • can then generate AS3 domain classes as well as the flex app itself

Filed under: Flex

Matt says...

Contact Suzanne McIntosh (suzanne.mcintosh@ncwresources.com) for more details.

----------
Responsibilities: The candidate will be part of a TEAM that is responsible for development, delivery and maintenance of applications and websites based on ColdFusion and Oracle database back-end. He/she will participate in software and hardware migrations and may administer Web Server and Web Application Service software. The successful candidate will work closely with various clients to fine tune requirements in developing ColdFusion web applications. The individual must have an excellent knowledge with hands-on experience performing analysis and design, as well as implementation and follow-up maintenance of website applications. He/she needs to be aware of Government 508 Compliancy requirements and have an experience with ColdFusion coding and tags. He/she must demonstrate effectiveness as a team player and possess strong attention to details. The candidate will be required to work closely with clients and staff to solve technical problems and ensure the technical feasibility of all business requirements.

Qualifications: Working knowledge of Microsoft Windows platform and IIS Web Server, ColdFusion MX, HTML, Java Script, VB Scripts and experience with Internet services including HTTP, HTTPS, FTP, SFTP and SMTP. Other required skills include experience with PL/SQL, Oracle 8i - 10g and Microsoft SQL server environments. Demonstrated ability to work independently and as a team-member with all levels of the staff. Must be a quick learner and have excellent interpersonal skills. Proficient experience in all phases of Software Development Life Cycle is required Strong oral and written communication skills. Education/Experience: BA or BS degree in Computer Science or a related field with a minimum of 3 years ColdFusion and SQL experience.

Must have Adobe Flex.

Filed under: Flex