[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-07-15 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 Stefan changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit|

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-06-28 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #15 from Stefan --- Diff added to phabricator -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-06-25 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #14 from Stefan --- And adding works also now :) Believe never the documentation ;) -- You are receiving this mail because: You are the assignee for the bug. ___

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-06-25 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #13 from Stefan --- Reading, deleting and modifying works now. Adding is still a problem. A reason could be the date format. -- You are receiving this mail because: You are the assignee for the bug.

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-06-23 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #12 from Stefan --- Today a was working on the write access. The deletion of an note works now, but the resource blocks after this operation and is then unusable. Adding and modifying don't work at the moment. The note

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-06-22 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #11 from Stefan --- The resource provides a configuration dialog now -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-06-21 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #10 from Stefan --- The resource provides read-only access now. The next steps are a network error handling and a configuration dialog. -- You are receiving this mail because: You are the assignee for the bug.

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-06-21 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #9 from Stefan --- I get now also now content and the remote revision. I think that I had not set everything correctly from the original item, so that the result wasn't recognized properly. I now doing this: resultItem

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-06-20 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #8 from Stefan --- A little update from yesterday: Getting all items with correct id works now. I have also now a Job class for collections for getting the global sync revision. This also seems to be working now. I'm

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-06-19 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #7 from Stefan --- The OAuth authentication works now. Also getting access to seems to be working (no QNetwork-Reply error). So the problem now seems to be parsing the JSON data. I think I use QJsonDocument not

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-06-18 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #6 from Stefan --- I hope I have the right idea now: KMime::Message::Ptr akonadiNote = KMime::Message::Ptr(new KMime::Message); akonadiNote->subject(true)->fromUnicodeString( jsonNote["title"].toString(), "utf-8" );

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-06-18 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #5 from Stefan --- A little status update: For OAuth I use now the suggested o2. Because of cmake it was a little bit difficult getting it working. I want to use the following KJob classes: - TomboyJobBase: it

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-06-01 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #4 from Stefan --- Link to the repository: https://github.com/staeglis/tomboynotes -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-06-01 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #3 from Stefan --- Hello, thank you for your comment. QOAuth is no option anymore because it's not working properly. Using kQOAuth could be also problematic because it support only HTTP POST and not HTTP PUT. The API

[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource

2016-05-28 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #1 from Stefan --- I need also a library that implements OAuth 1.0. For now I have two candidates: QOAuth: https://github.com/ayoy/qoauth kQOAuth: https://github.com/kypeli/kQOAuth I think the better candidate is

[kleopatra] [Bug 363148] Deselecting Signing check box in Advanced Settings - Certificate Usage results in General Error in Kleopatra

2016-05-17 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363148 Stefan changed: What|Removed |Added CC||luke1...@gmx.de --- Comment #1 from

[kleopatra] [Bug 363154] New: Cannot create certificate with @ in the name field.

2016-05-16 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363154 Bug ID: 363154 Summary: Cannot create certificate with @ in the name field. Product: kleopatra Version: 2.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED

[kleopatra] [Bug 362640] cryptic error message, when using long password to export secret key

2016-05-03 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362640 --- Comment #1 from Stefan --- On a related note: Regardless of the error, the output file is created (it's empty however, in the error case). It would be better, if the file would either not be created, if there was an error, or that

[kleopatra] [Bug 362640] cryptic error message, when using long password to export secret key

2016-05-03 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362640 Stefan changed: What|Removed |Added CC||luke1...@gmx.de -- You are

[kleopatra] [Bug 362640] New: cryptic error message, when using long password to export secret key

2016-05-03 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362640 Bug ID: 362640 Summary: cryptic error message, when using long password to export secret key Product: kleopatra Version: 2.2.0 Platform: Other OS: MS Windows

[kmail2] [Bug 361503] New: Spam filter (spamassasin) does not work

2016-04-07 Thread Stefan via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361503 Bug ID: 361503 Summary: Spam filter (spamassasin) does not work Product: kmail2 Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: