On Friday 24 August 2007 11:03, Stefan Schubert wrote:
Katarina Machalkova schrieb:
Provided that this method is really deprecated, I'm probably supposed to use something else instead, to achieve the same goal in UI ;-) Could you please point me to some other libzypp method I can possibly use, or advise me how to collect names of the packages that will be installed once user select a pattern?
This was a very quick hack and with a lot of unexpected behaviour. Now you only have to select the pattern and make a complete solver run. The solver will select the concerning packages which you will have to pick up then.
But that's not the same.
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.
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.
In NCurses, there is no counterpart to the simple pattern selector.
In Qt, I would feel forced to throw the patterns filter view out of the
package selector (because without a package list it really is out of place
there). This OTOH would be a big step backward for the users.
Very much the same would be true for patch contents that (AFAICS) has the same
problem: No list of packages any more.
How are we going to go ahead with this?
CU
--
Stefan Hundhammer