summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* tests: Fix some compiler warnings in the YouTube testsPhilip Withnall2015-07-101-3/+2
|
* tests: Remove outdated async authentication tests from YouTubePhilip Withnall2015-07-101-189/+0
| | | | | | These were using the unsupported ClientLogin API. The OAuth2 authoriser has its own async authorisation tests, so porting the existing YouTube tests would gain us nothing.
* youtube: Fix a potential NULL object dereferencePhilip Withnall2015-07-101-1/+1
|
* tests: Port and re-enable YouTube upload testsPhilip Withnall2015-07-105-94/+225
|
* youtube: Re-enable video uploads using the v3 APIPhilip Withnall2015-07-103-4/+33
| | | | | This required a way of deleting videos once we’re done with them, plus a tweak to the upload parts parameter.
* tests: Port and re-enable online YouTube comment testsPhilip Withnall2015-07-109-173/+3045
|
* tests: Port and re-enable offline YouTube comment testsPhilip Withnall2015-07-101-17/+21
|
* youtube: Remove a small amount of dead codePhilip Withnall2015-07-101-4/+0
| | | | Set but unused variables.
* youtube: Port YouTube comments to the v3 APIPhilip Withnall2015-07-103-16/+421
| | | | | | This should make YouTube comments work again. They have been ported to JSON from XML, and the GDataCommentable implementations updated to use the correct comment URIs.
* core: Add a new internal method for setting GDataEntry:etagPhilip Withnall2015-07-102-0/+19
| | | | This will be useful for YouTube comments, coming up shortly.
* tests: Remove an unused YouTube testPhilip Withnall2015-07-101-51/+0
| | | | From way back in 2009. Time flies!
* youtube: Simplify video ratings handling codePhilip Withnall2015-07-081-4/+16
| | | | | | | This simplifies the code and fixes a problem where if both region_restriction_allowed and region_restriction_blocked were not spcified, the GDataYouTubeVideo would behave as if restricted for all regions, which is most likely not the intention.
* tests: Port and re-enable YouTube video rating testsPhilip Withnall2015-07-081-142/+28
| | | | | | | | A lot of the media:group parsing stuff has gone, and was not tested properly to begin with, so that test can be dropped. Similarly, the error handling test can be dropped because the JSON parser code is deliberately a lot more tolerant now that arbitrary ratings boards are supported.
* tests: Port and re-enable YouTube category testsPhilip Withnall2015-07-084-69/+1375
| | | | | | | Unfortunately the YouTube category list is no longer localised to the region passed in to the query — the category names are now always in English. So the only way we can detect differences caused by changing region is to look at how many categories are returned.
* app: Fix parsing of YouTube categoriesPhilip Withnall2015-07-081-1/+8
| | | | | | | | The GDataAPPCategories parser used to take in the GType of the GDataCategory subclass to construct when parsing its category list; in the port to JSON, it was accidentally changed to always construct GDataCategory instances. This broke the YouTube code, which was hoping to see GDataYouTubeCategory instances be constructed.
* docs: Add gdata-documents-utils.h to IGNORE_HFILESPhilip Withnall2015-07-081-0/+1
| | | | It’s a private header and shouldn’t be in the documentation.
* tests: Port and re-enable several YouTube parsing testsPhilip Withnall2015-07-081-185/+96
|
* youtube: Fix parsing videos which have no recordingDatePhilip Withnall2015-07-081-1/+2
| | | | | If they have a recordingDetails section, but no recordingDate, the parser was crashing.
* Updated Portuguese translationPedro Albuquerque2015-07-061-50/+56
|
* Updated Polish translationPiotr Drąg2015-07-051-139/+154
|
* Updated POTFILES.inPiotr Drąg2015-07-051-0/+1
|
* tests: Port and re-enable the YouTube batch API testsPhilip Withnall2015-07-054-137/+188
| | | | | | | | | Now testing that GDataYouTubeService no longer claims to support batch operations, rather than testing that they work. https://developers.google.com/youtube/v3/guides/implementation/deprecated#Batch_Processing https://bugzilla.gnome.org/show_bug.cgi?id=750914
* youtube: Mark GDataBatchable as unsupported by YouTube any morePhilip Withnall2015-07-051-1/+18
| | | | | | | It is no longer supported in version 3 of the API, so implement the new GDataBatchable.is_supported API and return FALSE for everything, meaning that all batchable operations on GDataYouTubeService will now fail with GDATA_SERVICE_ERROR_WITH_BATCH_OPERATION.
* core: Add GDataBatchable.is_supported virtual methodPhilip Withnall2015-07-052-0/+36
| | | | | | This new API is intended to be used by GDataYouTubeService to allow it to indicate which batch operations it supports (since this has changed since v3 of the API — now batch operations are no longer supported).
* tests: Port and re-enable the YouTube query URI testsPhilip Withnall2015-07-051-9/+39
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=750914
* tests: Fix query parameter comparisons involving dates in YouTube testsPhilip Withnall2015-07-058-3581/+2970
| | | | | | | | | | | | | | | The only way to implement some of the standard feeds in the YouTube service is now to query filtering against the current date, which means that a custom message comparison function has to be installed into the uhttpmock code to ignore that query parameter when replacing HTTP traces. Use some new convenience API in libuhttpmock to achieve this. Dependency changes: • libuhttpmock ≥ 0.5.0 https://bugzilla.gnome.org/show_bug.cgi?id=750914
* youtube: Reduce assumed accuracy of time query parametersPhilip Withnall2015-07-051-0/+3
| | | | | | | There is no point in sending microsecond datestamps to the server. This also makes the API more testable, since the unit tests no longer need to guess the date stamp with microsecond accuracy. (They are still open to second-accuracy race conditions, though.)
* tests: Port and re-enable a few more YoUTube unit testsPhilip Withnall2015-07-049-2825/+4561
|
* core: Add a missing NULL terminator to parsed JSON string arraysPhilip Withnall2015-07-041-0/+3
| | | | | This fixes a crash on finalisation of GDataYouTubeVideo if it has keywords set.
* docs: Fix multiply-defined index IDsPhilip Withnall2015-07-021-2/+2
| | | | | | 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.
* Updated Portuguese translationPedro Albuquerque2015-07-011-162/+196
|
* goa-authorizer: Add domains for documents if "files" is onDebarshi Ray2015-07-011-1/+1
| | | | | | | | | The new gvfs backend will enable nautilus and the gtk+ file chooser to interact with Google Drive. This means that GOA accounts in Google will get a "files" switch, which we should check when deciding whether to enable the documents service. https://bugzilla.gnome.org/show_bug.cgi?id=751782
* documents: Add support for updating content using Drive v2Debarshi Ray2015-07-011-5/+11
| | | | | | | | | There is a bug in the Drive web UI where the preview doesn't get updated with the new content, but if you download or go through the revisions then things are as they should be. I could reliably reproduce it with plain/text content. https://bugzilla.gnome.org/show_bug.cgi?id=684920
* tests: Add a test for location presence in default YouTube video JSONPhilip Withnall2015-06-241-0/+36
| | | | | This is a unit test for the fix in commit 5ca05e195f7cecd63d6616aeef8410df8eee978c.
* documents: Split out the code to add a parent folder's link to an entryDebarshi Ray2015-06-171-13/+18
| | | | | | We will need this for creating folders and copying files. https://bugzilla.gnome.org/show_bug.cgi?id=684920
* documents: Set mimeType in JSONDebarshi Ray2015-06-172-0/+38
| | | | | | | | A Drive v2 folder is a file with the MIME type application/vnd.google-apps.folder (and with no extension). Therefore, setting the MIME type is crucial for creating new folders. https://bugzilla.gnome.org/show_bug.cgi?id=684920
* documents: Support uploads to a specific location using Drive v2Debarshi Ray2015-06-163-5/+70
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=684920
* core: Use constructed instead of constructorDebarshi Ray2015-06-161-8/+5
| | | | | | | | | The constructed vfunc is the idiomatic place to access construct properties, which is what we are doing in this case. The constructor is more intrusive and is usually used for implementing things like singletons. https://bugzilla.gnome.org/show_bug.cgi?id=684920
* core: Add GDataOAuth2Authorizer:refresh-token APIPhilip Withnall2015-06-164-5/+123
| | | | | | | | | | | | | 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
* tests: Use GDataDocumentsAccessRule for documents ACLsDebarshi Ray2015-06-161-9/+9
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=684920
* documents: Add support for uploads using Drive v2Debarshi Ray2015-06-162-53/+22
| | | | | | | This is enough to upload a file to the root folder, but you can't select a specific location. https://bugzilla.gnome.org/show_bug.cgi?id=684920
* documents: Split out the code to map a content type to a GTypeDebarshi Ray2015-06-154-25/+100
| | | | | | We will need this in gdata_documents_service_finish_upload. https://bugzilla.gnome.org/show_bug.cgi?id=684920
* documents: Support searching for readers using Drive v2 queriesDebarshi Ray2015-06-121-13/+20
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=684920
* core: Read-only properties are not going to be set via the public APIDebarshi Ray2015-06-121-4/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=684920
* calendar: Fix a path in the GDataCalendarAccessRule documentationDebarshi Ray2015-06-101-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=684920
* documents: Add support for editing ACLs using Drive v2Debarshi Ray2015-06-1010-71/+369
| | | | | | | | | | | | | | | 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
* core: Expose _gdata_access_rule_set_key() internallyDebarshi Ray2015-06-102-0/+17
| | | | | | This will be used by GDataDocumentsAccessRule when parsing the JSON. https://bugzilla.gnome.org/show_bug.cgi?id=684920
* core: Fix the GDataAccessRule exampleDebarshi Ray2015-06-091-3/+5
| | | | | | | | We need to pass the a GDataAuthorizationDomain to gdata_service_insert_entry, and we should not unref the GDataLink returned by gdata_entry_look_up_link. https://bugzilla.gnome.org/show_bug.cgi?id=750395
* build: Fix -Werror build for clangTing-Wei Lan2015-06-091-1/+2
| | | | | | This fixes implicit enumeration type conversion. https://bugzilla.gnome.org/show_bug.cgi?id=750480
* tests: Silence -Wunsafe-loop-optimizationsDebarshi Ray2015-06-031-1/+3
| | | | | | | We can end up with an infinite loop if end_num is G_MAXUINT. Let's use ‘<’ instead of ‘<=’ to avoid this. https://bugzilla.gnome.org/show_bug.cgi?id=750335
View Lorry Controller Status