Title: Cairgorm features
Hey Michel,

- Error Handling 
 

What would you require exactly; remember we're not "in JVM" so the responsibility to throw errors is different.  What would you be looking for...?

 - Internacionalization  

We intended implementing the solution by Benoit Hedard into the Cairngorm framework, but haven't made any concrete commitments to delivering that.  We're trying to balance decisions about whether features belong in an architectural framework, or whether we should lobby for their inclusion in the technology itself.

 
- Action Mapping (regarding navigation)

 Again, what would you be looking for here ?  Currently, actions are essentially "event names" that invoke commands, and the map as such is the implementation of the FrontController.  We've found that to be a lightweight implementation that delivers on what people require ... would you require more.

Struts is built upon the Core J2EE Patterns, Cairngorm is an implementation of an RIA microarchitecture that leverages the Core J2EE Patterns that the iteration::two team considered over the years to be appropriate to RIA development, and have since won support from the other members of the Cairngorm project committee (and the developers using the framework).

Our goal is to deliver an implementation of a best-practice microarchitecture that best-leverage the feature-set of Flex; our goal has never been to port Struts (which I would consider to be too heavyweight for stateful client-side microarchitecture, but that's another discussion).

Have you built an RIA with Cairngorm, and did you find anything lacking in being able to engineer and deliver the kind of user-experiences that you hoped for ?  Feature requests based upon real-world use-cases are greatfully accepted...

Best wishes,

Steven

 

--
Steven Webster
Technical Director
iteration::two
 
 
This e-mail and any associated attachments transmitted with it may contain confidential information and must not be copied, or disclosed, or used by anyone other than the intended recipient(s). If you are not the intended recipient(s) please destroy this e-mail, and any copies of it, immediately.
 
Please also note that while software systems have been used to try to ensure that this e-mail has been swept for viruses, iteration::two do not accept responsibility for any damage or loss caused in respect of any viruses transmitted by the e-mail. Please ensure your own checks are carried out before any attachments are opened.


--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




YAHOO! GROUPS LINKS




Reply via email to