| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=654812
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=677652
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=677653
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=675928
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=655046
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Add i18n support using intltool and glib-gettext (to avoid the
well-known issues with vanilla gettext).
This patch is heavily based on a patch by Gabor Kelemen.
https://bugzilla.gnome.org/show_bug.cgi?id=642217
|
|
|
|
|
|
| |
Various bits of UI used "dconf Editor" and others "DConf Editor". Use
"dconf" consistently. Remove a lone instance of "Configuration Editor"
as well.
|
|
|
|
|
|
|
|
|
| |
Mark UI strings for translation.
The various warnings that are issued as a result of errors while parsing
schemas have not been marked for translation because they are never
shown in the UI (only via g_warning()) and because they are expected to
be removed soon.
|
|
|
|
|
| |
We were issuing a g_critical() on failing to load the GtkBuilder xml
files which isn't very helpful. Just abort with g_error().
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
bin/dconf-dump.vala
configure.ac
editor/Makefile.am
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix the vapi file to properly describe the changed signal (including the
possibility of NULL tag).
Change the dconf tool's implementation of the signal handler (and
simplify it due to the changed semantics of the signal).
Do the same for the editor.
|
| |
| |
| |
| | |
And fit the .gitignore over the same issue, as well.
|
| |
| |
| |
| |
| |
| |
| | |
Disable C compiler warnings entirely while building Vala code.
Fix-up a couple of legitimate issues plus one false-positive
(in service.c).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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).
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
visible on selected entry
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=650631
|
| |
|
|
|
|
|
|
| |
We had some '#if VALA_0_14' guards for compatibility with older Vala
versions. We're a far way from being able to build with valac 0.12, so
drop those.
|
|
|
|
|
|
| |
Drop the 14x14 and 92x92 icons.
https://bugzilla.gnome.org/show_bug.cgi?id=669154
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Let dconf-editor show in the applications list. If someone installed it
then it is appropriate for them to see it.
|
|
|
|
|
|
|
|
|
|
| |
Vala 0.13 (leading toward 0.14) corrects an error in the binding for
GtkTreeModel. Unfortunately, the correction is incompatible and there
is no way to have code that will work with both old and new Vala
compilers.
Rather than hard-depend on the unstable Vala release, just use two
separate declarations decided on #if VALA_0_14.
|
|
|
|
|
|
|
| |
Watch for changes to DConf and update the view. This is not done in the
most elegant or efficient way, but it's simple and it works.
https://bugzilla.gnome.org/show_bug.cgi?id=649443
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=645611
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=622292
|
|
|
|
| |
Based on a patch from Fabian Deutsch <fabian.deutsch@gmx.de>
|
| |
|
| |
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=641293
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=641293
|
|
|
|
|
|
| |
enums from being loaded.
Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=636880
|
|
|
|
|
| |
The code will fail badly if it encounters a 'flags' key in a schema, so
add a very minimal workaround to deal with that.
|
|
|
|
|
|
| |
The name "Configuration Editor" is too confusingly generic.
Fixes #643894.
|