[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [p2-dev] Proposed changes in p2 UI workflows
|
The mockups aren't intended to address (yet) exactly how we will drill down from something the user installed to the IU's that it requires.
That is something we're going to work on (https://bugs.eclipse.org/bugs/show_bug.cgi?id=224472), but for now I was just trying to show how the p2 views would integrate with the about views.
I think the need for "feature details" will become clearer later.
Other concerns are whether products will rely on it being there for backward compatibility, and whether there is any product configuration where the feature model might be represented and p2 is not part of the environment (and therefore not contributing to the about dialog). For example, would a product without self-update capability still want to show a feature view?
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=246875#c3
I think we should continue this discussion there...
susan
Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
![]()
| ![]()
| ![]()
To: P2 developer discussions <p2-dev@xxxxxxxxxxx>
cc: ui-best-practices-working-group@xxxxxxxxxxx, p2-dev@xxxxxxxxxxx, cross-project-issues-dev@xxxxxxxxxxx, p2-dev-bounces@xxxxxxxxxxx
Subject: Re: [p2-dev] Proposed changes in p2 UI workflows |
This is great. The only remark / question I have for now stand around the "feature details" mode of the about dialog:
I would get rid of the term feature altogether.
Do you envision this mode to show the relationship between the groups that are installed (or have a toggle)? Would we want to delve down to the level of each IU?
If the relationships were shown, what do you think of also showing the "installed software" items there.
PaScaL
Susan Franklin McCourt ---10/09/2008 12:28:23 PM---Hi again, everyone. Last month I asked for some input about your users and how they go about
![]()
From: | ![]()
Susan Franklin McCourt <susan_franklin@xxxxxxxxxx> |
![]()
To: | ![]()
p2-dev@xxxxxxxxxxx, cross-project-issues-dev@xxxxxxxxxxx, ui-best-practices-working-group@xxxxxxxxxxx |
![]()
Date: | ![]()
10/09/2008 12:28 PM |
![]()
Subject: | ![]()
[p2-dev] Proposed changes in p2 UI workflows |
Hi again, everyone.
Last month I asked for some input about your users and how they go about updating their software. (http://dev.eclipse.org/mhonarc/lists/p2-dev/msg00101.html)
While we didn't have overwhelming input, we did get some interesting remarks, and I changed the user personas a bit to reflect the input.
http://wiki.eclipse.org/Equinox_p2_UI_Use_Cases
>From this, I attempted to outline some use cases and then draw some conclusions about the problem areas, and from those problem statements, I mocked up some changes in the workflow.
http://wiki.eclipse.org/Equinox_p2_UI_3.5_workflows
Now we are looking for comments on the proposed changes. The wiki page lists several bug reports we are using to track suggestions and discuss the design. There is also discussion happening in the "Discussions" section on the wiki itself.
Please review and comment. I hope to begin work on some of this during M3, so the sooner the feedback, the bettter!
thanks,
susan
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
![GIF image](gifpx95GC9ToT.gif)
![GIF image](gifwZi8xyTeOR.gif)
![GIF image](gif6dDr62uSgn.gif)