[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] [prov] How best to help the user through incompatible/bad provisioning plans

For the installation case, I can see two possibilities
1) opening the wizard again when an error is detected
2) don't let the user click the install button until the proper things have
been selected. This means that the validation is done as the user selects
and unselects things in the UI.

The update case is a bit more tricky because of the permutations that could
occur for all the things that you are looking an update for.
For example let's say that I have the SDK1 and EMF1 installed and there is
an update available for each one of them.
In this case I will see two entries in the update dialog (SDK2 amd EMF2).
Now there are two cases:
- either SDK2 can replace SDK1 and keep EMF1 happy in which case there is
no problem (same goes for EMF2)
- either SDK2 breaks EMF1, in which case the update dialog will show a red
X next to SDK2. Because the question answered by the validation done is
"can I replace SDK1 by SDK2 without breaking anything else"?
However in these two cases, the user is not given the ability to install
the both SDK2 and EMF2 who will work together.

So in short, unless we explore the permutations of all the things that can
be installed from the update, I think we can't do a meaningful validation.

So what I'm proposing it to make the update dialog the same than the
install dialog except that the content shown is filtered based on what the
user has already installed. In this dialog the updates are not
pre-validated, they are just shown. Then the workflow for the update is the
same than the install one and we can use one of the two possibilities
described above for the installation.

   HTH

   PaScaL


|------------>
| From:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Susan Franklin McCourt <susan_franklin@xxxxxxxxxx>                                                                                                |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To:        |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |equinox-dev@xxxxxxxxxxx                                                                                                                           |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |02/12/2008 05:33 PM                                                                                                                               |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| 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