Re: [equinox-dev] [prov] How best to help the user through incompatible/

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

This is definitely a tricky problem.
A likely scenario is that they have installed some additional plug-in,
and that plug-in has a constraint that is not compatible with constraints
in the updates (The extra plugin requires version 1 of "foo",
and the update requires version 2). The problem is, our solver might not
be able to come up with a simple explanation that makes any sense to the
user (they likely know little about the various IUs they have installed).
 Until we can come up with an explanation that allows us to guide
the user through correcting the problem, I would opt for keeping quiet
in the automatic update case (just log it). Personally, it drives me crazy
when applications have uninvited and unsuppressible modal popup dialogs
about updates. If the update can proceed silently it's fine. If I explicitly
asked for an update, it's ok to prompt me about problems. But if I didn't
ask for it, don't bother me about it. It would be nice if there as an unobtrusive
way to let the user know though - such as a trim widget that gets an error
overlay added.  In the updates dialog, we would presumably still show
the updates, and the user can try the update from there if they want to.

John

Susan Franklin McCourt <susan_franklin@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

02/12/2008 05:33 PM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To	equinox-dev@xxxxxxxxxxx
cc
Subject	[equinox-dev] [prov] How best to help the user through incompatible/bad provisioning plans

Hi, everyone.
I've been struggling with how to handle the case where the user has automatic
updates on, we find updates, but the resulting provisioning plan for those
updates is not OK. Meaning, there is some incompatibility/problem. Do we
tell the user? Do we let them try to update anyway? etc. etc...

This issue also applies to provisioning actions the user selects. They
select A, B, C and say "Install..." but the resolver can't find
a plan that satisfies everything. What then? We currently just report the
(often cryptic) error. Should we let them try anyway, or at least open
the wizard and let them check/uncheck things until they get a good solution?

If you have any thoughts in this area, could you please read and respond
in this bug?
https://bugs.eclipse.org/bugs/show_bug.cgi?id=217927

thanks,
susan_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev