| 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
|
| |
|
|
|
|
| |
The cleanup function is not defined for GDataQuery, which prevents
G_DECLARE_DERIVABLE_TYPE use for its subclasses. Let's define it
so G_DECLARE_DERIVABLE_TYPE can be used in the subsequent commits.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
| |\
| |
| |
| |
| | |
core: Add g_autoptr() support for GDataUploadStream
See merge request GNOME/libgdata!26
|
| | |
| |
| |
| | |
https://gitlab.gnome.org/GNOME/libgdata/-/merge_requests/26
|
| |/ |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
all: Fix various typos and incorrect terminology
See merge request GNOME/libgdata!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>
|
| |\ \
| |/
|/|
| |
| | |
Various minor fixes to meson_options.txt
See merge request GNOME/libgdata!24
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
People should be able to get these from meson itself, or by reading
`meson_options.txt`. Putting them in the description strings is just
going to lead to that going out of sync with the actual options.
Spotted by Debarshi Ray in !23.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
| | |
| |
| |
| |
| |
| | |
Conventionally, they’re not enabled by default.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
| | |
| |
| |
| | |
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
| |/ |
|
| |\
| |
| |
| |
| | |
build: Disable the gtk-doc documentation by default
See merge request GNOME/libgdata!23
|
| |/
|
|
|
|
|
|
|
| |
This matches the documentation in the current Meson build, and the
behaviour of the old Autotools build.
Fallout from d3ba69233a9ef1f415b10efc44ea186a6d58a2bb
https://gitlab.gnome.org/GNOME/libgdata/-/merge_requests/23
|
| | |
|
| |
|
|
| |
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
core: Always refresh authorization when creating streams
Closes #23
See merge request GNOME/libgdata!22
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Non-resumable upload streams quite often fail with authorization errors
as we are probably hitting some limits. The only way currently to deal
with them is to refresh authorization manually and upload everything
again as it is not possible to resume the transfer. This is big issue
for streaming operations provided by GVfs. I have made several tests
and realized that if we explicitely refresh the authorization before
the transfer, then those authorization errors doesn't occur. So let's
always refresh the authorization when constructing the streams and do
the same for upload streams as well as they are also affected. In theory,
the resumable streams could solve this better, however they currently
require content size to be specified at the beginning, which is not
usable for the streaming operations in GVfs.
Fixes: https://gitlab.gnome.org/GNOME/libgdata/issues/23
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
