On Fri, 2 Jun 2000, Eric S. Raymond wrote:
> Francesco Chemolli <email@example.com>:
> > Maybe some four-state toggle for the UI
> > (force-as-no-and-force-all-dependants-as-no, weak-and-module (default),
> > weak-and-builtin, strong) could be a good UI element.
> No. No. A thousand times *no*. This is exactly the kind of nasty
> UI complication I want to avoid -- it makes modeling the interface's
> behavior too hard for the user.
> We'll have *one* set of clear, *simple* deduction rules, with a
> possible fallback to "ask the user" in case the right thing is not
> deducible. I'll be happy to join an argument about what the rules
> should be -- one advantage of the declarative-language-plus-Python
> strategy is that trying out new deduction rules has low overhead --
> but on the meta-principle of one simple set I will not budge.
Just to make myself clear. The four-state toggle would have been meant to
describe the various enabled modules. I thought it to be intuitive, but I
might be wrong, or it might be simple according to my mindset but not to
It's all right to ask the user when some kind of inference is done (i.e.
selected module foo requiring bar, if foo as module, shoudl I have bar as
a module?)`, but I wouldn't like, if I select an option with many
dependencies, to be greeted by 15 pop-ups requiring me to enter input,
-- Kinkie primary e-mail: firstname.lastname@example.org
[random fortune] Got a dictionary? I want to know the meaning of life.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:18 EST