[opensuse-kde3] Ideas for new NetworkManager frontend
Hello KDE3 users, I started the development for new NetworkManager frontend, but i'm not sure how to make it to be powerful and user-friendly at same time. Basically, it will have 3 components: 1) a secret agent running as KDE service 2) a connection manager, integrated in KControl 3) a kicker applet Any ideas will be apreciated (screenshots or .ui files created with Qt3 designer are preffered). Thanks. PS I attached a screenshot with current done work (the list of connections for ethernet and wireless). PPS Do not confuse "connection" with "access point" or "ethernet device". A physical device can have more than one connection (for example "eth0 work" and "eth0 home"). -- Serghei
On Friday 16 November 2012 02:17:03 Serghei Amelian wrote:
I started the development for new NetworkManager frontend, but i'm not sure how to make it to be powerful and user-friendly at same time.
Basically, it will have 3 components:
1) a secret agent running as KDE service 2) a connection manager, integrated in KControl 3) a kicker applet
Any ideas will be apreciated (screenshots or .ui files created with Qt3 designer are preffered).
Thanks.
PS I attached a screenshot with current done work (the list of connections for ethernet and wireless).
PPS Do not confuse "connection" with "access point" or "ethernet device". A physical device can have more than one connection (for example "eth0 work" and "eth0 home").
Thank you very much! I suggest a tray application rather than kicker applet. Also I wonder why the current knetworkmanager cannot be used at least for interface. I think it has quite intuitive interface. Unfortunately it does not connect to the wi-fi networks under 12.2 although it lists the networks well. Possibly it only needs minor corrections. Also it requires hal... -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Friday 16 November 2012 02:24:37 Ilya Chernykh wrote: [...]
Thank you very much!
I suggest a tray application rather than kicker applet.
Why a tray application?
Also I wonder why the current knetworkmanager cannot be used at least for interface. I think it has quite intuitive interface.
Unfortunately it does not connect to the wi-fi networks under 12.2 although it lists the networks well. Possibly it only needs minor corrections. Also it requires hal...
I don't like very much the interface of old knetworkmanager. However, because developing of new knetworkmanager will take some time, I will try to adapt it to be compatibile with NM 0.9. -- Serghei -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Friday 16 November 2012 12:23:32 Serghei Amelian wrote:
I suggest a tray application rather than kicker applet.
Why a tray application?
I do not like the knetworkmanager plasmoid in KDE4. - I think a panel applet will take unnecessary place from the panel, take excess memory. - Also a tray icon can be configured to be hidden, not shown while the applet is always visible. - Also the applet may not be well adapted to various kicker configurations and placement - A buggy applet may cause a kicker crash (unlike a tray app) - In a case of any kicker crash or restart, the applet also will be killed - Some people may not use kicker at all. There are multiple KDE3 docks such as ksmoothdock and kooldock. Also there is a separate application ktray that allows to display tray content without any panel.
Also I wonder why the current knetworkmanager cannot be used at least for interface. I think it has quite intuitive interface.
Unfortunately it does not connect to the wi-fi networks under 12.2 although it lists the networks well. Possibly it only needs minor corrections. Also it requires hal...
I don't like very much the interface of old knetworkmanager. However, because developing of new knetworkmanager will take some time, I will try to adapt it to be compatibile with NM 0.9.
Would be wonderful. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Friday 16 November 2012 12:55:50 Ilya Chernykh wrote:
I suggest a tray application rather than kicker applet.
Why a tray application?
I do not like the knetworkmanager plasmoid in KDE4.
- I think a panel applet will take unnecessary place from the panel, take excess memory.
- Also a tray icon can be configured to be hidden, not shown while the applet is always visible.
- Also the applet may not be well adapted to various kicker configurations and placement
- A buggy applet may cause a kicker crash (unlike a tray app)
- In a case of any kicker crash or restart, the applet also will be killed
- Some people may not use kicker at all. There are multiple KDE3 docks such as ksmoothdock and kooldock. Also there is a separate application ktray that allows to display tray content without any panel.
As an example, ksmoothdock: http://storage9.static.itmages.ru/i/12/0208/h_1328714170_3730451_27d857649c.... Kicker is not the only way to work with KDE3. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Friday 16 November 2012 10:55:50 Ilya Chernykh wrote: [...]
Unfortunately it does not connect to the wi-fi networks under 12.2 although it lists the networks well. Possibly it only needs minor corrections. Also it requires hal...
I don't like very much the interface of old knetworkmanager. However, because developing of new knetworkmanager will take some time, I will try to adapt it to be compatibile with NM 0.9.
Would be wonderful.
Well, updating the old KNM to NM 0.9 seems a big PITA :) Very complicate design, almost incomprehensible. I'm still trying, anyway. -- Serghei -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Tuesday 20 November 2012 22:03:28 Serghei Amelian wrote:
Unfortunately it does not connect to the wi-fi networks under 12.2 although it lists the networks well. Possibly it only needs minor corrections. Also it requires hal...
I don't like very much the interface of old knetworkmanager. However, because developing of new knetworkmanager will take some time, I will try to adapt it to be compatibile with NM 0.9.
Would be wonderful.
Well, updating the old KNM to NM 0.9 seems a big PITA :) Very complicate design, almost incomprehensible. I'm still trying, anyway.
The basic patch that makes it built is already in openSUSE: https://build.opensuse.org/package/view_file?expand=1&file=nm-0_9-compatibility.patch&package=knetworkmanager-kde3&project=KDE%3AKDE3 -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Tuesday 20 November 2012 20:17:05 Ilya Chernykh wrote:
On Tuesday 20 November 2012 22:03:28 Serghei Amelian wrote:
Unfortunately it does not connect to the wi-fi networks under 12.2 although it lists the networks well. Possibly it only needs minor corrections. Also it requires hal...
I don't like very much the interface of old knetworkmanager. However, because developing of new knetworkmanager will take some time, I will try to adapt it to be compatibile with NM 0.9.
Would be wonderful.
Well, updating the old KNM to NM 0.9 seems a big PITA :) Very complicate design, almost incomprehensible. I'm still trying, anyway.
The basic patch that makes it built is already in openSUSE:
https://build.opensuse.org/package/view_file?expand=1&file=nm-0_9-compatibi lity.patch&package=knetworkmanager-kde3&project=KDE%3AKDE3
Well, I made it buildable already (and even more, like to use new introspection files). The problem is to understand how it's working, to make necessary corrections. -- Serghei -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Tuesday 20 Nov 2012 20:30:48 Serghei Amelian wrote:
On Tuesday 20 November 2012 20:17:05 Ilya Chernykh wrote:
On Tuesday 20 November 2012 22:03:28 Serghei Amelian wrote:
Unfortunately it does not connect to the wi-fi networks under 12.2 although it lists the networks well. Possibly it only needs minor corrections. Also it requires hal...
I don't like very much the interface of old knetworkmanager. However, because developing of new knetworkmanager will take some time, I will try to adapt it to be compatibile with NM 0.9.
Would be wonderful.
Well, updating the old KNM to NM 0.9 seems a big PITA :) Very complicate design, almost incomprehensible. I'm still trying, anyway.
The basic patch that makes it built is already in openSUSE:
https://build.opensuse.org/package/view_file?expand=1&file=nm-0_9-compatib i
lity.patch&package=knetworkmanager-kde3&project=KDE%3AKDE3
Well, I made it buildable already (and even more, like to use new introspection files). The problem is to understand how it's working, to make necessary corrections.
This is why I did a complete rewrite of it for KDE 4. It was written by a kernel C hacker, I just tried to make it work, not leak memory and be relatively sane. The code is unmaintainable. If I were you I'd scrap any code derived from the NM 0.7/0.8 based KDE3 knetworkmanager and backport the dbus code (IIRC, the KDE 3 dbus bindings are copied from Qt 4's so this should be simple) and the config dialogs from KDE 4 knetworkmanager. There are no big differences to KDE 3 programming style there. Then I would write a new tray app as frontend. You don't need a connection settings service with NM 0.9 as NM itself stores the connections, and the tray app should intercept receive any local secret request signals and return those from KWallet. Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Tuesday 04 December 2012 18:08:47 Will Stephenson wrote: [...]
Well, I made it buildable already (and even more, like to use new introspection files). The problem is to understand how it's working, to make necessary corrections.
This is why I did a complete rewrite of it for KDE 4. It was written by a kernel C hacker, I just tried to make it work, not leak memory and be relatively sane. The code is unmaintainable.
If I were you I'd scrap any code derived from the NM 0.7/0.8 based KDE3 knetworkmanager and backport the dbus code (IIRC, the KDE 3 dbus bindings are copied from Qt 4's so this should be simple) and the config dialogs from KDE 4 knetworkmanager. There are no big differences to KDE 3 programming style there.
Qt3 DBUS binding is based on older implementation of Qt4 DBUS, and it's pretty buggy. In any case, I decided to avoid direct dbus calls and to use nm-utils and nm-glib. With glib mainloop patch for Qt3 the integration is pretty nice and simple.
Then I would write a new tray app as frontend. You don't need a connection settings service with NM 0.9 as NM itself stores the connections, and the tray app should intercept receive any local secret request signals and return those from KWallet.
Yes, I know. Actually I want to create a KDED service, to act as secret agent, the tray applet should be used just for activating/deactivating connections.
Will
[...] Now i'm working on the connection editor, implemented as kcm module, see the attachment. -- Serghei
Check there: http://sourceforge.net/p/kde3/_list/git
Thanks, but seems not that active for now... -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Serghei, kdegraphics3 is now failing in Factory due to new gphoto2. https://bugzilla.novell.com/show_bug.cgi?id=789162 The API changed... Several KDE3 packages are failing for the same cause. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Friday 16 November 2012 11:44:43 Ilya Chernykh wrote:
Serghei, kdegraphics3 is now failing in Factory due to new gphoto2.
https://bugzilla.novell.com/show_bug.cgi?id=789162
The API changed... Several KDE3 packages are failing for the same cause.
Please give me a build log. I just built kdegraphics on Fedora 17 with cmake and seems fine (libgphoto2-2.4.14). -- Serghei -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Friday 16 November 2012 14:02:28 Serghei Amelian wrote:
Serghei, kdegraphics3 is now failing in Factory due to new gphoto2.
https://bugzilla.novell.com/show_bug.cgi?id=789162
The API changed... Several KDE3 packages are failing for the same cause.
Please give me a build log. I just built kdegraphics on Fedora 17 with cmake and seems fine (libgphoto2-2.4.14).
Here it is: https://build.opensuse.org/package/rawlog?arch=i586&package=kdegraphics3&project=KDE%3AKDE3&repository=openSUSE_Factory -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Friday 16 November 2012 12:22:06 Ilya Chernykh wrote:
On Friday 16 November 2012 14:02:28 Serghei Amelian wrote:
Serghei, kdegraphics3 is now failing in Factory due to new gphoto2.
https://bugzilla.novell.com/show_bug.cgi?id=789162
The API changed... Several KDE3 packages are failing for the same cause.
Please give me a build log. I just built kdegraphics on Fedora 17 with cmake and seems fine (libgphoto2-2.4.14).
Here it is:
https://build.opensuse.org/package/rawlog?arch=i586&package=kdegraphics3&pr oject=KDE%3AKDE3&repository=openSUSE_Factory
At this moment I can't provide a fix, because upgrading to libgphoto-2.5 broke a large part of my system. Maybe when Fedora 18 will be released (if it come with libgphoto-2.5). -- Serghei -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Friday 16 November 2012 14:02:28 Serghei Amelian wrote:
https://bugzilla.novell.com/show_bug.cgi?id=789162
The API changed... Several KDE3 packages are failing for the same cause.
Please give me a build log. I just built kdegraphics on Fedora 17 with cmake and seems fine (libgphoto2-2.4.14).
Factory has libgphoto-2.5 -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Thursday 15 November 2012 12:17:03 pm Serghei Amelian wrote:
Hello KDE3 users,
I started the development for new NetworkManager frontend, but i'm not sure how to make it to be powerful and user-friendly at same time.
Basically, it will have 3 components:
1) a secret agent running as KDE service 2) a connection manager, integrated in KControl 3) a kicker applet
Any ideas will be apreciated (screenshots or .ui files created with Qt3 designer are preffered).
Thanks.
PS I attached a screenshot with current done work (the list of connections for ethernet and wireless).
PPS Do not confuse "connection" with "access point" or "ethernet device". A physical device can have more than one connection (for example "eth0 work" and "eth0 home").
I have never used nm. A couple of years ago i found out about wicd and it simply works. The only negative items on it are that sometimes permissions need to be manually set at the first install, also the passwords can be seen when the mouse pointer is over the pwd box. Perhaps a review of the gui and features can be beneficial. as an example, really nice "must have" is the automatic encryption detection. good luck, d. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
participants (4)
-
Ilya Chernykh -
kanenas＠hawaii.rr.com -
Serghei Amelian -
Will Stephenson