While watching some great talks in Nokia Developer Summit, Monaco I decided to blog about our new Network Manager which is made with great capabilities of KDE, Qt and Comar.
If you remember from my blog entry about Network Manager Plasmoid, Pardus uses Comar layer for all stuff that needs by a desktop user; networking, user operations, service operations, display management, disk management etc. It also integrated with PolicyKit; so you can define atomic privileges per user. Comar also provides great API that helps Qt’s “Code less, Create more.” thought ;)
For example, to connect a profile that you have in your wireless profile list:
>> import comar
>> link = comar.Link()
>> link.Net.Link['wireless_tools'].setState('Monaco','up')
That’s all ! And if you need a privilege for this operation Comar will call PolicyKit-Kde4 for asking you a password ;) Comar uses D-Bus for communication and it is possible to make aysnc calls just by using async key and proper function to notify by current operation.
And this is the New Network Manager of Pardus !
Don’t forget to watch the screencast in here !
If everything goes ok I will be at Akademy Gran Canaria and I hope we will show you a lot of impressive tools that we made ;)
Be Here To Love Me by Norah Jones
![[FSF Associate Member]](http://blog.ratonred.com/wp-content/uploads/2008/11/getbutton.png){kind=small}
#1 by friesoft on 28 April, 2009 - 18:40
Quote
Holy shit!! That’s one hell of a powertool :-)
And still it looks really simple to handle… great job .. I’m not yet familiar with Pardus (just by name) but any chance to get this also upstream? (e.g. into extragear?)
I’ll definately give pardus a try :-)
#2 by Dario Freddi on 28 April, 2009 - 18:56
Quote
Not to bring your work down, that is surely great, but why didn’t you simply make a Solid backend for Comar (something I strongly suggest you to do, in any case) and helped us in abstracting KDE’s NetworkManagement Plasmoid? It would have really helped you in not maintaining yet another tool, and I still hope you’ll consider the possibility of using NetworkManagement in the future :)
P.S.: I am still waiting for someone to answer my mail about GSoC on pardus-dev
#3 by Abdurrahman AVCI on 28 April, 2009 - 18:57
Quote
WOOW man, it looks awesome.
#4 by Giovanni on 28 April, 2009 - 19:27
Quote
Will pardus changes be merged with “upstram” network-management plasmoid?
#5 by Lzfy on 28 April, 2009 - 23:56
Quote
Cool It looks much better then the current network manager plasmoid. Pardus 2009 will be my new distro as soon as it’s out.
#6 by Gökmen Göksel on 29 April, 2009 - 11:40
Quote
Thanks for everyone for comments ;)
@ Dario Freddi
Pardus is using Comar for three years for network operations and Comar’s Network Backend has great features and its pretty more than the Gnome’s NetworkManager backend. By the way, I can use Gnome’s NetworkManager and also Solid & KDE solution in Pardus but as you know the development decisions of Gnome’s NetworkManager is up to Ubuntu or another power behind the Gnome :) So, for a from scratch distribution view, Pardus can not wait one for a needs in Network backend. You could say; you can fork and walk in your way, but this time there is another problem appears; programming languages: we are widely use python in almost all of our applications and we are very happy with it :) It is very easy to add a new feature to Comar’s network backend.
Network Manager in Pardus uses Solid for notifying the desktop for network status but not more than; I actually I like Will Stephenson comment about this situation: http://tinyurl.com/dh8r8z
If you want we can discuss it in pardus-devel, because it is very hard write something in this little box :)
@ Giovanni
Pardus NM and KDE’s one are different but I hope we can merge something with upstream ;)
Pingback: Le “nouveau” gestionnaire réseau de Pardus « Le blog d’un manchot pardusien