Re: Command pattern: Interaction allowed?
- From: "tailorma_de" <tailormade@xxxxxxx>
- Date: 20 Nov 2006 06:20:37 -0800
It is perfectly OK to have the U/I present the dialog BEFORE calling the
command. In other words, the command is called by the U/I when the U/I is
certain that it wants the command to occur, and not before.
Aha, interesting. I didn't expect this answer. But don't you encounter
cases where this gets disadvantageous? Because of too much logic within
the UI? Consider also multiple UIs.
About my other assumption: What do you think about a design where the
UI solely triggers the business model. Do you think this is realistic?
Or is it a wrong assumption? Would be nice if I could clarify this for
my self.
.
- Follow-Ups:
- Re: Command pattern: Interaction allowed?
- From: Nick Malik [Microsoft]
- Re: Command pattern: Interaction allowed?
- From: Nacho Facello
- Re: Command pattern: Interaction allowed?
- From: tailorma_de
- Re: Command pattern: Interaction allowed?
- References:
- Command pattern: Interaction allowed?
- From: tailorma_de
- Re: Command pattern: Interaction allowed?
- From: Nick Malik [Microsoft]
- Command pattern: Interaction allowed?
- Prev by Date: Re: Strong argument for Use Case
- Next by Date: Re: Howto model decoupled hierarchies?
- Previous by thread: Re: Command pattern: Interaction allowed?
- Next by thread: Re: Command pattern: Interaction allowed?
- Index(es):
Relevant Pages
|