Hi; creating GObject classes with modern best practices is matter of calling:
G_DECLARE_FINAL_TYPE or: G_DECLARE_DERIVABLE_TYPE in your header file, and: G_DEFINE_TYPE in your source file. Anything else is usually dependent on what your class is going to contain; properties? Signals? A custom constructor? Private data? A singleton pattern for g_object_new()? Templating will get you only as far as you're going to make the template flexible enough. On 8 January 2018 at 19:07, Pavlo Solntsev <pavlo.solnt...@gmail.com> wrote: > I am open to comments and critics. Any suggestions are very welcome. I am > more than willing to see a tool like that as part of the glib library. You probably want to look at GNOME Builder's snippet functionality, if you want to generate code. Additionally, we had a UI tool ages ago called "Turbine", which was fairly flexible: https://git.gnome.org//browse/turbine You could fork it and update its templates. to follow best practices In general, though, I don't think we're going to have this tool shipped as part of GLib; after all, we have never landed an interface definition language to generate code either. Ciao, Emmanuele. -- https://www.bassi.io [@] ebassi [@gmail.com] _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
