blob: 9e4bcb84f7eb85bf1582c703113f7b724920a012 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] The shiny new Control Center
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20The%20shiny%20new%20Control%20Center&In-Reply-To=%3CCA%2Bh4nj5kKCJKocwJL3h%3DiGb9AaeZJAUGijSXzhmTA99XSTLd2w%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="019073.html">
<LINK REL="Next" HREF="019075.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] The shiny new Control Center</H1>
<B>Wolfgang Bornath</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20The%20shiny%20new%20Control%20Center&In-Reply-To=%3CCA%2Bh4nj5kKCJKocwJL3h%3DiGb9AaeZJAUGijSXzhmTA99XSTLd2w%40mail.gmail.com%3E"
TITLE="[Mageia-dev] The shiny new Control Center">molch.b at googlemail.com
</A><BR>
<I>Mon Oct 1 11:48:25 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="019073.html">[Mageia-dev] The shiny new Control Center
</A></li>
<LI>Next message: <A HREF="019075.html">[Mageia-dev] The shiny new Control Center
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#19074">[ date ]</a>
<a href="thread.html#19074">[ thread ]</a>
<a href="subject.html#19074">[ subject ]</a>
<a href="author.html#19074">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>2012/10/1 Angelo Naselli <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">anaselli at linux.it</A>>:
><i>
</I>><i> Good point, but as a developer i could say we can make it
</I>><i> configurable. I mean a generic panel can have the name into its
</I>><i> configuration file and shown on title, while to run it a script
</I>><i> called mcc can run "generic_panel -c mcc.conf" for instance,
</I>><i> we can also fix that as default forcing mageia behaviour :)
</I>
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".
><i> Said that we're using libyui, that is a work in progress abstraction
</I>><i> for the Suse Yast panel, so we're not reinvent the wheel :)
</I>
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
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="019073.html">[Mageia-dev] The shiny new Control Center
</A></li>
<LI>Next message: <A HREF="019075.html">[Mageia-dev] The shiny new Control Center
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#19074">[ date ]</a>
<a href="thread.html#19074">[ thread ]</a>
<a href="subject.html#19074">[ subject ]</a>
<a href="author.html#19074">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|