summaryrefslogtreecommitdiff
path: root/client
Commit message (Collapse)AuthorAgeFilesLines
...
* Massively reorganise the client-sideRyan Lortie2012-07-027-539/+121
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-012-4/+264
|
* common/: create two convenience librariesRyan Lortie2012-07-011-3/+1
| | | | | | | One -fPIC and one without. This is done instead of pulling the various source files from other Makefiles.
* client: clean up some Vala issuesRyan Lortie2012-02-051-13/+7
| | | | | | We had a workaround for a Vala bug that has been fixed, so remove that. Add another workaround because Vala cannot be certain that a particular value has been set or not (so just set it to null to stop the warning).
* engine: drop some dead filesRyan Lortie2012-02-051-1/+1
|
* Silence some harmless warnings from vala codeRyan Lortie2011-11-211-1/+1
|
* Finish removing 'set_locked'Ryan Lortie2011-09-191-15/+0
| | | | A few leftovers from the tear-out: docs and header file.
* Remove "service func" logicRyan Lortie2011-09-112-14/+0
| | | | | | This was required to support the case where the dconf client was unable to determine the cache directory for itself. Since we now use the XDG runtime directory, this is redundant.
* Remove 'set lock' support from dconfRyan Lortie2011-09-111-42/+0
| | | | | | | | | | | | | | | | | | The dconf service can not presently be run at the system level and it doesn't make sense to support locks on user-level databases. It also became clear that most distributors and sysadmins would rather work directly with text files anyway, so we supported that directly instead. For this reason, 'set lock' support has never been properly implemented. All the plumbing was added for it though, which means we have it appearing on the API of the client library and documented in the help of the commandline tool. This is misleading, since these functions do nothing at all (and actually contain bugs anyway since their do-nothingness was never actually tested). For now, we rip out these functions. We can add them back later if we decide to support this properly.
* Properly support watching in DConfClientRyan Lortie2011-05-101-0/+30
|
* Don't compare VariantType by pointer valueRyan Lortie2011-05-101-1/+1
|
* Fix up CLEANFILES for both librariesRyan Lortie2011-01-181-1/+1
|
* One more linker fixRyan Lortie2011-01-181-1/+2
|
* Disable gobject-introspection supportRyan Lortie2010-12-211-19/+1
| | | | | It's not usable for libdconf anyway (due to lack of GVariant support in the bindings) and it keeps causing build problems.
* Reduce GDBus abuseRyan Lortie2010-12-182-19/+21
| | | | Use our own private thread instead
* -Wno-error for dconf clientRyan Lortie2010-11-021-0/+1
| | | | Dodge vala codegen buglets.
* introspection: fix dconf-1.0.gir build with g-i masterDiego Escalante Urrelo2010-09-071-1/+1
| | | | Bug #628845
* Tweak shared library installationRyan Lortie2010-08-082-10/+16
| | | | | | ldconfig gets angry if it finds the soname not to be a symlink. So, install libdconf.so.0.0.0 and symlink libdconf.so.0 to that.
* bump .gir version to dconf-1.0Ryan Lortie2010-08-051-7/+7
|
* More cleanups and gtk-doc fill-inRyan Lortie2010-08-036-27/+248
|
* set_lock -> set_locked and cleanup gtk-docRyan Lortie2010-08-034-9/+130
| | | | | | | | 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.
* Introspection fixupsRyan Lortie2010-07-271-0/+1
| | | | | | | | I just pushed a patch to gobject-introspection to have the scanner compilation set an -rpath= if --no-libtool is specified. Specify --no-libtool here and bump our dependency to the latest gobject-introspection (not yet released).
* Add missing $(DESTDIR)Ryan Lortie2010-07-241-1/+1
| | | | 'make distcheck' has a pretty neat check that uncovered this.
* Installing symlinks doesn't work -- use a hookRyan Lortie2010-07-241-1/+4
|
* Remove Vala 'dconf.deps' from tree on 'make clean'Ryan Lortie2010-07-241-1/+1
| | | | | This file left in the tree breaks 'make distcheck' which ensures that the tree is clean after 'make clean' runs.
* Get rid of libtoolRyan Lortie2010-07-242-8/+15
| | | | | | | | | | | You need to type 'make clean' before trying to rebuild dconf after this update (in fact, 'git clean' may be appropriate to clean out all the extra files that libtool leaves around). It's quite likely that this completely breaks dconf builds on non-ELF platforms (and maybe some ELF ones). Please report any problems to bugzilla. I'm very happy to accept patches to fix portability (via ./configure-time checks).
* dist the generated .vapiRyan Lortie2010-07-191-0/+1
| | | | so people can install it without requiring valac
* bring service API in line with the clientRyan Lortie2010-07-191-15/+33
| | | | | also, cache GDBusConnections in the client since GDBus doesn't keep them alive for us.
* port client library to ValaRyan Lortie2010-07-197-686/+199
| | | | | | | | | | | | - 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-182-6/+6
|
* assorted client API cleanups, vala port of 'dconf'Ryan Lortie2010-07-183-35/+87
|
* Move shmdir guessing code to common/Ryan Lortie2010-07-171-0/+1
| | | | | | | Increase the intelligence of the algorithm: use ~/.cache/dconf as a reasonable default if not on NFS. The dconf engine now has a non-blocking startup when not on NFS.
* 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.
* conditionalise use of gobject-introspectionRyan Lortie2010-06-171-9/+11
|
* gtk-doc cleanupsRyan Lortie2010-06-112-21/+28
|
* copyright commentsRyan Lortie2010-06-103-0/+82
|
* Switch from sequence numbers to tag stringsRyan Lortie2010-06-102-39/+121
|
* FreeBSD: Don't use {a,b,c} expansion in MakefilesRyan Lortie2010-06-021-1/+1
|
* Remove ResetList and ReadType from client APIRyan Lortie2010-05-283-5/+1
|
* simplify API, add gobject-introspectionRyan Lortie2010-05-283-12/+118
|
* add pkgconfig file for libdconfRyan Lortie2010-05-242-0/+14
|
* 'list' updatesRyan Lortie2010-05-242-3/+5
| | | | | - 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-242-18/+47
|
* 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-233-9/+29
|
* more client library API, exposed by cmdline toolRyan Lortie2010-05-231-7/+36
|
* begin laying async support for DConfClientRyan Lortie2010-05-232-34/+200
|
* flesh out the APIs a bitRyan Lortie2010-05-232-4/+86
| | | | | - add a sync set() call to client API - GCancellable/GErrorify some APIs
* refactor, add client library, add 'dconf' commandRyan Lortie2010-05-224-0/+233
| | | | Only very preliminary functionality for all of these.
View Lorry Controller Status