Especially since glade is pushing the use of libglade as THE
way to incorporate glade-produced layouts into applications,
libglade should be packaged so as to encourage just that. Not
make it hard for application developers to figure out how to use
it. In any case, this is more an issue
On Friday 16 February 2007 11:17 pm, Michael Torrie wrote:
On Fri, 2007-02-16 at 22:13 -0500, Gerald I. Evenden wrote:
I believe that much of the above and following issues are reasonably well
resolved but there are serious problems with the adequacy of some
sections (glib) but I will
Dear all,
I've learned how to use gtk by reading this documentation,
and other ressources found on the fly on the web; I've found
is extremely useful and well done, especially for a growing
project.
I am no C-guru, not even a computer scientist, and my
training is programming is twenty years
On Saturday 17 February 2007 12:16 pm, you wrote:
Gerald I. Evenden wrote on 02/17/2007 05:49 PM:
On line 72 in module main there is a reference to function
g_signal_connect. I cannot find any reference to this entry in the index
Have you tried typing g_signal_connect
On Saturday 17 February 2007 12:38 pm, Michael Torrie wrote:
...
My comments about information access is addressed on another email.
The example works just as it is supposed to. I get a pulsing progress
bar which, on my GTK theme, is a small blue rectangle that moves back
and forth
On Sat, 2007-02-17 at 13:18 -0500, Gerald I. Evenden wrote:
LOL
I give up! I throw in the towel.
Sorry to hear that. I believe that you could have found GTK programming
very rewarding. Note that I did not say libglade because I think you
had difficulties because you focused on libglade and
Geraldi,
I take notice of the following comment. I give up! I throw in the
towel. This is certainly your option, but I will tell you that your
experience with libglade is typical for persons who approach programming
the wrong way. Let me suggest an alternative that WILL yield different
and
On Fri, 2007-02-16 at 22:13 -0500, Gerald I. Evenden wrote:
I believe that much of the above and following issues are reasonably well
resolved but there are serious problems with the adequacy of some sections
(glib) but I will address these to a specific issue on a subsequent email
I'm not
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.
2. A side thread
On Thu, 2007-02-15 at 13:46 -0500, Gerald I. Evenden wrote:
[...]
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
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
Gerald I. Evenden wrote:
2. A side thread suggested that in order to understand the usage of a system
like libglade one should study the source.
I think that's pretty standard practice where any open source
library/development system is concerned. Having full reference
documentation,
12 matches
Mail list logo
