-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Make Tasks a DAV client, close #280 #291
Conversation
308236c
to
d268392
Compare
@georgehrke @raghunayyar I would like to use your implementation of the client side calendar service and maybe other files from the calendar-rework if its ok with you. |
Sure, it's free software, go ahead :) |
Can someone tell me if it is possible to also get the id of a calendar? If yes, how has the request body to look like? I tried something like this
but this does not return an id. @DeepDiver1975 @georgehrke maybe? |
|
Yes, that's true. But I need something to show in the address bar when a user opens a calendar, so the page history works correctly. The database ID would have been the easiest solution. |
The display name is supposed to be unique. Although I'm not sure this if this is enforced at the moment. |
The displayname is currently not enforced to be unique and it won't be for different users. For the moment I will just count upwards, but this might result in a usability problem when a user bookmarks the link to a certain calendar. I will have to think of a better solution later on. |
The displayname is indeed not unique. But the Uri is. |
The Uri also seems to only be unique for one user. But when User1 shares a calendar with the (for him) unique Uri 'test' with User2 which also has a calendar with this Uri, User2 has two calendars with the same Uri. Hence, only the principaluri is really unique, or am I wrong? |
The shared Uri will be test_shared_by_user1 |
Ah, alright, thank you.
does not return any uri, but gives
instead. |
you have to extract it |
Thank you Raimund for the hard work! Can't wait to use the new version! 👍 |
\o/ |
With 8808e77 we only load pending tasks. But this also means completed tasks are not loaded at all at the moment. @DeepDiver1975 Is there a possibility to load the five newest completed tasks per list? And maybe also a query to get the total number of completed tasks at the server? |
CalDAV and carddav queries have no understanding of aggregation functions - we have been looking for this for Contacts already. |
Hm, can someone give me a hint on how to limit and order the result set? My naive try to limit the result set to five didn't succeed and I don't seem to be able to figure it out by myself: <c:calendar-query xmlns:c="urn:ietf:params:xml:ns:caldav" xmlns:d="DAV:" xmlns:a="http://apple.com/ns/ical/" xmlns:o="http://owncloud.org/ns">
<d:prop>
<d:getetag/>
<c:calendar-data/>
</d:prop>
<d:limit>
<d:nresults>5</d:nresults>
</d:limit>
<c:filter>
<c:comp-filter name="VCALENDAR">
<c:comp-filter name="VTODO">
<c:prop-filter name="COMPLETED">
<c:is-not-defined/>
</c:prop-filter>
</c:comp-filter>
</c:comp-filter>
</c:filter>
</c:calendar-query> |
I don't think that CalDAV reports support limit and offset. |
I thought this was possible because of this: https://tools.ietf.org/html/rfc5323#section-5.17 Did I misunderstand it? |
The webdav search extension has nothing to do with CalDAV and CardDAV reports. |
indeed - only carddav query supports that ... my bad - sorry |
will you release the app soon and add the features afterwards, or will you just continue to develop in the master branch and release the app when everything is done? |
As it was requested by several users, I will release a version to the appstore soon and indicate the yet missing features. So it is possible to install via the appstore again and everybody can decide whether or not he is willing to update. |
awesome! 👍 |
Thanks a lot @raimund-schluessler |
Great work @raimund-schluessler. 🍻 at ownCloudConf! |
We want to get rid of the calendar dependency and use the CalDAV server build-in in oC core 9.x.
In order to hopefully make the development easier the same DAV library as in core and calendar will be used. No more server side CalDAV stuff in the app itself.
Todos:
_Calendars_
_Tasks_
_Various_
./occ app:check-code tasks
_Search_