[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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 <tjwatson@xxxxxxxxxx>                                                                       
  To:         Equinox development mailing list <equinox-dev@xxxxxxxxxxx>                                                
  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.


(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/IBM@IBMUS                
 (Embedded image moved (Embedded image moved to file: pic08031.gif)        
 to file:              equinox-dev@xxxxxxxxxxx                             
 (Embedded image moved (Embedded image moved to file: pic02449.gif)        
 to file:              10/02/2007 01:57 PM                                 
 (Embedded image moved (Embedded image moved to file: pic30219.gif)        
 to file:              [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

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,

equinox-dev mailing list
equinox-dev mailing list

Attachment: pic03929.gif
Description: GIF image

Attachment: pic31713.gif
Description: GIF image

Attachment: pic04846.gif
Description: GIF image

Attachment: pic22422.gif
Description: GIF image

Attachment: pic08031.gif
Description: GIF image

Attachment: pic02506.gif
Description: GIF image

Attachment: pic02449.gif
Description: GIF image

Attachment: pic10353.gif
Description: GIF image

Attachment: pic30219.gif
Description: GIF image