(BE::SHELL) Networkmanager or something in the systray
Status: Beta
Brought to you by:
baghira-style
Menu
▾
▴
I agree with this request. Currently, the systray is very limited. It hardly has anything. clipboard, knemo, full application list. None of them. You might want to enhance the systray Thomas. Just like the way it was in old baghira days.
Also, missing is the Menu (which unfortunately pulls in Plasma).
And how do we specify a keyboard handler for the runner. Alt + F2 doesn't work.
erheemm - as mentioned on the installation page:
"kcmshell4 kded", deactivate "status notifier daemon"
I never implemented that protocol (i probably should, but didn't care that much about the systray either)
reg. the runner: "kcmshell4 keys", select BE::Shell and assign a shortcut to it.
There's also a dbus interface (in general, try "qdbus org.kde.be.shell")
PS: can you still not open tickets?
I followed the wiki completely and did do "kcmshell4 kded", deactivate "status notifier daemon" but it does not bring in networkmanger (which I know is a plasma widget) but even if we could use wicd or something to be able to switch wireless access points or networks would be nice.
I don't have a problem with a menu I assigned it to a key already and I didn't try opening a ticket sorry
Sorry, I was referring to Ritesh regarding the systray and the menu.
Regarding networkmanager: I was under the impression it came with a regular systray icon (i use netcfg, so i actually can't say) but it should neither be too hard to write a frontend for the networkmanager daemon (similar to what i use here, but netcfg now also has some sort of python systray GUI)
I'd however have to take a look at networkmanager but it provides a cli and that means it should be easy to invoke ("biggest" hinder maybe the demand of dynamic menus, ie. menus that are (re)created from a (bash) script when triggered (and luckily i wanted to write that anyway)
Ah no problem my friend ;-)
Hmm....you must be using arch then as well huh? I used to use netcfg but since networkmanger or even wicd they are just a little easier to just click on and away you go.
I just looked at AUR and there is a netcfg-tray-git but it's out of date...I know I could compile it myself but if it wouldn't be to much trouble for you to write a frontend that would be awesome!!
Thank you Thomas ;-)
the systray thing and gui wifi-select replacement is meanwhile part of netcfg (former netcfg2)
there's no need to fetch stuff from yaourt
Update:
a) networkmanager has a systray applet - with a bunch of gnome deps :-(
b) networkmanager also has nmcli, first look is very promising - should not be hard to invoke it
c) nmcli is broken in current arch version but fixed upstream ("nmcli con" just yells an error)
d) once that's fixed i shall become the first demo of "how to create a button applet"
Yeah I seen that networkmanger has a bunch of gnome deps. I tried nmcli a while back but since kde had the widget I just used that.
I use to use wicd when I first setup arch on a system especially when all I had access to was wireless. wicd also has a cli to it to that I think is better than networkmanager but that's just me :-)
Thanks for looking into it ;-)
You got one shot free, ie. i'll write one demo network manager ;-)
So which do you prefer?
Don't worry about he cli, telling me which usually works better for you is enough.
I can't judge between networkmanager and wicd, but netcfg is too arch specific. Plus i'll likely share the button for it somewhen anyway.
LOL!! well alright better make it for networkmanager as that is what is used the most I guess ;-)
Thanks again Thomas :-D
:-(
I broke my promise.
Networkmanager is as of now still not updated and without nmcli, the entire thing becomes really nasty (one can operate on dbus directly to select networks - that's trivial - but creating them is rocket science ...
So I've added demo scripts for netcfg (and a GUI version of wifi-select) now and will "port" them to networkmanager once that thing gets updated.
Sorry =(
It's not your fault, would wicd be easier (of course I think most of the popular distros use networkmanager I believe.) I do appreciate all that you have done BE:SHELL is so awesome!! I'm loving how configurable it is ;-)
Is there a qt/kde network manager without all the gnome dependencies?
wicd-cli is as good (or worthless) as nmcli - connecting a pre-configured network is easy with both, but not configure - wicd-cli seems to have the very same defect (but seems profile based, so there's a chance one can just write them as well)
Looking at the dependencies and package size networkmanager is more bloat, but both lack the charming simplicity of netcfg.
To make that clear: if you just want to be able to scan for networks and select one, pass the key (store it) and be in - that works (i've "ported" wifi-select to kdialog, so it provides a shell free GUI ;-)
Hello Thomas,
Any update on having this? Thanks
For some reason I can't add a reply here so I will do it here.
Thomas I haven't tried networkmanager do you mean it should work now?
Last edit: CraazyT 2012-12-05
Since systray support should be improved - is this still an open issue?