Is Network Manager Applet Plasmoid and its data-engine going to provide full funtionality and potential of "Network Manager 0.7"???

If by the network manager plasmoid, you mean this one here Then I believe so, not sure however. It would be best to contact one of its developers directly.

bcooksley wrote:If by the network manager plasmoid, you mean this one here Then I believe so, not sure however. It would be best to contact one of its developers directly.

yes!!!
the same....
Does the solid-NM supports "Network Manager 0.7" fully?

Not sure about Solid-NM, However I think the plasmoid uses Network Manager directly, it might use some Solid functionality in some areas though.

bcooksley wrote:Not sure about Solid-NM, However I think the plasmoid uses Network Manager directly, it might use some Solid functionality in some areas though.

Some information on it....
http://vizzzion.org/?blogentry=839

rajputrajat wrote:

bcooksley wrote:Not sure about Solid-NM, However I think the plasmoid uses Network Manager directly, it might use some Solid functionality in some areas though.

Some information on it....
http://vizzzion.org/?blogentry=839

Hi
did you manage to build it from svn? And if so, would you tell me how?
cmake works but typing "make" doesn't do anything and does not show messages either.
Thanks, david

dcrabs wrote:

rajputrajat wrote:

bcooksley wrote:Not sure about Solid-NM, However I think the plasmoid uses Network Manager directly, it might use some Solid functionality in some areas though.

Some information on it....
http://vizzzion.org/?blogentry=839

Hi
did you manage to build it from svn? And if so, would you tell me how?
cmake works but typing "make" doesn't do anything and does not show messages either.
Thanks, david

I've not tried yet...
but will try n tell.....

OK, tried it today.

Getting to build was quite easy. (I think there were a few smaller probs).

