[Libdexter-commits] SF.net SVN: libdexter:[389] libdexter/trunk/docs/reference/dexter/ dexter-docs.sgml

[<pk...@us...>]

Revision: 389
          http://libdexter.svn.sourceforge.net/libdexter/?rev=389&view=rev
Author:   pkovacs
Date:     2011-09-15 00:46:16 +0000 (Thu, 15 Sep 2011)
Log Message:
-----------
fix documentation links

Modified Paths:
--------------
    libdexter/trunk/docs/reference/dexter/dexter-docs.sgml

Modified: libdexter/trunk/docs/reference/dexter/dexter-docs.sgml
===================================================================
--- libdexter/trunk/docs/reference/dexter/dexter-docs.sgml	2011-09-15 00:03:22 UTC (rev 388)
+++ libdexter/trunk/docs/reference/dexter/dexter-docs.sgml	2011-09-15 00:46:16 UTC (rev 389)
@@ -81,9 +81,9 @@
     <para>
       One of the design goals for Libdexter is to make it easy-to-use, with clear, understandable library 
       functions and minimal external dependencies.  Libdexter was implemented in C using both the 
-      <ulink url="http://developer.gnome.org/doc/API/2.0/glib/index.html">GLib</ulink> Library
+      <ulink url="http://developer.gnome.org/glib/stable/">GLib</ulink> Library
       and the
-      <ulink url="http://developer.gnome.org/doc/API/2.0/gobject/index.html">GObject</ulink> 
+      <ulink url="http://developer.gnome.org/gobject/stable/gobject-The-Base-Object-Type.html">GObject</ulink> 
       object system.  I wanted to avoid "inflicting" GObject upon users of Libdexter, however,
       as that object system does have a learning curve for those completely unfamiliar with it.
       Accordingly, all of the GObject implementation details are hidden behind opaque structures.  

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.