summaryrefslogtreecommitdiff
path: root/client/dconf-client.h
Commit message (Collapse)AuthorAgeFilesLines
* client: restrict list_locks to work on dirsAllison Ryan Lortie2015-12-161-1/+1
| | | | | | | 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.
* client: replace _read_default() with _read_full()Allison Ryan Lortie2015-12-161-2/+5
| | | | | | | | | 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
* Modernise the headers of dconf-clientAllison Ryan Lortie2015-11-301-7/+2
| | | | | | | 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
* engine, client: add list_locks() operationAllison Ryan Lortie2015-11-301-0/+4
| | | | | | | 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/+3
| | | | | | | | 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
|
* Reimplement sync() functionalityRyan Lortie2012-07-101-0/+2
| | | | | | | | | 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.
* 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).
* Massively reorganise the client-sideRyan Lortie2012-07-021-66/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Finish removing 'set_locked'Ryan Lortie2011-09-191-15/+0
| | | | A few leftovers from the tear-out: docs and header file.
* More cleanups and gtk-doc fill-inRyan Lortie2010-08-031-13/+14
|
* set_lock -> set_locked and cleanup gtk-docRyan Lortie2010-08-031-3/+3
| | | | | | | | Rename set_lock to set_locked again (and same SetLock -> SetLocked). Add missing gtk-doc bits, clean up some that are no longer there. Bump gtk-doc dependency.
* port client library to ValaRyan Lortie2010-07-191-4/+9
| | | | | | | | | | | | - 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
* header cleanupRyan Lortie2010-07-181-3/+3
|
* assorted client API cleanups, vala port of 'dconf'Ryan Lortie2010-07-181-16/+7
|
* gtk-doc cleanupsRyan Lortie2010-06-111-6/+6
|
* copyright commentsRyan Lortie2010-06-101-0/+21
|
* Switch from sequence numbers to tag stringsRyan Lortie2010-06-101-4/+17
|
* Remove ResetList and ReadType from client APIRyan Lortie2010-05-281-2/+0
|
* simplify API, add gobject-introspectionRyan Lortie2010-05-281-3/+6
|
* 'list' updatesRyan Lortie2010-05-241-1/+2
| | | | | - move to new GSettingsBackend API - add 'length' parameter, update callers
* client: implement write_many APIRyan Lortie2010-05-241-0/+4
|
* proper CFLAGS, distcheck fixesRyan Lortie2010-05-231-1/+15
|
* begin laying async support for DConfClientRyan Lortie2010-05-231-0/+2
|
* flesh out the APIs a bitRyan Lortie2010-05-231-0/+2
| | | | | - add a sync set() call to client API - GCancellable/GErrorify some APIs
* refactor, add client library, add 'dconf' commandRyan Lortie2010-05-221-0/+90
| | | | Only very preliminary functionality for all of these.
* rename client to engineRyan Lortie2010-05-211-74/+0
|
* factor-out common client-side codeRyan Lortie2010-05-211-0/+74
Preparing for creating standalone client-side library.
View Lorry Controller Status