summaryrefslogtreecommitdiff
path: root/client/dconf-client.c
Commit message (Collapse)AuthorAgeFilesLines
* client: Fix a minor typo in some documentationPhilip Withnall2018-08-081-1/+1
| | | | Signed-off-by: Philip Withnall <withnall@endlessm.com>
* Add some transfer annotationsXavier Claessens2018-08-081-9/+11
| | | | | | | (Expanded by Philip Withnall <withnall@endlessm.com> to add more annotations and fix prior review comments.) https://bugzilla.gnome.org/show_bug.cgi?id=758903
* DConfClient: Add "writability-changed" signalXavier Claessens2015-12-161-0/+27
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=759128
* client: restrict list_locks to work on dirsAllison Ryan Lortie2015-12-161-3/+3
| | | | | | | This was always the intention, and is even documented that way in the gtk-doc block above. I'm not sure why I used paths. In any case, this API has never been released, so the change is safe.
* docs: add new APIsAllison Ryan Lortie2015-12-161-0/+17
| | | | ...and other various cleanups.
* client: replace _read_default() with _read_full()Allison Ryan Lortie2015-12-161-9/+32
| | | | | | | | | This API has never appeared in a released version of dconf (even unstable). Replace it with a more generally-useful form. Update the test cases, dconf commandline tool and vapi accordingly. https://bugzilla.gnome.org/show_bug.cgi?id=759128
* engine: add DCONF_READ_DEFAULT_VALUE flagAllison Ryan Lortie2015-12-161-29/+1
| | | | | | | | Add a flag that allows checking the default value without constructing a read_through queue. Make use of this new flag to simplify code in a couple of places. https://bugzilla.gnome.org/show_bug.cgi?id=759128
* engine: merge _read and _read_user_value()Allison Ryan Lortie2015-12-161-2/+2
| | | | | | | Delete the separate dconf_engine_read_user_value() and merge its functionality into dconf_engine_read() by adding a flags field. https://bugzilla.gnome.org/show_bug.cgi?id=759128
* Modernise the headers of dconf-clientAllison Ryan Lortie2015-11-301-1/+3
| | | | | | | Add support for g_autoptr() on DConfClient and DConfChangeset. Switch to using G_DECLARE_FINAL_TYPE in the declaration of DConfClient. https://bugzilla.gnome.org/show_bug.cgi?id=758871
* dconf-client: include dconf-paths headerAllison Ryan Lortie2015-11-301-0/+1
| | | | | We should have this included since we use the functions in it in our precondition checks.
* engine, client: add list_locks() operationAllison Ryan Lortie2015-11-301-0/+26
| | | | | | | Add an API to dconf-engine (and exposed via DConfClient) for getting a list of locks that are present in a given dconf profile. https://bugzilla.gnome.org/show_bug.cgi?id=758864
* DConfClient: add read_default() APIAllison Ryan Lortie2015-11-301-0/+54
| | | | | | | | Add an API to read the default value of a key. Add a testcase. https://bugzilla.gnome.org/show_bug.cgi?id=758860
* Updated FSF's addressDaniel Mustieles2014-01-311-3/+1
|
* engine: add support for WritabilityNotifyRyan Lortie2013-11-261-0/+1
| | | | | Wire through WritabilityNotify signals from the engine. This has been unimplemented for a very long time...
* engine: add 'profile' argument to constructorRyan Lortie2013-11-261-1/+1
| | | | | | | Allow specifying a profile when calling dconf_engine_new(). This will allow us to avoid setting/unsetting the DCONF_PROFILE environment in testcases from contexts where other threads may be reading from the environment.
* Add missing "config.h" include everywhereRyan Lortie2013-11-241-0/+2
| | | | We ought to be including this from each .c file.
* engine, gsettings: prevent empty changesetsRyan Lortie2013-02-111-1/+2
| | | | | | | | We should not send empty changesets to the service so just ignore them when we get them. This now means that an empty 'dconf load' will not send any D-Bus messages (and will not cause D-Bus activation).
* docs/comments: make some corrections/updatesRyan Lortie2013-02-111-3/+3
| | | | | Many fixes for typos but also some adjustments for the recent refactoring (particularly updating HACKING).
* engine: bring back origin_tag logicRyan Lortie2012-07-151-2/+3
| | | | | | | | | The GSettings backend still wants to use this and it does us no harm to have it on the engine API (which is only visible internally). Adjust the various consumers of the engine to the new API. Thanks to Rui Matos for reminding me about this...
* Reimplement sync() functionalityRyan Lortie2012-07-101-2/+24
| | | | | | | | | Add dconf_engine_sync() that does the same thing as the code in the GSettings backend used to do, in a cleaner way. Update the GSettings backend to use the new call. Add a new call to DConfClient wrapping the engine call as well.
* big docs cleanupRyan Lortie2012-07-101-0/+276
| | | | We're now back at 100% docs coverage with no warnings.
* massive Makefile reorganisationRyan Lortie2012-07-081-1/+1
| | | | | | | | | | Clean up the Makefiles and make them as similar as possible. Move CFLAGS to a common point of definition and stop using -I so much. Replace the 'dbus stub' with libdconf-mock.a in tests/. Fill in some stubs for future mock code for shm and gvdb (just to get things compiling for now).
* Implement change signalsRyan Lortie2012-07-021-4/+22
| | | | | | | | | | | | | | | | Support receiving and properly exposing change notifications. This required some changes to improve the thread-safety of destroying a DConfEngine. It is possible that a signal would be arriving (in the worker thread) at the exact instant that a DConfEngine was being destroyed (from the finalize of the DConfClient or DConfSettingsBackend). This could lead to the object being accessed after it was finalized. We can avoid this by using weak references and by being more careful about when the DConfEngine is freed (by taking a ref to it in the signal handler and releasing it when done).
* Massively reorganise the client-sideRyan Lortie2012-07-021-46/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit represents a rather complete rethinking of DConfEngine. - the different kinds of sources are now properly abstracted. This will make landing NFS support substantially easier. - there is now substantially more internal documentation - DConfEngineMessage is gone and replaced with ordinary function calls to be implemented by the D-Bus glue code - the GDBus glue has been factored out and is now shared between the client library and GSettings - the "outstanding" queue logic from the GSettings backend is now in the engine - all changes now go through a single API that accepts a (new) DConfChangeset object. Currently this only supports the current operations (ie: setting and resetting). In the future this object will also support the directory operations required by GSettingsList and will be the basis for the new approach to implementing the 'delayed' GSettingsBackend (which will be the method by which those two concepts can co-exist). The (internal) API of the engine changed substantially. This caused the following: - the libdconf client library has been rewritten in C. Most of the complicated aspects of it (that made it more convenience to use Vala) are now gone. - during the rewrite of libdconf, the DConfClient API changed a bit to look more like a proper GObject. It now makes GIO-style use of thread-default main contexts and uses GObject signals for notifications (instead of hand-rolled callbacks). - the GSettings backend has been substantially simplified (the "outstanding" logic is gone). No externally-visible changes. - the dbus-1 backend has taken a copy of the old engine code for now until it can be ported to the new engine and sufficiently tested. No externally-visible changes. - the dconf commandline tool and dconf-editor required minor changes to adjust to the DConfClient API changes There is a substantial amount of cleaning up and finishing of work to be done. There are many stubs remaining. There are likely still a large number of bugs.
* Add a HACKINGRyan Lortie2012-07-011-0/+264
|
* port client library to ValaRyan Lortie2010-07-191-620/+0
| | | | | | | | | | | | - the API is now completely implemented - update 'engine' API to be vala-bindable without annotations - update GSettings backend to new engine API - drop the readtype non-sense - build/api fixups for editor and commandline tool
* assorted client API cleanups, vala port of 'dconf'Ryan Lortie2010-07-181-19/+20
|
* Many improvementsRyan Lortie2010-07-151-1/+16
| | | | | | | | | | | | | | | | | | | | | | | - support the notion of 'profiles' This is how we will configure layering of databases in dconf. It's not wired-up yet (except to choose the name of the user database). - support multiple writers in the service Using the (very freshly API-broken) GDBus subtree support. Introspection returns the names of existing databases, but any object path can be used to create a new database. - support the start of the 'shm' file Used to prevent the reader from reopening the gvdb every time. dconf reads now involve zero system calls in the usual case. The server is queried on startup for the location of the shm files. By default, this is in ~/.cache/dconf/ for now. This won't work properly on NFS, but it's a start.
* gtk-doc cleanupsRyan Lortie2010-06-111-15/+22
|
* copyright commentsRyan Lortie2010-06-101-0/+40
|
* Switch from sequence numbers to tag stringsRyan Lortie2010-06-101-35/+104
|
* simplify API, add gobject-introspectionRyan Lortie2010-05-281-9/+95
|
* 'list' updatesRyan Lortie2010-05-241-2/+3
| | | | | - move to new GSettingsBackend API - add 'length' parameter, update callers
* Adapt to GDBus API changesRyan Lortie2010-05-241-31/+9
|
* client: implement write_many APIRyan Lortie2010-05-241-18/+43
|
* test async commands with the cmdline toolRyan Lortie2010-05-241-1/+1
| | | | fix a silly bug that the testing found
* proper CFLAGS, distcheck fixesRyan Lortie2010-05-231-6/+2
|
* more client library API, exposed by cmdline toolRyan Lortie2010-05-231-7/+36
|
* begin laying async support for DConfClientRyan Lortie2010-05-231-34/+198
|
* flesh out the APIs a bitRyan Lortie2010-05-231-4/+84
| | | | | - add a sync set() call to client API - GCancellable/GErrorify some APIs
* refactor, add client library, add 'dconf' commandRyan Lortie2010-05-221-0/+129
| | | | Only very preliminary functionality for all of these.
* rename client to engineRyan Lortie2010-05-211-172/+0
|
* factor-out common client-side codeRyan Lortie2010-05-211-0/+172
Preparing for creating standalone client-side library.
View Lorry Controller Status