GSoC proposal - Network management for PA

[Jan Grulich]

Dne 24.4.2013 17:53, Sebastian Kügler napsal(a):
> Hi Jan,
>
> On Monday, April 22, 2013 20:08:37 Jan Grulich wrote:
>> I would like to join to GSoC and I have my own idea. Since we are
>> working on a new plasma network applet I think it would be great to
>> improve this applet for Plasma active because the current applet is not
>> simply usable. I've already talked about it with Lamarque on the solid
>> sprint but I need also some co-mentor from Plasma active (if somebody
>> like this idea).
>>
>> The idea is:
>> *Network applet for Plasma applet written in plasma2:*
>> 1) Customize our applet for Plasma active and use plasma2
> Or maybe an alternative applet, which shares most of the UI. This should be
> possible with Plasma packages, which can then also be shared with an active
> settings module, or even a KCM. (In the future, it would make sense moving
> both to QML, to be able to share even more code.)
>
>> 2) Write some basic editor in QML instead of using QWidgets and drop
>> support for unnecessary devices and properties
> Yes, that makes sense.
>
>> 3) Maybe some KCM for Plasma active
> As Lamarque pointed out, there's Active Settings. Those are "KCM light done in
> QML". You can basically ship either a pure QML package, or a QML package along
> with a C++ plugin (which is in fact just a QObject subclass). More info here:
>
> http://techbase.kde.org/Development/Tutorials/Plasma/QML/ActiveSettings
>
>> 4) Add support for activities
> Why? What use cases do you have in mind? (I'm not saying it's nonsense, just
> that it does not directly pop up in front of my virtual eye what will happen
> here.)
For example: 1) Home - try to automatically connect to your home wifi
                      2) Work - automatically connect to VPN
                      3) Travel - turn off wifi and mobile broadband or 
active mobile broadband connection

The fact is, that NetworkManager automatically connects to some 
available and configured connection so maybe activities support will be 
useless.
>> 5) ???? if you have any other ideas
> I think getting these pieces right would be wonderful. I'd rather see a
> smaller set of well-working pieces, than a lot of bells and whistles.
>
> One more thing: As you probably know, Plasma2 and Frameworks5 is very much a
> moving target right now. Before you commit to some kind of timeline, have a
> good look at how much work needs to be put into porting dependencies before
> you can actually start on the NM UI. That (and probably most of your other
> work, too) will benefit also the desktop version (as it often happens with
> Plasma).
Could you please tell me more informations about porting to Plasma2 and 
Frameworks5? I can't imagine how long may take porting to Plasma2 a 
Frameworks5.
I've found only [1] and I think that porting to Plasma2 will be easy, 
but I have no idea about porting to Frameworks5.

[1] http://community.kde.org/Plasma/PortingTolibplasma2
<http://community.kde.org/Plasma/PortingTolibplasma2>
> As I said, I could co-mentor you for Plasma, or Active related questions. I've
> written a fair part of the NM UI (still have cut wounds on my arms from
> wrangling NM and QGraphicsWidgets, I can only imagine how fantastic your
> experience must be compared to that ;-)).
>
> Cheers, and good luck with your proposal!

Thanks

-- 
Jan Grulich
Red Hat Czech, s.r.o
jgrulich at redhat.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/active/attachments/20130425/70b2b943/attachment-0001.html>