Imay be a little late here, but no, its not only for calling backend. Anytime you want encapsulate some UI logic, put it in a command. Even if it just to manipulate data, update the view or to call the server-side. Dimitrios Gianninas Developer Optimal Payments Inc.
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of bnsmeets Sent: Wednesday, April 25, 2007 5:57 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Cairngorm, is this suitable as Cairngorm "event" Hi all, Wondering if the Cairngorm events are supposed to be only events that need backend comunication. Situation now is that I have a Model, which contains e.g. "SelectedObject". I use this var to store the selected object by users in the interface. No problems so far. But now I want to be able to let the user "clear" that selectedobject. I am tempted to just use AppModel.SelectedObject=null in a view. But the thought is running in my head that it might be neater to create a "SelectedObjectClearedEvent" and attach a command to that which contains the logic if it is possible to clear it. Question in the bigger picture is this: Are cairngorm events "as is" supposed to be used only when there is a "I want to call backend"- event? Or are View related events (or any other events in that matter) supposed to be Cairngorm events too? And on top of that, how do you (Cairngorm users out there) give your other events a place in your structure? For example, my model also dispatches a custom event which has nothing to do with the backend. I use it to listen to any changes in a Collection (Default ArrayCollection events didn't do the trick). Tx in advance, Ben -- WARNING ------- This electronic message and its attachments may contain confidential, proprietary or legally privileged information, which is solely for the use of the intended recipient. No privilege or other rights are waived by any unintended transmission or unauthorized retransmission of this message. If you are not the intended recipient of this message, or if you have received it in error, you should immediately stop reading this message and delete it and all attachments from your system. The reading, distribution, copying or other use of this message or its attachments by unintended recipients is unauthorized and may be unlawful. If you have received this e-mail in error, please notify the sender. AVIS IMPORTANT -------------- Ce message électronique et ses pièces jointes peuvent contenir des renseignements confidentiels, exclusifs ou légalement privilégiés destinés au seul usage du destinataire visé. L'expéditeur original ne renonce à aucun privilège ou à aucun autre droit si le présent message a été transmis involontairement ou s'il est retransmis sans son autorisation. Si vous n'êtes pas le destinataire visé du présent message ou si vous l'avez reçu par erreur, veuillez cesser immédiatement de le lire et le supprimer, ainsi que toutes ses pièces jointes, de votre système. La lecture, la distribution, la copie ou tout autre usage du présent message ou de ses pièces jointes par des personnes autres que le destinataire visé ne sont pas autorisés et pourraient être illégaux. Si vous avez reçu ce courrier électronique par erreur, veuillez en aviser l'expéditeur.
