Hey Maurus, On Tuesday 16 March 2010 01:30:36 maurus rohrer wrote: > > In that case, best is probably to add it to SVN. I understand you don't > > have a > > KDE SVN account, so if you send me the files, I can add them for you. If > > you > > plan to contribute more regularly, we'll hook you up with your own > > account. OK? > > > > :) > > I will send you the files as soon I have them tested, and all functions > build in, will be soon.
Sounds good :) It doesn't need to be perfect at first, testing will reveal errors anyway, so as soon as you think it makes sense to get some people to test it, it should probably go in. (No risk of regressions anyway, since it's a new component.) > cool, can't wait to get a account :) but I first have look closer in to the > code, before I mess the hole repository up :) We got sticks and stones to cover for that :-) > > Help on those issues is definitely welcome. It just needs some > > coordination (which is why you wrote this email of course, so that's > > great :)). If you could > > have a look at the connection secrets issue, that would be great. > > I had some time to look at it. It seams that there is a way to set the > storage type over KNetworkManagerServicePrefs::SecretStorageMode, but it > seams to be the setting for the hole networkmanager envioroment? Or is > there a way to set this enum for each connection? I thought about adding > a variable to the vpnsettings, and trigger the secret widget in the > connectionsecretsjob. Why would you store the information for different connections in different ways? -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ kde-networkmanager mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-networkmanager
