After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 574252 - All GnomeMud components should be better GObjects.
All GnomeMud components should be better GObjects.
Status: RESOLVED OBSOLETE
Product: gnome-mud
Classification: Other
Component: general
0.11.x
Other Linux
: Normal normal
: ---
Assigned To: Les Harris
GNOME MUD Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-05 12:14 UTC by Les Harris
Modified: 2017-12-06 16:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Les Harris 2009-03-05 12:14:40 UTC
Right now most things in GnomeMud are GObjects.  But these aren't very good gobjects and ignore most of the benefits GObject provides.

Things which should be changed:
  * Get rid of explicit 'mud_foo_new' functions where able. g_object_new() should be used instead.

  * Convert private members to properties where it makes sense. We have alot of settings stuff that we pass to an object (with one of those 'mud_foo_new' functions) that then gets stored into our private data.  If we need to pass these things it would be better if we just made them parameters.

  * Explore use of signals.  Right now there are some complicated intertwining of our classes wherein pieces of one of them will call functions in another when some condition is filled.  These are obvious cases where using a signal might benefit.
Comment 1 GNOME Infrastructure Team 2017-12-06 16:27:23 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-mud/issues/9.