From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-October/019074.html | 82 +++++++++++++++++++++++++++++ 1 file changed, 82 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-October/019074.html (limited to 'zarb-ml/mageia-dev/2012-October/019074.html') diff --git a/zarb-ml/mageia-dev/2012-October/019074.html b/zarb-ml/mageia-dev/2012-October/019074.html new file mode 100644 index 000000000..9e4bcb84f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-October/019074.html @@ -0,0 +1,82 @@ + + + + [Mageia-dev] The shiny new Control Center + + + + + + + + + +

[Mageia-dev] The shiny new Control Center

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Mon Oct 1 11:48:25 CEST 2012 +

+
+ +
2012/10/1 Angelo Naselli <anaselli at linux.it>:
+>
+> Good point, but as a developer i could say we can make it
+> configurable. I mean a generic panel can have the name into its
+> configuration file and shown on title, while to run it a script
+> called mcc can run "generic_panel -c mcc.conf" for instance,
+> we can also fix that as default forcing mageia behaviour :)
+
+Sure, as long as the name "mcc" shows up in reviews and in the user's
+minds and not something like "foobar, an overworked new version of the
+formerly called mcc".
+
+> Said that we're using libyui, that is a work in progress abstraction
+> for the Suse Yast panel, so we're not reinvent the wheel :)
+
+May be I misunderstand this sentence, but the new mcc will not carry
+any "yastish" ingredients or behavior?
+(From SuSE 4.4.1 on until today YaST has always been one outstanding
+reason for me to not use SuSE)
+
+-- 
+wobo
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1