[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [equinox-dev] New Update Manager UI : Your thoughts
|
This is a classic producer/consumer
viewpoint issue. If you bake it into the bundle/feature/group/...
then you limit the consumption scenarios. Yes, it is true, one could
allow this policy to be set by the bundle producer but I would very very
strongly urge people to never set it to "force" (whatever). Look
at it another way, I think my thing is "Eclipse" so I put "Eclipse"
everywhere in the messages. You think your thing is your product
(RAD, Foo, Bar, ...) and get very bummed when users see "Eclipse"
everywhere. Similarly, you are some enterprise that has bought a
site license for a product that happens to include some bundles that have
this force bit set. Now all your users are faced with license questions
when they update.
Anyway, it may be that we allow producers
to force license display but I really hope no one uses it. :-)
Jeff
Peter Manahan/Toronto/IBM@IBMCA
Sent by: equinox-dev-bounces@xxxxxxxxxxx
06/13/2007 09:55 AM
|
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx> |
|
|
To
| Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| Re: [equinox-dev] New Update Manager
UI : Your thoughts |
|
The need for license acceptance is typically a requirement discretion
of the plugin provider and not the consumer of the plugins. So allowing
the consumer to disable the license acceptance should only be optional
at the discretion of the plugin provider.
Peter
equinox-dev-bounces@xxxxxxxxxxx wrote on 06/13/2007 09:04:39 AM:
>
> The provisioning system should already know about the sites and
> should be able to discover more.
>
> Actually I missed in there where the users said which plugin they
wanted.
>
> User should not have to accept a license if the plugin is coming
> from a known/trusted site. Sites should be ranked in this way
>
> Restart may not be needed
>
> Jeff
>
>
>
> "Prashant Deva" <prashant.deva@xxxxxxxxx>
> Sent by: equinox-dev-bounces@xxxxxxxxxxx
> 06/12/2007 08:26 PM
>
> Please respond to
> Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
>
> To
>
> "Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>
>
> cc
>
> Subject
>
> Re: [equinox-dev] New Update Manager UI : Your thoughts
>
>
>
>
> Ok, here is some thoughts on the gui for installing a new plugin.
> This is in keeping with the philosophy of keeping the simple things
simple.
> I wish there were a place where I could upload some docs and sample
> images to make the point more clear, but i will just type some stufffor
now.
>
> 1. User clicks on 'Install new plugin'
button
> 2. Dialog box with single text field asks
to enter the url of
> pluign update site.
> 3. update manager automatically gets the
latest available
> version of the plugin.
> 4. asks the user to accept the license.
> 5. if license accepted, then installs plugin
and asks user torestart.
>
> The update site url, etc are automatically saved by the program and
> user doesnt need to give a 'name' along with the url as we have to
do now.
> Also no dialog box for confirming 'install all'. All user has to
> enter is the url and accept the license.
>
> the dialog in step 2 can have an 'advanced' button, which when
> selected allows user to choose the exact version to install.
>
> your thoughts? any compulsory steps in the install process we might
> be missing this way?
>
> prashant_______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
Attachment:
smime.p7s
Description: Binary data
