Re: libglade frustration redux

[Michael L Torrie <torriem chem byu edu>]

I have made a major mistake here.  Apparently google is indexing the old
libglade-1.0 stuff rather than the new stuff.  The 2.0 docs are here:

http://developer.gnome.org/doc/API/2.0/libglade/index.html

Note that for any gnome-related library, you can find the api and
reference docs at:

http://developer.gnome.org/doc/API/

Michael



On Thu, 2007-02-15 at 12:27 -0700, Michael L Torrie wrote:
> On Thu, 2007-02-15 at 13:46 -0500, Gerald I. Evenden wrote:
> > A the originator of this thread I will rephrase my problems and make a larger 
> > scale complaint.
> >
> > 1. My original complaint was compile/linking glade output.  Thanks to M. 
> > Torrie this problem was nicely solved and I can compile/link several examples 
> > from various sources.
>
> In the future, please be specific as to what compiler options you have
> tried and what error messages were given to you.
>
> > 2. A side thread suggested that in order to understand the usage of a system 
> > like libglade one should study the source.  Hmmm.  To use the C (or any 
> > compiler) I should study the source code for the compiler???  To use the math 
> > library I should study the library's source??  I did mess with the mathlib 
> > source many years ago when the function 'hypot' was poorly implemented but I 
> > have not done such a thing since.  And read the C compiler code for 
> > understanding of how to use C---you have to be kidding.
> >
> > 3. Getting back to libglade.  I have searched through many pages of google to 
> > find either a decent reference and/or tutorial for libglade.  A couple of 
> > tutorials make halfway attempts but ultimately fail because they have no 
> > reference manual to rely on---among other failings.  Finding a libglade 
> > reference manual is a total failure.  There are a couple of sites which claim 
> > to be a reference manual but I find them totally inadequate.  There is NO 
> > reference manual for libglade that can compared to what is available for GTK.  
> > Even the GTK reference is questionable as I find reference to GTK functions 
> > that are not in the GTK index nor locatable in sections dealing with the 
> > widget involved.
>
> In fairness, the API reference for libglade is complete and fine.  It's
> only three calls.  Easy to use.  There are a plethora of complete
> examples of libglade usage out on the web.  I found several good ones
> using google.  They include complete glade files, the .c file, and
> compilation instructions.  
>
> I really don't know why you are saying there are no decent tutorials or
> references.  Have you looked at the libglade docs on the web?  
> http://developer.gnome.org/doc/API/libglade/libglade.html
>
> In fact, a complete example, complete with compilation instructions is
> at:
> http://developer.gnome.org/doc/API/libglade/libglade-notes.html#LIBGLADE-BASICS
>
> During the 5 minutes I spent doing some research to answer your original
> post, I encountered a problem with their example code where the auto
> signal connect routine would complain that it couldn't find symbols.  I
> punched the error message into google and learned very quickly that I
> had to add a compiler flag to allow the symbols to be found (can't
> remember offhand now what it was).
>
> So I don't think we can say the docs are bad or hard to find.  They
> really aren't.
>
>
> > I would love to be proved wrong about libglade documentation so please flame 
> > me if I am and point out my sins.  Even though I am now able to compile/link 
> > libglade code I find that I am now stymied by lack of documentation on its 
> > usage. 
>
> After seeing the documentation, what parts of you stymied by?
>
> Michael
>
>
> _______________________________________________
> gtk-app-devel-list mailing list
> gtk-app-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list