RE: [equinox-dev] [p2] UI priorities for M3
Hi, Walter.
Thanks for the info. I'm not sure yet how p2 will affect the workbench
startup logging issues, but the discussion about making it more obvious
that a plug-in is not enabled in the configuration is definitely relevant
to us. I put a pointer to that bug in this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=205517
This bug was opened today to track update manager usability concerns and I
encourage anyone who knows of current update manager usability bugs to
post references to this bug.
thanks,
susan
"Walter Harley" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
10/03/2007 12:07 PM
Please respond to Equinox development mailing list
To: "Equinox development mailing list"
cc:
Subject: RE: [equinox-dev] [p2] UI priorities for M3
Hi, Susan. Somewhat related to the update issue, I think, is
https://bugs.eclipse.org/bugs/show_bug.cgi?id=174515, which concerns how
users are notified when plugins on their machine have failed to load. I
would really like to see some attention to this bug - partly because I'm
responsible for some plugins that only load on 1.5 or even 1.6, but also
because I spend time monitoring eclipse.newcomer and this seems to be an
ongoing source of problems there.
Thanks,
-Walter Harley
JDT APT team
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Susan M Franklin
Sent: Tuesday, October 02, 2007 11:52 AM
To: equinox-dev@eclipse.org
Subject: [equinox-dev] [p2] UI priorities for M3
Hi, everyone.
One of the goals for M3 is to try to define the conent/scope of our 3.4
deliverable. So I'm trying to balance our desire to resolve unknowns with
getting current workflows more polished. I'm interested in the
community's feedback on the current M3 UI plan, which currently includes
- improving the install/uninstall/update workflow by providing more info
(size, time, invalid states, etc.)
- polling for software updates and notifying the user
- improved support for browsing repos (IU categories and filtering)
- more info in admin artifact repo views
(You can see the expanded detail at
http://wiki.eclipse.org/Equinox_p2_User_Interface#Milestone_plan).
This is a rather aggressive plan but still does not address some other big
UI items, most notably
- UI for rollback
- presentation of licenses
So if you have opinions on the pressing issues and priorities in the UI,
please let me know via this list, or annotating bugs you care about,
etc
thanks,
susan___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
RE: [equinox-dev] [p2] UI priorities for M3
Hi, Susan. Somewhat related to the update issue, I think, is https://bugs.eclipse.org/bugs/show_bug.cgi?id=174515, which concerns how users are notified when plugins on their machine have failed to load. I would really like to see some attention to this bug - partly because I'm responsible for some plugins that only load on 1.5 or even 1.6, but also because I spend time monitoring eclipse.newcomer and this seems to be an ongoing source of problems there. Thanks, -Walter Harley JDT APT team From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Susan M Franklin Sent: Tuesday, October 02, 2007 11:52 AM To: equinox-dev@eclipse.org Subject: [equinox-dev] [p2] UI priorities for M3 Hi, everyone. One of the goals for M3 is to try to define the conent/scope of our 3.4 deliverable. So I'm trying to balance our desire to resolve unknowns with getting current workflows more polished. I'm interested in the community's feedback on the current M3 UI plan, which currently includes - improving the install/uninstall/update workflow by providing more info (size, time, invalid states, etc.) - polling for software updates and notifying the user - improved support for browsing repos (IU categories and filtering) - more info in admin artifact repo views (You can see the expanded detail at http://wiki.eclipse.org/Equinox_p2_User_Interface#Milestone_plan). This is a rather aggressive plan but still does not address some other big UI items, most notably - UI for rollback - presentation of licenses So if you have opinions on the pressing issues and priorities in the UI, please let me know via this list, or annotating bugs you care about, etc thanks, susan ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [p2] UI priorities for M3
I glanced through it and there are some interesting ideas. I will provide feedback through the appropriate channels. From: Thomas Watson <[EMAIL PROTECTED]> To: Equinox development mailing list Date: 10/02/2007 03:42 PM Subject: Re: [equinox-dev] [p2] UI priorities for M3 There is a proposal for a new Bundle-License manifest header that will be considered for the next release of the OSGi specification. We will need to monitor this RFC #125 to ensure that it meets our needs for presentation of licenses in p2. This is not an immediate concern for p2 but we need to make sure the proposal is something we can use in the future. Tom (Embedded image moved to file: pic03929.gif)Inactive hide details for Susan M Franklin---10/02/2007 01:57:50 PM---Hi, everyone.Susan M Franklin---10/02/2007 01:57:50 PM---Hi, everyone. (Embedded image moved (Embedded image moved to file: pic04846.gif) to file: Susan M Franklin/Beaverton/[EMAIL PROTECTED] pic31713.gif) From: (Embedded image moved (Embedded image moved to file: pic08031.gif) to file: equinox-dev@eclipse.org pic22422.gif) To: (Embedded image moved (Embedded image moved to file: pic02449.gif) to file: 10/02/2007 01:57 PM pic02506.gif) Date: (Embedded image moved (Embedded image moved to file: pic30219.gif) to file: [equinox-dev] [p2] UI priorities for M3 pic10353.gif) Subject: Hi, everyone. One of the goals for M3 is to try to define the conent/scope of our 3.4 deliverable. So I'm trying to balance our desire to resolve unknowns with getting current workflows more polished. I'm interested in the community's feedback on the current M3 UI plan, which currently includes - improving the install/uninstall/update workflow by providing more info (size, time, invalid states, etc.) - polling for software updates and notifying the user - improved support for browsing repos (IU categories and filtering) - more info in admin artifact repo views (You can see the expanded detail at http://wiki.eclipse.org/Equinox_p2_User_Interface#Milestone_plan). This is a rather aggressive plan but still does not address some other big UI items, most notably - UI for rollback - presentation of licenses So if you have opinions on the pressing issues and priorities in the UI, please let me know via this list, or annotating bugs you care about, etc thanks, susan___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev <><><><><><><><><>___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [p2] UI priorities for M3
There is a proposal for a new Bundle-License manifest header that will be considered for the next release of the OSGi specification. We will need to monitor this RFC #125 to ensure that it meets our needs for presentation of licenses in p2. This is not an immediate concern for p2 but we need to make sure the proposal is something we can use in the future. Tom From: Susan M Franklin/Beaverton/[EMAIL PROTECTED] To: equinox-dev@eclipse.org Date: 10/02/2007 01:57 PM Subject:[equinox-dev] [p2] UI priorities for M3 Hi, everyone. One of the goals for M3 is to try to define the conent/scope of our 3.4 deliverable. So I'm trying to balance our desire to resolve unknowns with getting current workflows more polished. I'm interested in the community's feedback on the current M3 UI plan, which currently includes - improving the install/uninstall/update workflow by providing more info (size, time, invalid states, etc.) - polling for software updates and notifying the user - improved support for browsing repos (IU categories and filtering) - more info in admin artifact repo views (You can see the expanded detail at http://wiki.eclipse.org/Equinox_p2_User_Interface#Milestone_plan). This is a rather aggressive plan but still does not address some other big UI items, most notably - UI for rollback - presentation of licenses So if you have opinions on the pressing issues and priorities in the UI, please let me know via this list, or annotating bugs you care about, etc thanks, susan___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev <><>___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] [p2] UI priorities for M3
Hi, everyone. One of the goals for M3 is to try to define the conent/scope of our 3.4 deliverable. So I'm trying to balance our desire to resolve unknowns with getting current workflows more polished. I'm interested in the community's feedback on the current M3 UI plan, which currently includes - improving the install/uninstall/update workflow by providing more info (size, time, invalid states, etc.) - polling for software updates and notifying the user - improved support for browsing repos (IU categories and filtering) - more info in admin artifact repo views (You can see the expanded detail at http://wiki.eclipse.org/Equinox_p2_User_Interface#Milestone_plan). This is a rather aggressive plan but still does not address some other big UI items, most notably - UI for rollback - presentation of licenses So if you have opinions on the pressing issues and priorities in the UI, please let me know via this list, or annotating bugs you care about, etc thanks, susan___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