But, well it is not really working. First I had to get arround the policy things in dbus (does't anybody know that is supposed to be done? I removed the restrictions for all users on the NetworkManger dbus node in the dbus config file.., seems not the right way).

But even after that it won't work. Doesn't show any network. From the output it seems to call two no existed DBus method (one obviously a typo and the other not sure..)

But well that was somehow expected still experimental. So I tried NM with the gnome nm-applet.

What really bugs me is: I removed networmanager about 1 year ago because it had more problems and connection issues every day. Went to "wicd" which just works most of the times.

So after all that time, after the many changes in 0.7 and a lot of big distributions using it as the default NM (though most likely not 0.7) it still seems to be "broken". It is impossible to connect to my Wifi (normal WPA2 with PSK (password)). Wicd can without a problem. My E71 has no problem with it, my N810 neither.. NM still unusable, so I can stop waiting für a KDE applet and stick with wicd?

I agree. Knetworkmanager still lags behind a LOT. I want a good networkmanager that allows me to:
- connect to any wireless network
- connect to any wired network
- switches transparently between networks
- reconnects automatically after suspend / resume
- offers VPN connections (also PPTP!!)
- stores profiles to select DHCP / fixed IP, DNS settings

Knetworkmanager, last time I checked in 3.5.10 has a looong way to go. Wicd is almost perfect, it just does not offer VPN and has an issue when you use dhclient.

The Gnome networkmanager in Ubuntu, as much as I hate to say it, is a lot better, so there is some catching up to do....

The reason the Gnome networkmanager is much better is because it is written and maintained by the guys who write NetworkManager itself. Therefore it usually would probably always work with the latest and greatest.

KNetworkManager due to being based on Qt3, and not exactly designed very well according to the developers of the new Plasmoid is being placed into maintenance mode and will probably become unmaintained once the Plasmoid matures.

I myself use Wicd as well and it works great ( over NetworkManager which would sit there stunned, doing nothing )

DanielW wrote:OK, tried it today.

Getting to build was quite easy. (I think there were a few smaller probs).

But, well it is not really working. First I had to get arround the policy things in dbus (does't anybody know that is supposed to be done? I removed the restrictions for all users on the NetworkManger dbus node in the dbus config file.., seems not the right way).

[...]

Hi
I have the problem that make doesn't do anything. I get a new prompt that's it, no error message. There is makefile though.
Could you please tell me what you did? I feel somewhat stupid right now.
david

dcrabs wrote:Hi
I have the problem that make doesn't do anything. I get a new prompt that's it, no error message. There is makefile though.
Could you please tell me what you did? I feel somewhat stupid right now.
david

What was the output of cmake?

Basicly you build it as every other cmake/kde thing. First you need KDE 4.2 from trunk (beta 2 may be enough (not sure))

Then you get the complete kde-base/plasma module from playground with svn.

Create a new directory where you build it. In that directy you call cmake (with the usual params) pointing to the source dir (source of the complete kde-base/plasma)

And after that you can go down to the network manager plasmoid build dir. Where a make should build it, make install install it.

If you get any error messages when doing this paste them here or in some paste bin.


And btw:

I got the networkmanager applet to work now. I used to have networkmanger 0.6 on my system and so had the solid backend for both on my system. In the solid settings in the systemsettings I had to switch from networkmanger 0.6 to 0.7 backend.

But as expected: It can not connect to my wifi, but ethernet works. Similar to the problems with the gnome network manager applet. So I think it is a networkmanger issue not the applet. (or my setup of networkmanger, dbus/hal)

DanielW wrote:

dcrabs wrote:Hi
I have the problem that make doesn't do anything. I get a new prompt that's it, no error message. There is makefile though.
Could you please tell me what you did? I feel somewhat stupid right now.
david

What was the output of cmake?

Basicly you build it as every other cmake/kde thing. First you need KDE 4.2 from trunk (beta 2 may be enough (not sure))

Then you get the complete kde-base/plasma module from playground with svn.

Create a new directory where you build it. In that directy you call cmake (with the usual params) pointing to the source dir (source of the complete kde-base/plasma)

And after that you can go down to the network manager plasmoid build dir. Where a make should build it, make install install it.

If you get any error messages when doing this paste them here or in some paste bin.


And btw:

[...]

Well that is, I think, exactly what I did.
I checked out plasma with:

Code: Select all

svn co -N svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma

as one of the developers pointed out. Then in the new directory:

Code: Select all

svn up networkmanager

Than I had to edit CMakeLists.txt so that it didn't check for other plasmoids and started cmake. The output is:

Code: Select all

david@farnsworth ~/build/kde4/plasma % make
-- Found Qt-Version 4.4.3 (using /usr/bin/qmake)
-- Found X11: /usr/lib/libX11.so               
-- Phonon Version: 4.2.80                       
-- Found KDE 4.2 include dir: /usr/include     
-- Found KDE 4.2 library dir: /usr/lib         
-- Found the KDE4 kconfig_compiler preprocessor: /usr/bin/kconfig_compiler
-- Found automoc4: /usr/bin/automoc4                                     
-- Ruby found: /usr/lib/libruby.so                                       
-- checking for one of the modules 'NetworkManager'                       
-- Configuring done                                                       
-- Generating done                                                       
-- Build files have been written to: /home/david/build/kde4/plasma

Which looks OK for me. The make in the networkmanager directory does as I said before nothing. It is as if the Makefile were empty, which it isn't.
I have no clue anymore.
david

try

make help in that networkmanger applet build dir:

I get:

Code: Select all

[kde-devel@newlapi networkmanager]$ make help
makeobj[0]: Entering directory `/home/kde-devel/ownbuild/build/plasma/applets/networkmanager'
The following are some of the valid targets for this Makefile:
... all (the default if no target is provided)
... clean
... depend
... edit_cache
... install
... install/local
... install/strip
... list_install_components
... rebuild_cache
... test
... uninstall
... plasma_applet_networkmanager
... knmstorage
... knmui
... knmdbus
... testconfigxml
... kcm_knetworkmanager
... knetworkmanager_configshell
... kded_knetworkmanager
... knetworkmanager4_openvpnui
... knetworkmanager4_vpncui
makeobj[0]: Leaving directory `/home/kde-devel/ownbuild/build/plasma/applets/networkmanager'


That looks different here

Code: Select all

david@farnsworth ~/build/kde4/plasma/applets/networkmanager % make help
The following are some of the valid targets for this Makefile:
... all (the default if no target is provided)
... clean
... depend
... edit_cache
... rebuild_cache
... test

I guess I would need make install.