| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
GTK lost it's '+' suffix back in 2019, according to
<https://mail.gnome.org/archives/gtk-devel-list/2019-February/msg00000.html>
This commit can be re-generated with:
git grep -l GTK+ \
| grep -v -e ^NEWS -e ^glib/tests/collate.c \
| xargs sed -i 's/GTK+/GTK/g'
Most of the changes are in comments and documentation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The documentation previously implicitly said in a few places that
interfaces are classed, but reading through the implementation of
`GType`, I don’t think they are. If they were, the registration of the
fundamental `G_TYPE_INTERFACE` in `gobject_init()` would specify
`G_TYPE_FLAG_CLASSED`. It only specifies `G_TYPE_FLAG_DERIVABLE`.
I think this makes sense, because you can’t subclass an interface.
Subclassing is a key property of being classed.
Tweak the `GType` tutorial to remove that implicit statement, and expand
the documentation for `G_TYPE_IS_CLASSED`.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
Fixes: #252
|
|
|
|
|
|
|
| |
Make it a bit clearer in the documentation that using
`G_PARAM_STATIC_STRINGS` everywhere is a good thing.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
|
|
|
|
|
|
| |
Rather than using a mixture of ‘instantiable’ and ‘instantiatable’
everywhere, standardise on the term which is already in the public API.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The example code defines an interface with three methods. The preceding text
reads 'This interface defines two methods'. This appears to be because the
example code was changed without updating the surrounding text.
https://bugzilla.gnome.org/show_bug.cgi?id=790830
|
|
|
|
|
|
|
|
| |
It's unnecessary, and only adds visual noise; we have been fairly
inconsistent in the past, but the semi-colon-less version clearly
dominates in the code base.
https://bugzilla.gnome.org/show_bug.cgi?id=669355
|
|
|
|
|
|
|
|
| |
Change it to a running example of a file viewer application with a file
class and various derived classes and related interfaces. Hopefully the
reader can relate to this a little better than to their maman.
https://bugzilla.gnome.org/show_bug.cgi?id=753935
|
|
|
|
|
|
|
| |
The libffi one is slower than type-specific generated ones, but is
generally better to use.
https://bugzilla.gnome.org/show_bug.cgi?id=744060
|
|
|
|
|
|
| |
They’re the new vogue for handling signals.
https://bugzilla.gnome.org/show_bug.cgi?id=744060
|
|
|
|
|
|
| |
Make it obvious the parameter is not related to AClass.
https://bugzilla.gnome.org/show_bug.cgi?id=744060
|
|
|
|
|
|
|
| |
Not setting a pure vfunc is a programmer error, so can be handled with a
g_return_if_fail() rather than needing a g_warning().
https://bugzilla.gnome.org/show_bug.cgi?id=744060
|
|
|
|
|
|
|
|
| |
Use G_DECLARE_INTERFACE and G_DEFINE_INTERFACE. Fix a couple of typos.
Add some comments to empty functions to make it obvious they’re
intentionally empty.
https://bugzilla.gnome.org/show_bug.cgi?id=744060
|
|
|
|
|
|
| |
Use get_instance_private().
https://bugzilla.gnome.org/show_bug.cgi?id=744060
|
|
|
|
|
|
| |
Be a bit more consistent about property enum numbering.
https://bugzilla.gnome.org/show_bug.cgi?id=744060
|
|
|
|
|
|
|
|
|
| |
• Consistently make all titles sentence case
• Fix various typos
• Remove an unnecessary footnote
• Remove first person phrasing
https://bugzilla.gnome.org/show_bug.cgi?id=744060
|
|
|
|
|
|
| |
Unused, outdated, and unsalvagable.
https://bugzilla.gnome.org/show_bug.cgi?id=744060
|
|
|
|
|
|
| |
Break the text up a little with some formatting.
https://bugzilla.gnome.org/show_bug.cgi?id=744060
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Restructure the section of the how-to which covers the header and source
code boilerplate for declaring and defining GObjects to use the new
G_DECLARE_*_TYPE macros. Present both final and derivable types.
Trim various supporting paragraphs.
Rename ‘class functions’ to ‘virtual functions’ to use consistent,
modern terminology.
https://bugzilla.gnome.org/show_bug.cgi?id=744060
|
|
|
|
|
|
|
| |
These are in the header boilerplate section, but are actually source
boilerplate which is covered in later sections.
https://bugzilla.gnome.org/show_bug.cgi?id=744060
|
|
|
|
|
|
| |
ISO-8859-1 — that’s a blast from the past.
https://bugzilla.gnome.org/show_bug.cgi?id=744060
|
|
|
|
|
|
| |
It is no longer atomic.
https://bugzilla.gnome.org/show_bug.cgi?id=741589
|
|
|
|
|
|
| |
In the sections Concepts, Tools and Tutorial.
https://bugzilla.gnome.org/show_bug.cgi?id=736914
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=731979
|
|
|
|
|
|
|
|
|
|
| |
On initialisation, GObject guarantees to zero-fill
class/object/interface structures. Document this so people don’t spend
forever writing:
my_object->priv->some_member = NULL;
my_object->priv->some_other_member = NULL;
https://bugzilla.gnome.org/show_bug.cgi?id=729167
|
| |
|
|
|
|
|
|
|
| |
As it turns out, we have examples of internal functions called
type_name_get_private() in the wild (especially among older libraries),
so we need to use a name for the per-instance private data getter
function that hopefully won't conflict with anything.
|
|
|
|
|
|
|
|
| |
Started off by using the new instance private data macro, ended up
cleaning up the obscure, out of date, or simply broken concepts and
paragraphs.
https://bugzilla.gnome.org/show_bug.cgi?id=700035
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=692848
|
|
|
|
|
| |
This makes all the subsection headers consistent.
https://bugzilla.gnome.org/show_bug.cgi?id=659428
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Document how to override interfaces already implemented
in a base class, and also call those base class implementations
from a derived reimplementation.
* Don't recomend people use base_init() style functions to
initialize interface signals and properties, use default_init()
aka class_init() instead (as G_DEFINE_INTERFACE() uses).
* The above solves the interface init called multiple times
problem, so remove some needless naysaying about that.
* Document default_init() in the interface initialization discussion
* Linkify more stuff.
* Remove some crud and typos
https://bugzilla.gnome.org/show_bug.cgi?id=675504
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Either g_type_register_static_simple (used by G_DEFINE_TYPE_EXTENDED)
and G_IMPLEMENT_INTERFACE use automatic variables for GTypeInfo and
GInterfaceInfo structs, while tutorials and source code often use
static variables. This commit consistently adopts the former method.
https://bugzilla.gnome.org/show_bug.cgi?id=600161
|
|
|
|
|
|
| |
Some links were broken due to typos, because functionality was removed
in GLib 2.0 or for various other reasons. Fix up as many of them as is
reasonable.
|
| |
|
|
|
|
| |
We use 'pspec' instead of 'maman_param_spec' elsewhere too.
|
|
|
|
| |
'type' must be inside of 'link'.
|
| |
|
| |
|
|
|
|
| |
svn path=/trunk/; revision=7757
|
|
|
|
| |
svn path=/trunk/; revision=7707
|
|
|
|
| |
svn path=/trunk/; revision=7201
|
|
|
|
|
|
|
| |
* gobject/tut_howto.xml: Fix a formatting glitch
svn path=/trunk/; revision=6900
|
|
|
|
|
|
| |
* gobject/tut_howto.xml: Add missing *.
svn path=/trunk/; revision=6829
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2007-11-13 Cody Russell <bratsche@gnome.org>
* docs/reference/gobject/gobject-docs.sgml:
* docs/reference/gobject/tut_gsignal.xml:
* docs/reference/gobject/tut_gtype.xml:
* docs/reference/gobject/tut_intro.xml:
* docs/reference/gobject/tut_tools.xml:
* docs/reference/gobject/tut_howto.xml:
* docs/reference/gobject/tut_gobject.xml: Documentation fixes.
Recommend macro type names such as NAUTILUS_TYPE_WINDOW (not
NAUTILUS_WINDOW_TYPE). Fixed text which erroneously stated that
superclass initializers don't run when an object is
instantiated. Fixed numerous spelling mistakes. Minor grammar
edits. (#490637, Adam Dingle)
svn path=/trunk/; revision=5857
|