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 166363 - Document standard macros and functions
Document standard macros and functions
Status: RESOLVED OBSOLETE
Product: gtk-doc
Classification: Platform
Component: general
unspecified
Other Linux
: High normal
: ---
Assigned To: gtk-doc maintainers
gtk-doc maintainers
Depends on:
Blocks:
 
 
Reported: 2005-02-05 12:54 UTC by Damon Chaplin
Modified: 2018-05-22 13:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Damon Chaplin 2005-02-05 12:54:31 UTC
We need to document the standard macros like these:

  GTK_ABOUT_DIALOG
  GTK_IS_ABOUT_DIALOG
  GTK_TYPE_ABOUT_DIALOG

  GTK_ABOUT_DIALOG_CLASS
  GTK_IS_ABOUT_DIALOG_CLASS
  GTK_ABOUT_DIALOG_GET_CLASS

  (gtk_about_dialog_get_type? - maybe we only show it if a macro like
  GTK_TYPE_ABOUT_DIALOG isn't defined for the widget)

I suggest placing them as a group at the bottom of the Synopsis, with links to a
page in the GObject docs that describes them.
Comment 1 Stefan Sauer (gstreamer, gtkdoc dev) 2005-08-24 16:53:13 UTC
shouldn't these just go to the private section? At least thats what gtk+ does.
The docs for GObject (G_OBJECT, G_IS_OBJECT and so on) are right now very
gobject specific. On the other hand glib-2.8 has the gobject tutorial included,
so we can link to that.
Comment 2 Matthias Clasen 2005-08-24 17:31:41 UTC
The idea for standard macros was, IIRC, to have a generic explanation of them
somehwere in the gobject docs, and then just link to there.
Comment 3 Stefan Sauer (gstreamer, gtkdoc dev) 2005-10-23 17:12:39 UTC
Now that the GObject-Tutorial is part of gobject api-docs I suggest to link
those to this chapter:
http://developer.gnome.org/doc/API/2.0/gobject/gtype-conventions.html

I would first change the gobject docs a bit to provide separate hrefs for each
macro (mimic a normal api page) and then come up with a patch for gtk-doc to
link to these docs.

Is that a good plan?
Comment 4 Damon Chaplin 2005-10-23 20:06:42 UTC
Yes, that sounds good.

(Though the title for that page is disappearing under the fixed navigation bar
for me, using epiphany. Is that a bug in the css code?)
Comment 5 Stefan Sauer (gstreamer, gtkdoc dev) 2006-03-21 10:46:45 UTC
fixed the css problem in cvs
Comment 6 Stefan Sauer (gstreamer, gtkdoc dev) 2011-09-05 14:50:47 UTC
It seems we should make sure the standard macros end up in the index.sgml. We could emit generic docs for them into object pages. 

Now we could just add those to the end of the page if the symbols are in the standard section, or otherwise just have the docs where the symbols are. Does that sound like a plan?

Anything that could go wrong with that plan?
Comment 7 GNOME Infrastructure Team 2018-05-22 13:00: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/gtk-doc/issues/2.