G-Golf Core Reference modules and documentation structure and naming conventions are based, whenever it is possible, on the structure and naming conventions of the corresponding GNOME library.
To illustrate, let’s look at a few GLib, GObject and GObject Introspection sections and corresponding G-Golf sections and modules naming examples:
Glib
Memory AllocationMemory Allocation
(g-golf glib mem-alloc)The Main Event LoopThe Main Event Loop
(g-golf glib main-event-loop)…
GObject
Type InformationType Information
(g-golf gobject type-info)GObjectGObject
(g-golf gobject gobject)Enumeration and Flag TypesEnumeration and Flag Types
(g-golf gobject enum-flags)…
GObject Introspection
GIRepositoryRepository
(g-golf gi repository)common typesCommon Types
(g-golf gi common-types)GIBaseInfoBase Info
(g-golf gi base-info)…
Support to the G-Golf Core Reference modules themselves, or additional
functionality to G-Golf as a all, is organized and located in other
(none GNOME library based) modules, such as (g-golf support …),
g-golf override …) …