[Mono-bugs] [Bug 68549][Blo] New - Can't browse GTK# documentation with monodoc or the web frontend

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by cnehren@gmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=68549

--- shadow/68549	2004-10-19 12:53:37.000000000 -0400
+++ shadow/68549.tmp.18124	2004-10-19 12:53:37.000000000 -0400
@@ -0,0 +1,36 @@
+Bug#: 68549
+Product: Mono: Doctools
+Version: unspecified
+OS: other
+OS Details: Website and FreeBSD, probably others
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Blocker
+Component: Core
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: cnehren@gmail.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Can't browse GTK# documentation with monodoc or the web frontend
+
+I can't browse the GTK# documentation either via monodoc installed locally
+or via the official website. If I open it in the web frontend, I can't
+access the tutorial because there don't appear to be any links to it. Those
+things to which there are links are more often broken than not (though I
+suppose that that's a different bug report). When I attempt to browse the
+documentation offline in monodoc, there's no listing of the GTK# tutorial
+table of contents in the Contents node, and there are no "previous" and
+"next" navigation items in the nodes themselves. This means that I have to
+select a node, view it, then go back and select a new node. This is a very
+annoying and bass-ackwards methodology of viewing documentation, and it's
+preventing me and certainly others from learning GTK#. The fact that there
+doesn't appear to be any other way to read the GTK# tutorial (besides
+unzipping monohb.zip and viewing it in a browser, but I shouldn't have to
+do that -- and the "no navigation" item still applies) is a disappointment.
+I'm quite interested in this technology (Mono and .NET in general) and am
+working on getting it to function properly on FreeBSD. The fact that the
+documentation is difficult to navigate makes this process even more trying
+than it is otherwise.