On Wed, 2003-02-12 at 20:22, Tom Brinkman wrote: > On Wednesday February 12 2003 03:17 pm, Lyvim Xaphir wrote: > > I used to could start rpmdrake 1.4 from an Eterm and then as I > > conducted actions in the UI, it would report back to Eterm exactly > > what it was doing, connecting to, unpacking, installing, etc, et > > al, ad infinitim. Very handy; very good UI experience; a good > > teamwork job between the CLI and the UI. Now with 9.1 all that is > > history. > > That's not fair. The underlying functionality (urpmi) is greatly > improved, and the GUI frontend's for it are improving.
OK, I agree that things are improving; but you should know that I never meant to intimate that the underlying functionality itself was not getting better. My beef is with the UI; and I realize that it will get better; I hope anyway. The thrust of this was never to actually resurrect all aspects of rpmdrake 1.4, backend and frontend. The objective is to reach a compromise where the backend performs to expectations while pushing a frontend that is as usable as 1.4 was, while perhaps at the same time having attributes that would satisfy the needs of users like Anne. > At least the > complaints from the naysayers have dimished. GUI's are always gonna > be a hotbed of debate as to what's better, more intuitive, and > userproof. If you read thru the past discussions on the cooker > archives as I previously advised, I believe you'll understand that > the change was necessary to improve functionality. I don't have any problems with the backend changes; but I continue to maintain that more compromises should have been considered with regard to the UI. > > If you always want to be able to see what's happening and when, > use urpmi on the CL. You were sort'a kind'a doin it anyhow runnin > rpmdrake in a terminal. As of right now, that's certainly what is happening, and I appreciate your advice in that direction. > Well, I've expressed the following sentiment in regards to GUI's > for burnin CDr's, and I believe it equally applies to rpm management > (among many other tasks). The best way to learn how to use a GUI > front end, is to become familiar and proficient with how the > underlying task is accomplished on the CL first. That's fine, and for the most part I agree; but I just don't have time to examine every single aspect of the system in excruciating exhaustive detail all the time. Sometimes I need to actually get stuff done, and then move on to more important productive things. On a rainy day when I have time, great; but not right now. In other words, rpmdrake is not the sole reason for my existence on planet Mandrake, although it does (used to rather) grease the rails. Rpmdrake 1.4 was a valuable tool that allowed me to accomplish these things. > As to votes for rpmdrake 1.4... don't hold your breath. It ain't > gonna happen. MOF, I think I'll go vote for the status quo ;~PPP You go right ahead. That's what the voting system is supposed to be used for. :) LX -- ��������������������������������������������������� Kernel 2.4.21pre4-1mdk Mandrake Cooker 9.1 Enlightenment 0.16.5-12mdk Evolution 1.2.1-1mdk Registered Linux User #268899 http://counter.li.org/ ���������������������������������������������������
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
