| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Entries on Shared Drives, or Shared with me are not always editable.
Let's add gdata_documents_entry_can_edit to allow GVfsBackendGoogle to
set file permissions accordingly. It would be nice to make also canDelete,
canRename and canListChildren available, but it would require libgdata
port to Drive API v3 unfortunatelly.
Relates: https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/114
|
|
|
|
|
|
|
|
| |
Let's make available the SharedWithMeDate property to make implementation
of the Shared with me folder for GVfsBackendGoogle easier.
Relates: https://gitlab.gnome.org/GNOME/gvfs/-/issues/444
Relates: https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/114
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It seems that the existing documents APIs works nicely with the files
on Shared Drives (formerly Team Drives), although it is possible that
some small changes will be needed to handle differences:
https://developers.google.com/drive/api/v2/shared-drives-diffs
However, the main problem is that there is no way currently to get the
list of Shared Drives IDs and their names. Let's add new APIs for it
which will be consequently used by GVfs.
Relates: https://gitlab.gnome.org/GNOME/gvfs/-/issues/377
Fixes: https://gitlab.gnome.org/GNOME/libgdata/-/issues/25
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Done using:
```
codespell \
--builtin clear,rare,usage \
--skip './po/*' --skip './help/*/*.po' --skip './.git/*' --skip './NEWS*' \
--write-changes .
```
and then some manual checking and editing.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
|
|
|
|
|
| |
We’re not ready to release 0.18.0 yet.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
|
|
|
|
|
| |
Various new symbols have been added in 0.18.0 and these symbols need to
be shown in documentation under a new section. The gdata-docs.xml file
is updated in this commit to reflect upon these new symbols.
|
|
|
|
|
|
|
|
|
|
|
| |
The parse_json and get_json functions have been augmented to support
parsing the "properties" list on a file/folder's metadata. The
"properties" list of GDataDocumentsEntry corresponds to the
"properties" list on a file/folder object's metadata. This list stores
all the public/private custom properties and is writable.
The "properties" list has elements of of type GDataDocumentsProperty,
and functions to search/remove/add such properties have also been added.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Google Drive API (v2) supports custom file properties on file/folder
metadata and allows to store key-value pairs there. We add
GDataDocumentsProperty which corresponds to a Property Resource, and
provides functionality to create public/private custom property. The
documentation has also been updated (a new section added for
GDataDocumentsProperty).
GDataDocumentsProperty class will later be used to add a list of
"properties" on GDataDocumentsEntry, accessible through the
file/folder metadata.
|
|
|
|
| |
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
|
|
|
|
|
|
|
|
| |
We’re using Meson now! This also means we drop the ChangeLog; use `git
log` now.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
Fixes: #27
|
|
|
|
|
|
|
|
| |
Automake 1.16.1 has issues with generating a valid Makefile. Since,
libgdata is one of the core-deps of GNOME, it should be ported from
Autotools + make to meson + ninja.
Significant contributions from both Iñigo Martínez and Mayank Sharma.
|
|
|
|
|
|
|
|
| |
This will be used by GNOME To Do through Evolution-Data-Server
to manipulate the position of the task in the list.
Additional test checks were added to ensure the propeties behave
as expected.
|
|
|
|
| |
Signed-off-by: Philip Withnall <philip@tecnocode.co.uk>
|
|
|
|
|
|
|
| |
Also relabel the ‘Documents API’ to ‘Documents/Drive API’ to make it a
bit clearer that it now covers Google Drive.
Signed-off-by: Philip Withnall <philip@tecnocode.co.uk>
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=785885
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on a patch by Milan Crha <mcrha@redhat.com>.
This reworks how pagination is implemented so that multiple pagination
mechanisms are supported explicitly, making the code a lot clearer. A
lot of the new services use pageToken parameters, which we did not
previously support — so this fixes support for pagination in the Google
Tasks service, for example.
This also means that we can drop the hacky pagination support from
GDataDocumentsService.
https://bugzilla.gnome.org/show_bug.cgi?id=775813
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=777980
|
|
|
|
|
|
|
| |
gtk-doc can now generate an entities file to do this for us.
This bumps our gtk-doc dependency to 1.25, which was released in March
2016.
|
|
|
|
|
|
|
|
| |
This property applies to all non-doc/sheet/slide/form documents. It is
similar but distinct from the quota-used property, which is not set if
the file's size isn't counting against the current user's quota.
https://bugzilla.gnome.org/show_bug.cgi?id=773057
|
|
|
|
|
| |
Mention HTTP versus HTTPS, and the need to encrypt files on disk if you
are handling the user’s data (which you are with Google Drive).
|
| |
|
|
|
|
| |
It’s a private header and shouldn’t be in the documentation.
|
|
|
|
|
|
| |
The api-index-full.xml and api-index-deprecated.xml files already define
those two IDs, so we can’t define them again in gdata-docs.xml. Use role
instead, whatever that is.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add new API to allow the refresh token from an OAuth 2 authorizer to be
stored by an application and restored into a new GDataOAuth2Authorizer
instance (a cold start). This adds the following new API:
• GDataOAuth2Authorizer:refresh-token
• gdata_oauth2_authorizer_dup_refresh_token()
• gdata_oauth2_authorizer_set_refresh_token()
It does not add any new tests.
https://bugzilla.gnome.org/show_bug.cgi?id=750746
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A new sub-class was introduced to set JSON as the content-type for
Drive v2. It was a good opportunity to move the Drive-specific JSON
parsing code from the base class.
New API added:
• GDataDocumentsAccessRule
This new class must be used in place of GDataAccessRule for any
interactions with the Drive API. This is essentially a soft API break,
but it’s unavoidable.
https://bugzilla.gnome.org/show_bug.cgi?id=684920
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was non-trivial. New API added:
• GDataCalendarAccessRule
Due to how this new class overrides GDataAccessRule, it must be used in
place of GDataAccessRule for any interactions with the Calendar API.
This is essentially a soft API break for anyone who uses calendars. It’s
unavoidable.
https://bugzilla.gnome.org/show_bug.cgi?id=664353
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Deprecated API:
• GDataCalendarFeed:timezone, gdata_calendar_feed_get_timezone()
• GDataCalendarFeed:times-cleaned,
gdata_calendar_feed_get_times_cleaned()
• GDataBatchable implementation in GDataCalendarService
• gdata_calendar_service_insert_event(),
gdata_calendar_service_insert_event_async()
• GDataCalendarCalendar:times-cleaned,
gdata_calendar_calendar_get_times_cleaned()
• GDataCalendarCalendar:edited, gdata_calendar_calendar_get_edited()
API changes:
• GDataBatchable implementation in GDataCalendarService will now always
fail
• ACLs are temporarily not supported; support for them will be re-added
in future when they have been ported to the new API
• Add gdata_calendar_service_insert_calendar_event(),
gdata_calendar_service_insert_calendar_event_async()
This includes a partial update of the unit tests, but most of them have
been disabled pending updates.
https://bugzilla.gnome.org/show_bug.cgi?id=664353
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Deprecated API:
• GDataYouTubeQuery:format, gdata_youtube_query_get_format(),
gdata_youtube_query_set_format()
• GDataYouTubeQuery:has-location
• GDataYouTubeQuery:language, gdata_youtube_query_get_language(),
gdata_youtube_query_set_language()
• GDataYouTubeQuery:sort-order, gdata_youtube_query_get_sort_order(),
gdata_youtube_query_set_sort_order()
• GDataYouTubeQuery:uploader, gdata_youtube_query_get_uploader(),
gdata_youtube_query_set_uploader()
• GDataYouTubeSortOrder
• GDataYouTubeUploader
• GDataYouTubeContent
• GDataYouTubeFormat
• GDataYouTubeVideo:video-id, gdata_youtube_video_get_video_id()
• gdata_youtube_video_look_up_content()
(use gdata_youtube_video_get_player_uri() instead)
• GDATA_YOUTUBE_RATING_TYPE_SIMPLE
• GDataYouTubeCredit, GDATA_YOUTUBE_CREDIT_ENTITY_PARTNER
• GDataYouTubeVideo:credit, gdata_youtube_video_get_credit()
• GDataYouTubeVideo:is-draft, gdata_youtube_video_is_draft(),
gdata_youtube_video_set_is_draft()
• GDATA_YOUTUBE_*_FEED except GDATA_YOUTUBE_MOST_POPULAR_FEED (all
others have been deprecated online and will transparently return the
most popular videos from the past 24 hours)
API changes:
• GDataYouTubeQuery:restriction no longer accepts IP addresses
• All GDataCommentable functionality on GDataYouTubeVideo is disabled
at runtime until the v3 YouTube API for comments is finished online
• Not all properties of a GDataYouTubeVideo may be retrieved when doing
searches, retrieving related videos, or listing standard feeds — to
guarantee getting all properties, use
gdata_service_query_single_entry() for the video in question; common
properties such as title, description, player URI and thumbnails
will always be retrieved
Internally, the GDataYouTubeControl and GDataYouTubeGroup APIs have been
removed, but they were never visible publicly, so this is not an API
break.
Due to the transition from v2 to v3 of the YouTube API, your client’s
developer key may stop working. Refresh it here:
https://developers.google.com/youtube/registering_an_application
https://bugzilla.gnome.org/show_bug.cgi?id=687597
|
|
|
|
|
|
|
|
|
|
|
|
| |
This parses YouTube-specific properties of the feed — specifically, the
total-results and items-per-page, which were previously handled in a
service-agnostic manner by GDataFeed, but YouTube doesn’t conform to
that.
This adds the following new API:
• GDataYouTubeFeed
https://bugzilla.gnome.org/show_bug.cgi?id=687597
|
|
|
|
|
|
|
|
|
| |
Having pre-defined and documented macros demystifies these strange
URL-like strings for the application developer.
This adds the following new API:
• GDATA_CATEGORY_SCHEMA_LABELS_SHARED
• GDATA_CATEGORY_SCHEMA_LABELS_VIEWED
|
|
|
|
|
|
|
|
| |
Making it a boxed type makes it friendly to bindings, as there's
some more embedded knowledge about how to deal with this type
memory-wise.
https://bugzilla.gnome.org/show_bug.cgi?id=737936
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a new GDataAuthorizer subclass to support OAuth 2.0
authorisation, which is needed for the Google Tasks unit tests.
This includes support for all Google OAuth 2.0 features (note that
Google’s implementation of OAuth 2.0 is not entirely standard, so this
OAuth 2.0 authoriser cannot be used outside of Google’s services). It
includes full unit tests too.
New API:
• GDATA_OAUTH2_REDIRECT_URI_OOB
• GDATA_OAUTH2_REDIRECT_URI_OOB_AUTO
• GDataOAuth2Authorizer
https://bugzilla.gnome.org/show_bug.cgi?id=646285
|
| |
|
|
|
|
| |
These are now correctly included in gtk-doc.make.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will come in useful when testing services which don’t support
ClientLogin authorisation, such as Google Tasks. Such services require
OAuth authorisation, which requires user interaction. That puts up a big
barrier to running the unit tests frequently, and Google seem to provide
no ‘playground’ API key which could be used to bypass this requirement
for testing purposes.
The idea is that traces are recorded for tests using an OAuth
authoriser (requiring user interaction), then the dummy authoriser is
substituted when the tests are run offline against the pre-recorded
traces. This will require custom message matching in uhttpmock to ignore
the Authorization header, which will differ between the OAuth and dummy
authorisers.
|
|
|
|
|
|
|
|
|
| |
So the user doesn’t need to keep typing out the well-known strings which
form the accepted values of GDataTasksTask:status.
This adds new API:
• GDATA_TASKS_STATUS_NEEDS_ACTION
• GDATA_TASKS_STATUS_COMPLETED
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds support for <gAcl:withKey/> elements, allowing for
authorisation keys in ACLs, e.g. for Google Documents.
This adds the following API:
• GDataAccessRule:key
• gdata_access_rule_get_key()
and appropriate tests.
https://bugzilla.gnome.org/show_bug.cgi?id=690628
|
| |
|
|
|
|
| |
These are now performed by gtk-doc. Yay!
|
|
|
|
|
|
|
|
| |
This helper function can be used together with the topic API,
if a returned element is an image, this function can be used to
retrieve a GInputStream to the image at a requested maximum size.
https://bugzilla.gnome.org/show_bug.cgi?id=726486
|
|
|
|
|
|
|
| |
This API enables searching for search terms, returning amongst other
info the Freebase IDs usable on the topic API.
https://bugzilla.gnome.org/show_bug.cgi?id=726486
|
|
|
|
|
|
|
| |
With this API, structured data can be obtained about any Freebase
ID, including localized text and references to images.
https://bugzilla.gnome.org/show_bug.cgi?id=726486
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This service is, according to the main site, a "A community-curated
database of well-known people, places, and things", it allows searching
for and offering information about a wide range of topics, in a
well-structured and uniform manner.
The most low-level API is the MQL query interface, that is a JSON-based
language, queries consist of a data graph (according to their data schema)
with blank places, that will be filled in in the reply.
https://bugzilla.gnome.org/show_bug.cgi?id=726486
|
|
|
|
|
|
|
|
|
|
|
| |
This is a link type which is included in the GData specification (in the
RelaxNG schema), but is not documented anywhere. Good job, Google. Best
for us to define it and allow clients to use it, than to ignore it.
New API:
• GDATA_LINK_PARENT
https://bugzilla.gnome.org/show_bug.cgi?id=725827
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds GDataTasks classes to libgdata:
• GDataTasksService
• GDataTasksQuery
• GDataTasksTasklist
• GDataTasksTask
This includes full documentation, but no test cases. No new dependencies
have been added to libgdata, as all the necessary ones were added with the
core JSON work.
https://bugzilla.gnome.org/show_bug.cgi?id=657539
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bound to SoupSession’s ‘proxy-resolver’ property. Based on commit
8f1923fcd9c4203f68ce6a0405526500a77783e5 by Matthew Barnes <mbarnes@redhat.com>.
This deprecates the following API:
• GDataOAuth1Authorizer:proxy-uri
• gdata_oauth1_authorizer_[get|set]_proxy_uri()
and adds the following new API:
• GDataOAuth1Authorizer:proxy-resolver
• gdata_oauth1_authorizer_[get|set]_proxy_resolver()
Closes: https://bugzilla.gnome.org/show_bug.cgi?id=709758
|