On Sun, Aug 13, 2017 at 01:20:14PM +0200, Joël Krähemann wrote:
> The AgsApplicationContext acts as a base entry point to your
> application. It is an extensible singleton
> where functions are added by interfaces.
>
> In order to use libags-thread.so.0 you have to implement
>
Hi,
The AgsApplicationContext acts as a base entry point to your
application. It is an extensible singleton
where functions are added by interfaces.
In order to use libags-thread.so.0 you have to implement
AgsConcurrencyProvider provider in your application context.
Likewise for
On Thu, Aug 10, 2017 at 02:39:12PM +0200, Joël Krähemann wrote:
> 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
On Fri, Aug 11, 2017 at 09:16:32AM +0700, Arnaud wrote:
> As for using the `g_object_set_data()` like you do, it's something I
> always tried to stay away from, because it seems to me that everything
> becomes possible with that, and there's probably plenty of mistakes to
> be made ;) On the other
On 8/11/2017 5:16 AM, Arnaud wrote:
> Hi Sébastien,
>
> thx for this post ! I'm a newby with GObject, and I'm always happy to
> learn bits here and there.
>
> As for using the `g_object_set_data()` like you do, it's something I
> always tried to stay away from, because it seems to me that
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:
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
