Comments on: Network-Manager Plasmoid

By: KDE4 Knetwork icon/plasmoid question - openSUSE Forums

KDE4 Knetwork icon/plasmoid question - openSUSE Forums — Sat, 08 May 2010 15:46:41 +0000

[...] [...]

By: Linuxcomics

Linuxcomics — Fri, 13 Feb 2009 13:04:28 +0000

I entirely agree with Neil.
In my opinion, Pardus is the best KDE distro I have ever seen and I can’t wait for KDE4 integration in Pardus 2009.
Thanks to all Pardus developpers who do a really great job !

P.S: will the wallpaper in your screenshot be in Pardus 2009 ? I like this super hero style mascot. :-)

By: Gökmen Göksel

Gökmen Göksel — Fri, 13 Feb 2009 13:00:53 +0000

Yes, I need some information to howto make it :) Actually writing a Comar backend for Solid in our TODO and if we make it now it will be helpful for us.

By: Will Stephenson

Will Stephenson — Fri, 13 Feb 2009 12:43:37 +0000

Oh and another thing, have you written a backend for Solid::Networking so that KDE apps know when they are online when using COMAR? Ping me if you need any info on how to do that.

By: Neil

Neil — Fri, 13 Feb 2009 12:09:25 +0000

Thank you for you’re efforts! This work looks very promising! The Pardus Networkmanager works already great in Pardus 2008.2 ! I’m so looking forward to 2009 with all the KDE4 integration!

Could you please blog more about the plans/progress of the next Pardus releases? It’s IMHO the easiest and best KDE distro right now!

Thanks! Tessekür edderim!

By: Gökmen Göksel

Gökmen Göksel — Fri, 13 Feb 2009 08:41:24 +0000

@Will Nice to see you in here :) I’m very happy now ;) Yes, there is a name conflict :) But as you said it is possible to use COMAR or FD NM as backend.
Actually its just based on profiles a mean as I said before to connect a network you must create a profile, but in COMAR 3.0 there will be different approach like NM in FD. You can find model document for Network.Link in here.
The plasmoid is not use engine in anyway for now, it uses COMAR Net.Link with d-bus and works asynchrously. So, COMAR provide Network Connection you can remove plasmoid anytime. I just made engine for future projects, it uses COMAR too.

But if we make KDE4 NM to use COMAR it will be great :) (And it is hard to write something in this small box, I will be gokmen@#kde-devel )

@iota We will make it but for now COMAR is not provide all of FD. NM features. And for making this plasmoid with COMAR is very easy then you think, we have already invited these in 2007 and used them with KDE3 its just a KDE4 way of Pardus Network Manager Applet .. I’m sad if one sad..

By: iota

iota — Fri, 13 Feb 2009 07:54:23 +0000

So why didn’t you just make a Solid backend for your COMAR Network Manager? This way the other plasmoid could use it, less duplication of efforts. From the sshots and screencast it’s pretty obvious that you’ve unfortunately reinventing the wheel instead of joining efforts with Will and Sebas.

Sad…

By: Will Stephenson

Will Stephenson — Fri, 13 Feb 2009 07:41:38 +0000

Hi Gökmen, this looks great although at first glance you gave me the shock of my life while eating breakfast.

At first I thought we had a naming conflict but I doubt this will be a problem as COMAR based distros will take yours and fd.o (GNOME) NM distros will take mine, the users should never see both applets or engines.

I’m wondering how this ‘profile based’ approach works differently to the ‘connection based’ approach used in Network Management. It would be cool if we could combine the 2 plasmoids, or make the engines replaceable. At the moment we are not using a Plasma::Engine at all though. It needs to happen so we can support ConnMan and wicd, and possibly COMAR if you want. Is there a feature list of COMAR somewhere so I can figure out if there is enough common ground?

Are COMAR clients stateless (Can you remove the plasmoid and keep your network connection up)?

@Robert In Network Management (the KDE 4 widget for fd.o NM) you can add a connection and enter the ESSID of the hidden network.

@Dread I hope you reported that crash.

@Byte You haven’t realised that these applets just show the popup menu have you? There is an icon that can go on a panel or wherever. The new system tray work should include a tray that can contain plasmoids as well as legacy tray icons and have hiding rules for them.

By: Gökmen Göksel

Gökmen Göksel — Fri, 13 Feb 2009 07:33:59 +0000

Thank you for your detailed comment :) Actually I looked Mac OS before making this but our Network Manager is working on profiles (for now) ; before connecting a network you should create a profile and the profile appears in applet and you may connect. But this things will change in Pardus 2009 and there will be hidden profiles to user; like Mac OS you can connect a network without creating a profile.

Bop and Kablo are my ethernet profiles and I know it needs a lot of GUI work ;) Again thank you for your opinions ;)

By: Michael Krog

Michael Krog — Fri, 13 Feb 2009 07:15:59 +0000

WWhile I think we need a better networkmanager and your look really cool, I think the usability lacks.

I can see that ethernet is not connected, but who/what is Bop and Kablo?

It is kind of the same with wireless. The selection needs a seperation from the options.

Another thing I dont really get, but which is general for network managers in Linux, is why ethernet shall “pollute” taskbar dialogs. How often do an ordinary user actually change that? Its is almost always DHCP anyway, whereas wireless is changed a lot more.

Have you tried taking a look at the way its done in Mac OS?

Wireless:
http://helpdesk.its.uiowa.edu/images/wireless/instructions/airport/networkpref.JPG

Ethernet(only via system options):
http://web.mit.edu/swrt/releases/macosx/notes/images/ethernet-3.png

Mobile network:
http://foliovision.com/images/2008/09/huawei-e220-hsdpa-connect.png