Omar,
 
Without a detailed understanding of your application, it's really hard to offer any particular advice at this stage.  I'd recommend if using Cairngorm that you're careful to maintain state in the ModelLocator, and decouple your views from the model through data-binding to the ModelLocator.  I'd recommend you consider the ViewHelper if and only if you are rendering your model with some manipulation. But for drawing shapes/etc ... that sounds more of a task for a class hierarchy of your own, using more classic OO implementations of Shapes, Polygons, Circle classes, etc, that are able to draw themselves and be manipulated by a ShapeManager type of class.  I'd expect all of that kind of functionality to sit in your own client-side architecture that provides structure to the implementation of your view.   Cairngorm offers no real help as to how you implement your view, and instead focuses on the task of helping you integrate your view with client-side business logic and server-side data services.
 
My previous advice still stands; build your app without Cairngorm until you feel you are losing by not having it there.
 
Cairngorm isn't a magic bullet, it doesn't guarantee project success, and it's not essential for Flex development.  It's simply a formalisation and generalisation of how some of us will implement n-tier Flex applications over and over again, and capitulates some of the lower-level design decisons to prior experience.  The challenges you're describing sound like challenges in one tier - the presentation tier - not in how you bind all those tiers together.   You're looking for guidance on the former, Cairngorm gives structure to the latter.
 
Best of luck,
 
Steven
 
--
Steven Webster
Technical Director
iteration::two
[EMAIL PROTECTED]
 
Office:  +44 (0)131 338 6108
Mobile: +44 (0)7977 216 223
 
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.
 


From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Omar Ramos
Sent: 23 August 2005 02:20
To: [email protected]
Subject: Re: [flexcoders] Cairgorm question.

Thanks for your responses. I can not give much details about the application as is confidential. But the application is also constantly comunicating with the database and .NET, so I have implemented Cairgorm for that part and it works nicely. But developing my canvas component I got to wonder what was the best way to have my other views invoke methods on the canvas to *Draw, Put a Image or Text* in it without having to directly reference it and avoid code like ( mx.core.application.canvas.pad.DrawRectangle() ). It is a complex application that uses drawing tools, database and xml ( DOM ) services. So the state of those shapes, images, ect will be stored on the server. Now you see where I thinkCairgorm fits in. I would put it all together and make it work, but the project needs to be scalable and maintainable and thus structured. Any ideas on how to best implement this type of project? Thanks for the replys and making me better understan Cairgorm.
 
 
Omar Ramos
System Developer
 


--
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