summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* calendar: WIP more v3 workwip/calendar-v3Philip Withnall2015-02-015-252/+393
|
* calendar: WIP V3 workPhilip Withnall2015-02-019-194/+1074
|
* calendar: WIP work to port to the v3 APIPhilip Withnall2015-02-0110-261/+376
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=664353
* tests: Add tests for Freebase search APICarlos Garnacho2014-12-233-0/+195
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=737541
* freebase: Fix locale-dependent issues in geolocated queriesCarlos Garnacho2014-12-231-2/+8
| | | | | | | | Latitude/longitude are really expected with a '.' decimal point by the service, breaking on locales that would use anything different. Use g_ascii_formatd which always uses the '.' decimal point. https://bugzilla.gnome.org/show_bug.cgi?id=737541
* freebase: Fix typo in search queryCarlos Garnacho2014-12-231-1/+1
| | | | | | | | The string array matches the GDataFreebaseSearchFilterType, using the FilterNodeType was unintended, and TYPE_CONTAINER happened to match GDATA_FREEBASE_SEARCH_FILTER_ALL. https://bugzilla.gnome.org/show_bug.cgi?id=737541
* freebase: Create async topic replies with the correct GTypeCarlos Garnacho2014-12-231-1/+1
| | | | | | | The async version was wrongly using the parent type, so the returned object wasn't a GDataFreebaseTopicResult at all. https://bugzilla.gnome.org/show_bug.cgi?id=737540
* freebase: Add GType for GDataFreebaseSearchResultItemCarlos Garnacho2014-12-234-0/+25
| | | | | | | | 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
* tests: Add tests for freebase topic APICarlos Garnacho2014-12-233-0/+4063
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=737539
* freebase: Fix thinko when creating compound GDataFreebaseTopicObjectsCarlos Garnacho2014-12-211-1/+1
| | | | | | | | The check was actually inverted, receiving a newly created object is obviously the expected condition. This made the parsing of compound objects a lot more shallower than the received data. https://bugzilla.gnome.org/show_bug.cgi?id=737539
* freebase: reader_fill_object_gvalue() is only meant for "object" typesCarlos Garnacho2014-12-211-1/+1
| | | | | | | | | | Compound types are only meant to be handled through reader_fill_compound_gvalue(), which will iterate through its "property" array. Otherwise, compound elements with an ID (which is not mandatory, but ok for these to have) would be created as shallow objects instead of containers of further objects/values. https://bugzilla.gnome.org/show_bug.cgi?id=737539
* demos: Add a docs-list demoDebarshi Ray2014-12-122-0/+141
| | | | | | | | Adapted from a bug report reproducer program by Debarshi Ray, this lists all the documents in the user’s Google Documents account, getting the account information from GOA. https://bugzilla.gnome.org/show_bug.cgi?id=741345
* build: Fix some whitespace in Makefile.amPhilip Withnall2014-12-121-19/+19
|
* documents: Handle final page pagination in GDataDocumentsServicePhilip Withnall2014-12-121-1/+59
| | | | | | | | | The Google Documents servers always return a next page URI in a GDataFeed unless on the final page of results, in which case no URI is returned. Pass that information through to the GDataQuery so that pagination works correctly for Google Documents. https://bugzilla.gnome.org/show_bug.cgi?id=741345
* core: Explicitly support a final page in GDataQuery paginationPhilip Withnall2014-12-123-2/+61
| | | | | | | | | | | | | | | | | The pagination model previously used by GDataQuery was to assume that the server would return an empty GDataFeed once the final page was passed by calling gdata_query_next_page(). Unfortunately, the Google Documents servers don’t do that — instead, they provide a next page URI in each GDataFeed, and don’t provide one on the final page. GDataQuery did not support this kind of explicit knowledge about the current page being the final one. Add support for it with a delightful set of hacky internal functions. Return a dummy empty feed from GDataService if passed a GDataQuery which is flagged as having reached the end of its pagination. https://bugzilla.gnome.org/show_bug.cgi?id=741345
* core: Allow the GDataFeed type to be passed to _gdata_feed_new()Philip Withnall2014-12-123-6/+16
| | | | | | | This will be used internally later to support constructing custom empty feeds for pagination purposes. https://bugzilla.gnome.org/show_bug.cgi?id=741345
* core: Virtualise feed parsing in GDataServicePhilip Withnall2014-12-122-11/+53
| | | | | | | | | | | | | | | Split the bulk of feed parsing out into a virtual method on GDataService. This will allow subclasses of GDataService to implement service-specific tweaks to feed parsing, which is required for pagination handling with Google Documents. New API: • GDataServiceClass.parse_feed This does not break ABI — it consumes one of the struct’s expansion slots. https://bugzilla.gnome.org/show_bug.cgi?id=741345
* core: Eliminate unnecessary is_async argument from parser functionsPhilip Withnall2014-12-124-31/+31
| | | | | | | | | Instead, use g_main_context_invoke(), which guarantees to call the callback synchronously if the GMainContext is owned, and in an idle callback otherwise. This is exactly what we want for implementing callbacks which could come from this thread or a worker thread. https://bugzilla.gnome.org/show_bug.cgi?id=741345
* core: Use correct relation URI for next/previous feed linksPhilip Withnall2014-12-121-2/+2
| | | | | | | | GDataLink enforces that all relations are proper URIs, prefixing iana.org to those which aren’t — so we need to do the same when calling gdata_feed_look_up_link(). https://bugzilla.gnome.org/show_bug.cgi?id=741345
* tests: Switch to non-interactive tests by defaultPhilip Withnall2014-12-121-3/+7
| | | | | | This fixes `make check` stalling forever on requesting user input. To run the interactive tests, the programs now need to be run with --interactive.
* tests: Eliminate ISO 8601 formatting workaround for datesPhilip Withnall2014-12-124-52/+52
| | | | | | | Follow up to commit 732017e4e5235e28c578cc3367fa0c4548b65495732017e4e5235e28c578cc3367fa0c4548b65495. https://bugzilla.gnome.org/show_bug.cgi?id=739956
* Updated Turkish translationYaşar Şentürk2014-12-041-80/+158
|
* tests: Temporarily disable some Contacts test assertionsPhilip Withnall2014-11-091-2/+3
| | | | | | Seems these elements broke on the server at some point. https://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3662
* tests: Update Contacts test traces for ISO 8601 date changesPhilip Withnall2014-11-0937-652/+3197
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=737799
* tests: Remove pointless async authorizer tests from contacts.cPhilip Withnall2014-11-091-45/+1
| | | | | The authorisers are tested separately, and don’t need to be re-tested in each unit test suite.
* core: Eliminate ISO 8601 formatting workaround for datesPhilip Withnall2014-11-091-19/+1
| | | | | | | | Google have fixed the issue upstream, so the workaround is no longer needed. Thanks Google! https://bugzilla.gnome.org/show_bug.cgi?id=737799 https://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3595
* Add --disable-tests to skip the building of testsKalev Lember2014-11-032-5/+13
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=739395
* core: Mark all API as stable and impose API and ABI stability guaranteesPhilip Withnall2014-11-03105-106/+111
| | | | | | | | It’s time for libgdata to grow up and start guaranteeing some stability for its users. In this vein, it’s already been API stable for around 3 years (since 0.9.1) — it’s about time that was made explicit. http://upstream-tracker.org/versions/libgdata.html is quite interesting.
* core: Add padding members to class structuresPhilip Withnall2014-11-0397-0/+555
| | | | | This gives us flexibility for soft ABI breaks in future if needed, after we lock down the ABI entirely.
* tests: Remove unnecessary non-NULL testPhilip Withnall2014-11-011-1/+1
| | | | | | It was confusing Coverity. Coverity issue: #74584
* docs: Fix a typo in the READMEPhilip Withnall2014-10-171-1/+1
|
* Updated German translationBernd Homuth2014-09-231-54/+68
|
* tests: Add networked tests for the Google Tasks servicePhilip Withnall2014-09-2127-127/+2035
| | | | | | | This brings test coverage of the gdata/services/tasks/ directory up to 84% of lines and 90% of functions, which is good enough. https://bugzilla.gnome.org/show_bug.cgi?id=657539
* tasks: Add preconditions for tasklist IDs being set when inserting tasksPhilip Withnall2014-09-211-0/+4
| | | | Can’t insert a task to a non-tasklist.
* tasks: Handle an additional form of AUTHENTICATION_REQUIRED errorPhilip Withnall2014-09-211-1/+2
| | | | Apparently there are two ‘reason’ codes which correspond to this.
* core: Don’t unset refresh token on refreshing OAuth 2.0 authorisationPhilip Withnall2014-09-211-2/+4
| | | | | | | When refreshing an OAuth 2.0 authorisation, only a new access token is returned by the server — the refresh token is left unchanged, so a new one is not returned. Do not use that as an excuse to forget the existing refresh token.
* core: Handle ‘etag’ and ‘kind’ members in JSON feedsPhilip Withnall2014-09-211-0/+4
| | | | Set the GDataFeed:etag property and ignore the kind.
* update Punjabi Translation for 3.14 releaseA S Alam2014-09-211-62/+78
|
* Updated POTFILES.inPiotr Drąg2014-09-211-0/+1
|
* build: Increment version to 0.17.0Philip Withnall2014-09-211-2/+2
|
* tests: Call setlocale() on startupPhilip Withnall2014-09-211-0/+3
| | | | So that the correct character encoding is set for all tests.
* core: Add a GDataOAuth2Authorizer for OAuth 2.0 supportPhilip Withnall2014-09-2121-7/+2922
| | | | | | | | | | | | | | | | | 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
* update zh_CN translationIris Gou2014-09-211-1/+1
|
* update zh_CN translationIris Gou2014-09-211-27/+34
|
* Updated Danish translationAsk H. Larsen2014-09-201-27/+34
|
* Updated Swedish translationMattias Eriksson2014-09-181-16/+15
|
* build: Increment version to 0.16.1Philip Withnall2014-09-181-1/+1
|
* Release version 0.16.0LIBGDATA_0_16_0Philip Withnall2014-09-188-13/+62
|
* tasks: Output the ‘hidden’ property in generated JSONPhilip Withnall2014-09-181-0/+3
| | | | | | It’s read-only, but that hasn’t stopped us outputting all the other read-only properties. This can be reverted if real life testing proves it’s a problem.
* tasks: Simplify some codePhilip Withnall2014-09-181-7/+2
| | | | This introduces no functional changes.
View Lorry Controller Status