Modules excluded

Daniel xracoonx at gmx.de
Fri Feb 3 08:03:39 UTC 2023


On 2023-02-03 01:18, Richard Kimberly Heck wrote:
> On 2/2/23 17:31, Jean-Marc Lasgouttes wrote:
>> Le 02/02/2023 à 23:12, Daniel a écrit :
>>>> The problem is when the depencies/exclusion graph contains 
>>>> furstrated loops. Something like
>>>>
>>>> - one has B, which provides feature "foo"
>>>> - want to insert A, which requires C
>>>> - C is incompatible with B
>>>> - of course the solution is to install D instead of B, because it 
>>>> also provides feature "foo" like B does, but how to find this solution?
>>>
>>> Automatically installing another module because it provides a certain 
>>> feature seems over the top. In your case I would just go with what 
>>> the user had done, i.e. tried to add A. So, ask:
>>>
>>> Add A and C and remove B? [Yes] [No]
>>
>> Obviously, I botched my exemple. My intention was to add the A 
>> requires the feature "foo" provided by B.

I see. So in this case it would be

- Add A, C and D and remove B [Yes] [No]

But I guess that is tricky to implement.

> I can't remember who used to say this all the time---maybe it was you, 
> JMarc---but one of the rules I learned early on here was: Don't try to 
> outsmart the user. So my worry was along these lines: Sometimes there 
> might be different ways to proceed, but we are going to have to choose 
> one, but on what ground? Better to let the user figure this out.

That sounds reasonable. Though my idea would be "let the user choose" 
(not to "choose for the user"). So, in a case of disjunctive 
requirements, the user could be presented with the list of possible 
options. But again, maybe that is too tricky.

> One thing we might do, though, is provide a bit more information about 
> why certain modules can't be installed. At the moment, the Add button 
> gets disabled, and there is information in the description of what it 
> excludes and requires. But maybe it would help to add to the tooltip, 
> say: "Cannot be added because it conflicts with..." or "...because it 
> depends upon module X...".

Something felt oddly cumbersome when playing around with the theorems 
modules. I haven't used them for a while, so I felt like a new user 
would be a bit perplexed too. Also, I had to scroll the description in 
order to see the requirements and exclusions. But I guess if one has 
used it a couple of times, in particular the same combinations, it feels 
rather easy.

I am not sure I would be inclined to expect a helpful tooltip on a 
disabled button.

I guess excluded modules and modules with unsatisfied requirements could 
be grayed out with "(unsatisfied req.)" and "(excluded)". (We only have 
grayed out with "(missing req.)" for missing package requirements so 
far.) So, one would get direct information in the list, and also when 
something becomes or ceases to be available due to the user's action. It 
will give the user a better feel for what is happening in the module 
dialog, I think.

Daniel




More information about the lyx-devel mailing list