| Summary: | Please make behaviour (display) of tools started from within the Mageia Control Center more consistent. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dick Gevers <dvgevers> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | anaselli, mageia, marja11, matteo.pasotti, micheelsen, nic |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA4TOO | ||
| Source RPM: | drakxtools | CVE: | |
| Status comment: | |||
|
Description
Dick Gevers
2011-03-19 17:25:44 CET
Ahmad Samir
2011-03-19 18:20:29 CET
Source RPM:
drakconf-12.21.1-1.mga1 =>
drakxtools
Manuel Hiebel
2011-10-01 23:23:00 CEST
Assignee:
bugsquad =>
thierry.vignaud only pinging so this bug won't show up in my "NEW, but no activity for over 3 months" list CC:
(none) =>
marja11
Thierry Vignaud
2012-01-02 17:37:00 CET
Priority:
Normal =>
Low Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja Keywords:
(none) =>
NEEDINFO Valid for 2 and Cauldron.
Sander Lepik
2012-05-28 12:52:22 CEST
CC:
(none) =>
sander.lepik (In reply to Nic Baxter from comment #4) > Still valid? Close? Still valid, it won't get fixed if we don't lure a bunch of perl developers into contributing to Mageia. I'll CC Anaselli and Pasmatt, though, who are porting our tools to libyui (adminpanel, soon to be called manapan, IIRC) They ported this behaviour along with it, but are very short on time, too, so we might have to just live with it. @ Anaselli & Pasmatt Is it useful to clone this report for adminpanel? CC:
(none) =>
anaselli, matteo.pasotti
Marja Van Waes
2015-02-14 10:27:20 CET
Whiteboard:
MGA2TOO =>
MGA4TOO Marja adminpanel (e.g. manatools) is not affected by that, in the meaning that what you see when you run as standalone, is the same as into the application launcher (mpan). Certainly in our TODO list we added, and we will develop it as soon as possible, the idea of having a common base layout for tools, at least for push buttons and their shortcuts, e.g. usually Information, Ok and Cancel. But we have to think about it better. The idea is to provide a template to use for further developers or new applications, and of course the ones we have just now have to be fixed following that layout. (In reply to Angelo Naselli from comment #6) > Marja adminpanel (e.g. manatools) is not affected by that, in the meaning > that what you see when you run as standalone, is the same as into the > application launcher (mpan). AFAIK all our drak* tools behave the same as standalone tool and when called from MCC, only the screen and the title of the screen may differ. So this bug is really only about things like the way to quit a tool being different in one tool than in another, regardless of whether it is called via MCC or as standalone tool. I've seen the very same difference in behaviour between different mpan/mana/dragora tools, so yes: they are affected. > Certainly in our TODO list we added, and we will develop it as soon as > possible, the idea of having a common base layout for tools, at least for > push buttons and their shortcuts, e.g. usually Information, Ok and Cancel. That sounds good, thanks :-) > But we have to think > about it better. The idea is to provide a template to use for further > developers > or new applications, and of course the ones we have just now have to be > fixed following that layout. Perfect, thx!
Hans Micheelsen
2020-12-28 10:42:18 CET
CC:
(none) =>
micheelsen |