Dj Marian a écrit :
Hello,
from former updates or package selections
if you have mdv installed for one year and you only choose some packages
keep a record of what is not selected (not wanted) on the system by
the user
Urpmi (the console program used by the graphical Rpmdrake) already knows
everything installed.
based on these things it could guess you don´t want everything to show
up on your screen
But currently, the user can still have the option to select other
packages if they wish.
and i think some users might benefit if they would have less packages
to choose from, the new users...
If using the default display by category, the user only has to go into
categories of interest.
Note that there have been numerous posts suggesting folding related
packages into one line (expandable to see each individual package),
which would greatly reduce the number of lines to choose from. This
would be very advantageous for localisations, as few users want every
language. Also useful for applications with many modules in separate
packages, like Mozilla Firefox and OpenOffice.
As I understand it, the default display is only GUI packages, which also
reduces choices for the newer user.
when i first installed mdv (last year after i deleted mdv 2008 from my
netbook) i needed some programs i looked for them in ´install and
remove software´ and some were confusing me...
One problem is the descriptions, many of which definitely need
improvement ...
so by keeping a large scale record of what users usually select, a
default guessing can be forced on every user on fresh install (the
buttons show more and/or show less would be good for someone who
doesn´t like the idea of being forced to accept something), after
let´s say 100 installed packages the user´s selection profile can
start to be clear
if he only selects gui packages, it´s clear he doesn´t want other ones
on the screen
Only Gui packages is a option at top left. (It may be the default, but
personally I would never restrict myself to that : many command-line
packages have internal menus and are very user-friendly.)
The problem is that if a user does a fresh install, the disk is normally
reformatted, thus removing any history. Reformatting the disk is
advisable to remove accumulated junk on the disk, as well as for
stability. However this can be overridden.
If the user wants to keep more or less the same packages, they can do an
update to a new release rather than a fresh install.
The currently installed packages are automatically replaced by newer
versions.
In some cases a newer version of a package is not available, sometimes
replaced by an equivalent, which may entail a choice by the user during
installation.
In any case, virtually no selection by the user to get essentially the
same configuration.
also if he has a profile on the mageia website, the profile could save
the user´s packages clicks online
when he logs in, mageia could just download his former profile without
asking (or maybe asking is good)
also if the user suddenly is a better linux user and for another 100
clicks he selects all kinds of packages, the former 2000 clicks should
have less influence on what appears on the screen, than the last 100
clicks
This all sounds a little complicated.
1) There is a security risk in storing the user's configuration online,
and also a question of privacy, so the user should always be asked.
2) Inexperienced users have a tendancy to accept everything, so the
default should be no.
Thus the users most likely to benefit are the least likely to use this
service.
3) There is the problem of identifying the user, in order to retrieve
the information.
If an email adresse is used, the user must remember to use the same adresse.
But it also increases the risk to security.
If the user must log in to a profile, they must remember the identity
and password. Again more challenging to a newer user.
Another possibility is to create a special file on disk, which could be
recuperated during a fresh install, if the user is using the same computer.
However it seems to me that improving the interface of Rpmdrake is a
better approach.
Exactly what changes is still under active discussion; there have been
many posts on this subject.
There has also been much discussion on using groups focused by usage to
simplify selection on installation, which could conceivably be
introduced to Rpmdrake as well.
while updating, maybe he never chooses and always updates
everything... in this case a button ´install all updates´
To do this :
1) Select "all updates", top left.
2) Press button "Select all", bottom left.
3) Press button "Apply", botton near right.
But maybe adding a single button is a good idea.
Although this could be problematic for bandwidth limited users, so some
way of deselecting some updates must remain an option.
By the way, in no way am I trying to discourage your input. Experienced
users/programmers like myself tend to overlook many details which are
daunting to newer users.
So your input is essential to a more usable product.
as a tooltip near the clock instead of the mdv usual would be faster,
painless, and appreciated by a new user who has no idea and doesn´t
care what would be best for him to update
Dan.
- André
