Guillaume Cottenceau wrote:
Eric Fernandez <[EMAIL PROTECTED]> writes:The problem is :
Right, but what is the relationship between the language and the
GUI concept ? I can understand the changes : they wanted to
integrate rpmdrake to the whole control center, which is a good
idea. Actually, the tabs of the previous rpmdrake have been
replaced by buttons in the CC. However, the ease of use has
decreased. To perform as simple operations as packages search, I
prefer to use urpmq in the console. This is a sign the GUI is not
very convenient for that.
Hum? 1. open rpmdrake 2. enter the text in search entry and hit enter What's the problem with that?
1) Open the control center
2) Choose "Install software"
3) Make a search for a package (example : xine)
4) It says it found nothing
5) You wonder : maybe it was already installed ?
6) Close "Install software"
7) Open "Remove Software"
8) Search xine
9) Bingo ! It has been found !
Using the console : urpmi -r xine and you know the package exists, wherever it is : locally installed, or on a remote server, ready to be downloaded and installed.
There are two issues here :
1) I think it is illogical to have two independent search engines, one for remote and uninstalled packages, and one with local and installed packages. I think it would be more convenient if there were only one search box. Then, if the package is not installed, an "Install" button would appear (and also all information : on what medium/server is it, files list, dependencies, etc...) or if the package is already installed, a "Uninstall" button would appear (and information : package version,files list, etc...) A colour code in the background (or whatever) could differenciate clearly both procedures, to avoid mistakes. This is basic GUI concept to not split the same request box into several meanings. At least this is my vision of a GUI, do other people share mine ?
2) Moreover, the "install software" engine is misinformative : it claims that it did not find any package, if it has already been installed. Then you can think that this package does not exist at all. You may also think you make a spelling error.
3) there is a vocabulary issue : why to call "Mandrake choice" what is the "Mandrake tree" or "categorization". This is a minor point (I like this way to order it, it is not a negative criticism, it is just the "choice" word I don't like).
Eric
