X-Git-Url: https://git.draconx.ca/gitweb/gob-dx.git/blobdiff_plain/e10d6e307623d0952f6e1f5d9fee8720ddab4808..1656cfade4879af0cb003e3847e58264caa5781f:/doc/gob.1.in diff --git a/doc/gob.1.in b/doc/gob.1.in index 40916fd..22c39f0 100644 --- a/doc/gob.1.in +++ b/doc/gob.1.in @@ -10,9 +10,9 @@ GOB \- The GTK+ Object Builder .SH SYNOPSIS .PP -.B gob [-?] [-h] [--help] [--version] [-w] [--exit-on-warn] -[--no-exit-on-warn] [--for-cpp] [--no-gnu] [--always-private-header] -[--no-private-header] [--no-touch-headers] file +.B gob +[ option ] ... +file .SH DESCRIPTION .PP GTK+ Object Builder is a simple preprocessor for easily creating @@ -548,6 +548,42 @@ argument lists and virtual and signal method names as it might confuse the PARENT_HANDLER macro. In fact avoiding all names with three underscores is the best policy when working with gob. +.SH USING GTK-DOC STYLE INLINE DOCUMENTATION +.PP +If you want to use gtk-doc style inline documentation for your objects, you +can do one of two things. First, you could include the inline documentation +comments in your %{ %} section which will then be put verbatim into the +output source file. This is the way you should use for functions you define +outside of the class. +.PP +For class methods, you should use a gtk+ style comment, however it can be +indented any number of tabs or spaces and you can use the short method name +without the type prefix. Gob will automatically try to extract these and +translate to full names and put them in the output source file. An example +would be: +.fi + + class Gtk:Button:Example from Gtk:Button { + /** + * new: + * + * Makes a new #GtkButtonExample widget + * + * Returns: a new widget + **/ + public + GtkWidget * + new(void) + { + return GTK_WIDGET(GET_NEW); + } + } + +.fi +If the function you are documenting is a signal or a virtual then it will +be documentating the wrapper that starts that virtual function or emits +that signal. + .SH DEALING WITH CIRCULAR HEADERS .PP Sometimes you may need to use an object of type MyObjectA in the MyObjectB