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 611831 - Move documentation to inline comments: GtkVBox
Move documentation to inline comments: GtkVBox
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Documentation
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 599599
 
 
Reported: 2010-03-04 18:22 UTC by Steven Harms
Modified: 2010-04-18 06:21 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Move documentation to inline comments: GtkVBox (2.73 KB, patch)
2010-03-04 18:22 UTC, Steven Harms 		needs-work Details | Review
Update documentation for gtkvbox (2.77 KB, patch)
2010-03-04 21:03 UTC, Steven Harms 		committed Details | Review

Description Steven Harms 2010-03-04 18:22:26 UTC 
Created attachment 155251 [details] [review]
Move documentation to inline comments: GtkVBox

As described at http://live.gnome.org/GTK+/TaskAPIDocMigration
Comment 1 Javier Jardón (IRC: jjardon) 2010-03-04 19:54:30 UTC 
Review of attachment 155251 [details] [review]:

Fix the little issue, otherwise looks good

::: gtk/gtkvbox.c
@@ +68,3 @@
+ * @homogeneous: %TRUE if all children are to be given equal space allotments.
+ * gtk_vbox_new:
+/**

Try to use gtk-doc syntax to improve cross references
Here GtkVBox -> #GtkVBox

See http://library.gnome.org/devel/gtk-doc-manual/stable/documenting_syntax.html.en for more info
Comment 2 Steven Harms 2010-03-04 21:03:59 UTC 
Created attachment 155262 [details] [review]
Update documentation for gtkvbox

Updated for cross-references
Comment 3 Javier Jardón (IRC: jjardon) 2010-03-05 04:26:06 UTC 
Comment on attachment 155262 [details] [review]
Update documentation for gtkvbox

commit 3f579a7a936b9b6cbd08aa2331eae932b1a68491
Comment 4 Javier Jardón (IRC: jjardon) 2010-03-05 04:26:59 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release.

Thank you Steven!