Mailinglist Archive: zypp-devel (92 mails)
| < Previous | Next > |
Re: [zypp-devel] Deprecated Pattern::install_packages() ?
- From: "Benji Weber" <benji.weber@xxxxxxxxx>
- Date: Fri, 24 Aug 2007 23:52:16 +0100
- Message-id: <d6b310ce0708241552m70d8ab02k81609587d511a2f6@xxxxxxxxxxxxxx>
On 24/08/07, Stefan Hundhammer <sh@xxxxxxx> wrote:
> As a user, I want to know what packages I'll get before I select a pattern. If
> the new behaviour is like you described, the user will se no pattern content
> (no packages) before selecting the pattern and all packages that somehow got
> dragged into the install set (regardless whether by the pattern or otherwise)
> afterwards.
I think this might because you are an advanced user who understands
package management. Do you think $User who wants to install KDE really
cares that he needs to install libqt kdelibs kdepimlibs libkde
kde-konqueror kde-kget etc etc?
I'm not so sure seeing pattern content prior to selection is necessary
for non-technical users. The result of potential installation can be
displayed post-solve as the API permits.
I knocked up a quick functional pattern selector in YCP that operates
in this manner:
http://benjiweber.co.uk/patternselector/1-select-patterns.png
http://benjiweber.co.uk/patternselector/2-display-results-of-solve.png
http://benjiweber.co.uk/patternselector/3-apply-changes.png
If you want to play grab
http://benjiweber.co.uk/patternselector/patternselector.ycp
> This invalidates the whole idea of that "Patterns" filter view. The only thing
> that would make sense would to only have the simple pattern selector that
> only shows the pattern description and no content. This in turn does not fit
> at all into the package selector framework: There, you can switch between
> different filter views that all have one thing in common: They have a list of
> packages.
By the simple pattern selector do you mean
http://benjiweber.co.uk/patternselector/_existing_pattern_selection_widget.png
? I have to admit I haven't seen it used on its own like this, do any
modules use it?
> In NCurses, there is no counterpart to the simple pattern selector.
This would not be an issue if it were entirely implemented in YCP.
_
Benjamin Weber
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
> As a user, I want to know what packages I'll get before I select a pattern. If
> the new behaviour is like you described, the user will se no pattern content
> (no packages) before selecting the pattern and all packages that somehow got
> dragged into the install set (regardless whether by the pattern or otherwise)
> afterwards.
I think this might because you are an advanced user who understands
package management. Do you think $User who wants to install KDE really
cares that he needs to install libqt kdelibs kdepimlibs libkde
kde-konqueror kde-kget etc etc?
I'm not so sure seeing pattern content prior to selection is necessary
for non-technical users. The result of potential installation can be
displayed post-solve as the API permits.
I knocked up a quick functional pattern selector in YCP that operates
in this manner:
http://benjiweber.co.uk/patternselector/1-select-patterns.png
http://benjiweber.co.uk/patternselector/2-display-results-of-solve.png
http://benjiweber.co.uk/patternselector/3-apply-changes.png
If you want to play grab
http://benjiweber.co.uk/patternselector/patternselector.ycp
> This invalidates the whole idea of that "Patterns" filter view. The only thing
> that would make sense would to only have the simple pattern selector that
> only shows the pattern description and no content. This in turn does not fit
> at all into the package selector framework: There, you can switch between
> different filter views that all have one thing in common: They have a list of
> packages.
By the simple pattern selector do you mean
http://benjiweber.co.uk/patternselector/_existing_pattern_selection_widget.png
? I have to admit I haven't seen it used on its own like this, do any
modules use it?
> In NCurses, there is no counterpart to the simple pattern selector.
This would not be an issue if it were entirely implemented in YCP.
_
Benjamin Weber
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |