[Mageia-dev] The shiny new Control Center

nicolas.lecureuil at free.fr nicolas.lecureuil at free.fr
Sun Sep 30 09:03:34 CEST 2012


> ----- Mail original -----
> De: "Steven Tucker" <tuxta2 at gmail.com>
> À: "Mageia development mailing-list" <mageia-dev at mageia.org>
> Envoyé: Samedi 29 Septembre 2012 14:14:03
> Objet: [Mageia-dev] The shiny new Control Center
> 
> Hi everyone,
> 
> I have been doing a little work on the proposed control center - mcc2
> 
> https://wiki.mageia.org/en/Feature:UiAbstraction4mcc
> 
> and would like to put a couple of questions forward to find some direction.

i don't see the point of this rewrite. This have not been discussed a lot but i think that
this is a lack of time. For me the prior thing to do would be to write a interactive::qt for mcc using perl-qt4 or perl-kde4

I think  that if you want to write it in an other language this is more because you have not saw  that all our code is linked 
so you will double the code base,  the code to maintain, the possible bugs, etc etc.

> 1/ What should we call it ??
> 
>          I have been using mcc2 as a working name, however I'm not 
> convinced this is the right approach. I will soon be uploading the code 
> (been using my own svn repo up till now), and it would be good to start 
> with the name it will stick with. Should the name relate to Mageia?, or 
> should it be more generic?
> 

you will upload it where ? you can use a github repo i think to make it public.

> 2/ What languages should be available for writing modules? (Perl, C++, 
> python and Ruby are possibilities)
> 
>          So far mcc2 has been written in Perl (even though I had never 
> written a line of Perl prior to starting this) so as to make porting 
> existing modules a matter of just replacing the Ui calls, but I do like 
> the idea of allowing the modules to be written in more than 1 language 
> to encourage more contributors who may be turned off by having to learn 
> another language.
> Sticking with Perl will make mcc2 core easier, so I may do that 
> initially regardless. What do you all think?? Is sticking with 1 
> language preferred even if it means less contributors, or is the goal to 
> attract as many module developers as possible?

yes but our libraries are in perl too don't forget this ( libDrakX ). In general i am not a big fan of 
mixing languages.

> 3/ What should the license be?
>          I would be happy to make it GPL V3, but is there any argument 
> for something different ?

As mcc is in gplv2+ i think you have to stick with this licence ( not 100% sure )

> 4/ As an official Mageia project, do I need to sign the copyright over 
> to Mageia ??
>          I am more than happy to do so, I would only ask that I get 
> noted somewhere as the developer, hopefully others will join the 
> developer list as well.


> Just to give you an idea of where my code is at ......
> It is still in early stages, with I would guess about 400 - 500 lines of 
> code.
> It works across ncurses, gtk and qt with a consistent interface, however 
> there seems to be a bug in the libyui-qt libriaries which Angelo and 
> Matteo will be looking into (Big thank you to those guys for packaging 
> the libyui libraries and helping out when I have questions). 

libyui has been choosen w/o real discussions, i don't want you to loose you time if 
at final we don't choose it.


> I have little time to work on this for the next 6 weeks, but I hope to 
> have the core system complete, or near to complete when Santa visits, 
> though porting (and adding new) modules will be the bigger task.

better work would be to fix existing one and add new interactive::qt ( or qt4 ). 
And seeing the != between qt4 and qt5 the port to qt5 will be a 'piece of cake'.



More information about the Mageia-dev mailing list