| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
| |
These suggestions came up in code review.
|
|
|
|
|
|
|
| |
APIs such as the Gio.AppInfo.get_id vfunc which contravene this advice,
can cause memory leaks. (See
https://gitlab.gnome.org/GNOME/gjs/-/issues/519)
Document it here so that it hopefully happens less often in the future.
|
|
|
|
|
|
| |
This includes the new points from Emmanuele's recent blog post
https://www.bassi.io/articles/2023/02/20/bindable-api-2023/
into the "Writing Bindable APIs" doc.
|
| |
|
|
|
|
|
| |
Add a disambiguation of what to return and do with the out values in case an
error is thrown.
|
|
|
|
|
| |
Add the (copy-func) and (free-func) annotations to the documentation,
and the copy-function and free-function attributes to the GIR schema.
|
|
|
|
|
|
|
| |
An escape hatch to specify a freeform string for the default value of a
property.
Fixes: #4
|
| |
|
|
|
|
|
|
| |
Signals that have an emitter function should have an annotation to allow
consumers of the introspection XML to effectively pair signals to their
corresponding emitter functions that share the same prototype.
|
|
|
|
|
|
|
|
|
| |
To avoid introducing additional strictness onto unsuspecting libraries,
we introduce a new mode: "strict".
The strict mode is opt-in, and used to signal potential issues with the
public API once exposed by language bindings, even when it's fully
introspectable.
|
| |
|
|
|
|
|
|
| |
Don't use a real function to describe optional/nullable differences, to avoid getting into
the weeds when it comes to edge cases.
Fixes: #211
|
|
|
|
|
| |
Remove mentions of Autotools: we only support Meson.
Fixes: #327
|
|
|
|
| |
Do not use the snapshot of the old developer.gnome.org website.
|
|
|
|
|
| |
Do not use the snapshot of the old developer.gnome.org website; we
generate and publish the API reference ourselves.
|
|
|
|
|
|
|
|
| |
The `set-property` and `get-property` identifier annotations only apply
to methods.
The `setter` and `getter` identifier annotations only apply to
properties.
|
|
|
|
|
| |
Public accessor functions are the functions typically called through
g_object_set_property() and g_object_get_property().
|
| |
|
|
|
|
|
| |
Mention them in the annotations list, and add the new attributes to the
GIR schema.
|
|
|
|
|
|
|
| |
The GNOME developers documentation website has been updated, and we're
in the process of moving API references elsewhere. The old documentation
is still available under developer-old.gnome.org, so let's update the
URLs we have in our documentation.
|
| |
|
| |
|
|
|
|
| |
We don't use them any more; discussions happen on Discourse.
|
|
|
|
|
| |
This is a trap that C APIs can fall into, so it should be mentioned on
the "Writing Bindable APIs" page.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The libgirepository example now is its own meson project.
There now is a small library that is buildable with meson and autotools
which creates a gir/typelib. Usefull for testing our build system integration
and for small experiments.
Fixes #287
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
My goal here is to keep it simple and get people started quickly.
See !96
|
|
|
|
| |
glib versions leaked
|
|
|
|
|
| |
So it's visible on the main website and has nice links to the
issues and merge requests.
|
|
The current output (more or less a straight copy of the wiki) is available
here:
https://gi.readthedocs.io
This contains two changes:
* Converts all (not completely outdated) wiki pages to a sphinx based
documentation.
* Converts the man pages to reST and adds a Makefile for building them
using rst2man. So they can be easily exposed in the sphinx docs.
Goals:
* Have a user focused/compact documentation instead of random wiki pages
with various todo/ideas pages.
* Take advantage of the gitlab MR workflow by
* allowing large documentation changes/refactorings with reviews
* allowing to combine features changes with documentation changes in MRs
|