Re: Auto selection
- From: "tailorma_de" <tailormade@xxxxxxx>
- Date: 24 Nov 2006 00:55:34 -0800
The single advantage of pop-up against tree + currently-in-focus pane is
that pop-up has a clean and intuitive commitment/confirmation procedure:
either you click OK or Cancel.
Or am I wrong?
You have to decide what drives what. Typically GUI is used to control
things, so it is logical to deploy a schema where the GUI enforces its view
on the model. An alternative would be a GUI reflecting sporadically
happening changes in the model. The second view is doable, but more
difficult and usually less intuitive to the user, because it gets
increasingly difficult to separate the changes I, the user, do vs. ones
asynchronously imposed on me. As you noticed, you will have problems with
things like focus etc, because they don't belong to the model. (Not to
mention notification services necessary) So you probably will need a third
player to tell GUI what's going on, some sort of context, session,
environment etc. I think you've got the idea - selection will not belong to
GUI anymore.
Yeah, I think I've got it. But sometimes, I think, you cannot avoid
another dialog. But that is quite clear. E.g. when creating a project
item where you have to choose what kind of project and initialize it
somehow. This would be less intuitiv if one tries to avoid a dialog.
I have to think about it. Maybe I will realize this. Though, I'm
curious if someone will oppose to your suggestion. Or acknowledge.
Thank you and Ed so far.
Cheers,
Robert
.
- Follow-Ups:
- Re: Auto selection
- From: Laurent Bossavit
- Re: Auto selection
- References:
- Auto selection
- From: tailorma_de
- Re: Auto selection
- From: Dmitry A. Kazakov
- Re: Auto selection
- From: tailorma_de
- Re: Auto selection
- From: Dmitry A. Kazakov
- Auto selection
- Prev by Date: Re: Command pattern: Interaction allowed?
- Next by Date: Re: Command pattern: Interaction allowed?
- Previous by thread: Re: Auto selection
- Next by thread: Re: Auto selection
- Index(es):
Relevant Pages
|