KNetworkManager

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

KNetworkManager
by Leo S on Thursday 01/May/2008, @14:58

Awesome to hear about the KDE4 port of KNetworkManager. It's pretty much the last KDE3 app that I depend on all the time. Konversation is the other..

Thanks for the digest Danny!

Related Links

·   Articles on Developer
·   Also by Leo S
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: KNetworkManager
by okparanoid on Thursday 01/May/2008, @15:28

About Knetworkmanager

i have seen in the feature list that somebody work on a networkmanager plasmoid
an other people on a network-manager backend for solid.

What is the difference with this 3 apps.

Is the idea to have an api provided by solid, usable by knetworkmanager or either the plasmoid (does not will make a lot of "bricks") ?

Or something else ?

Thanks !!

[ Reply To This | View ]

Re: KNetworkManager
by Emil Sedgh on Thursday 01/May/2008, @23:08

Hi
yeah, i think its like:

KNetworkManager
/
/
NetworkManager <---> Solid
\
\
Network Manager Plasmoid

[ Reply To This | View ]

Re: KNetworkManager
by Emil Sedgh on Thursday 01/May/2008, @23:10

oh! it ignored all whitespaces...
sorry for messing up.

[ Reply To This | View ]

Re: KNetworkManager
by Erunno on Friday 02/May/2008, @00:00

Solid is the hardware abstraction layer for KDE and is meant to ease the development of cross-plattform KDE application (together with other KDE frameworks like Phonon and, of course, Qt).
It is planned that Solid will get a NetworkManager Backend which will handle all networking functions transparently so developers won't have to work with NetworkManager directly anymore but can rely on Solid to do it via different backends on different platforms.

My uneducated guess about KNetworkMangager:

It will work directly on top of NetworkManager. KNetworkManager is developed by openSUSE guys and since they'll release openSUSE 11.0 with a heavily modified KDE 4.0 they aren't able to use (and develop against) Solid as long as the backend is not in place.

About the plasmoid:

The plasmoid *might* make use of Solid as both backend and plasmoid will probably be released with KDE 4.1 but I truely don't. One of the developers would have to comment on this.

[ Reply To This | View ]

Re: KNetworkManager
by Vide on Friday 02/May/2008, @01:47

Don't want to flame here but I really don't understand Novell and Opensuse folk here... why Danny Kukawa (knetworkmanager maintainer, hal developer) simply ignores Solid? KNM, as a KDE4 app, should only rely on Solid, and if something is missing in Solid to make this possible, development should be driven towards this goal. As far as I can tell reading Danny's blog, KDE news etc etc, this is not happening right now. Am I wrong? (I hope I am)

[ Reply To This | View ]

Re: KNetworkManager
by jos poortvliet on Friday 02/May/2008, @03:06

Maybe it's just an issue of time... They might get this into solid for KDE 4.1 or 4.2?

[ Reply To This | View ]

Re: KNetworkManager
by Segedunum on Friday 02/May/2008, @06:56

"why Danny Kukawa (knetworkmanager maintainer, hal developer) simply ignores Solid?"

I don't think he is. It's probably just a case of Solid being in a working state where KNM can use that instead of NM directly.

[ Reply To This | View ]

Re: KNetworkManager
by anon on Sunday 04/May/2008, @23:56

that has been answered. Solid is not at a point where OpenSUSE can use it for their upcoming release

[ Reply To This | View ]

Re: KNetworkManager
by Vide on Tuesday 06/May/2008, @04:01

So why OpenSuse doesn't put some of its employees working on Solid? (well, they could have started months ago, actually). IMO, Solid is something distro should just fall in love with, cause it can make system management integration much simpler.

[ Reply To This | View ]

Re: KNetworkManager
by she on Thursday 08/May/2008, @07:53

I agree, but seriously since Novell took over there was even more coding support for Novell-specific stuff. Fragmenting a community even more.

With KDE this would be so much better, because KDE is distro-agnostic - if it works on KDE, it will work on distros (with a little bit of tweaking sometimes)

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"My hobbies include, well, coding... and uhm... that's about it." -- Daniel M. Duley
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.