Hi Sébastien, I use some patterns like:
http://git.savannah.nongnu.org/cgit/gsequencer.git/tree/ags/audio/ags_recall_factory.h http://git.savannah.nongnu.org/cgit/gsequencer.git/tree/ags/plugin/ags_lv2_manager.h ... Or having an application context: http://git.savannah.nongnu.org/cgit/gsequencer.git/tree/ags/X/ags_xorg_application_context.h http://git.savannah.nongnu.org/cgit/gsequencer.git/tree/ags/thread/ags_concurrency_provider.h http://git.savannah.nongnu.org/cgit/gsequencer.git/tree/ags/audio/ags_sound_provider.h But what GObject makes really special are it's properties and events. Bests, Joël On Thu, Aug 10, 2017 at 2:23 PM, Sébastien Wilmet <swil...@gnome.org> wrote: > Hi, > > I've documented my first GObject design pattern: > https://blogs.gnome.org/swilmet/2017/08/09/gobject-design-pattern-attached-class-extension/ > > Question to the old-timers: do you know any other GObject-specific > design pattern? Not applying the classic design patterns with GObject, > I'm talking here about new design patterns that use GObject features > that are not necessarily present in other object systems. > > Or am I the first to write about a GObject-specific design pattern? > > Thanks, > Sébastien > _______________________________________________ > gtk-devel-list mailing list > gtk-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/gtk-devel-list _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list