Hi all,

I just had the pleasure of stepping through the Cairngorm Store (v2.0)
and checking it out. (I2, Great Work)

I have two event questions regarding the store.

1. I notice that there are two events (UpdateShippingCostEvent and
NewScreenEvent) which do not map to a command in the Controller. What
is the motivation behind that? Meaning, is there a specific reason why
one would choose to have some events not handled by a command in a
Cairngorm app?

2. The other is separation of logic from presentation. There are two
events mapped to Commands in the controller (FilterProductsEvent and
SortProductsEvent) which are nothing more than view manipulation of
the data. By putting these in a command, aren't we coupling the
business logic to the view a little too tight?


2. (Explained) I ask number two because I have a Component in my
application that is a List with the US States in it. Users can drag
the states from the List and drop them in a grid, where I have setup
additional data entry capabilities. The state List dataProvider is a
"copy" of a model variable called STATES_US. The List is re-sorted and
filtered as states are pulled from it. (Essentially to prevent the
user from adding the same state twice)

Following the logic of the Cairngorm Store, I would need to map an
event to a command and bounce it to the model. But in this case,
that's not possible since it is a component property we are sorting.

Thanks for any insight you can offer.

Reply via email to