On Wed, 2007-04-11 at 18:27 -0500, Daniel Espinosa wrote: > See other projects use Anjuta to create GObject templates, and you'll > see what I mean.
Daniel, you continue to indicate that you believe that we don't understand what a "proper" gobject looks like. Evidence that we do can be found in: - GncPlugins and GncPluginPages, which use gobject pretty "fully". - the GncTreeModel abstract util class, used by the GncTreeModelAccount and GncTreeModelPrice, as well as the corresponding Views. - the GncDenseCal widget and it's model interface, store implementation, and adapter-implementation. Much – but not all – of the new SX code, as well. - The gobject refcount-debugging code. - `find src -iname '*.c' |xargs grep -Hn "g_type_register_static" | grep "G_TYPE_OBJECT"` These might not use every feature of gobject, but sometimes there's no compelling reason to use every feature of gobject; properties come to mind. This is especially true with an existing code base such as GnuCash. -- ...jsled http://asynchronous.org/ - a=jsled;b=asynchronous.org; echo [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
_______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
