Torsdag 24 august 2006 22:40 skrev [EMAIL PROTECTED]: > Yes, it helps a lot. On the installation: Would like the old progress > bar or something to tell me what is being done, and the result though. A > nice to have I know ... buttons go grey when clicked and after a short > while go normal again. I take it that it has finished the install when > it becomes normal again, or did it not install and needs other required > packages?
I try to be very explicit about what each button does. Each button executes a small script - sometimes just a single command, when the button is not grey anymore the script is done. Hopefully succesfully - but things can fail. Maybe the redirect URLs handed out a bad mirror, maybe the user forgot to lower rug security level or update smart channels, maybe their internet connection is bad etc. To get better feedback I'll recommend running it from a root terminal - that way you can follow the process in the terminal output. Not very noob friendly I know. I'll try to look into using Kommander's possibilities better in this respect but I'm afraid they're limited - as is documentation. And unfortunately my middle name is neither C++ nor Qt. But I'm considering ways to improve in this area - I'm looking into building a RPM - maybe I'll have the menu-entry always run the script in a terminal - might be a bit confusing to users - but they'll have more feedback - and they'll be able to see what goes wrong if something doesn't work right. Just an idea so far. Btw. you can open the .kmdr file with a text-editor since it's actually just an xml-file - however this also means that it's not easily readable. But it's one way to see what the script does beforehand. You can also open the script with kommander-editor. Simply right click on the buttons -> Edit Kommander-text, to see the script for each button. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
