[off topic only as much as the rest of this thread]
On Fri, Feb 23, 2007 at 02:57:11AM -0500, Freddie Unpenstein wrote:
> > Do the packagers read this list?
> > Do the maintainers read this list?
>
> I don't know. Do they? Do you know for a fact that none of them do? Do you
> know that none of
> > He shouldn't, but as a user of libglade who DID go and out figure
> > out how to use it (I do still have some "best libglade practices"
> > issues to figure out, though), I don't see why I can't back him up
> > in so far as what I see as a good point.
> Do the packagers read this list?
> Do th
On Wed, Feb 21, 2007 at 02:58:29AM -0500, Freddie Unpenstein wrote:
> > Surely we can agree that theres no point in asking the maintainers
> > of the tarball to please give better documentation and examples, if
> > you've never even looked at the tarball right ?
>
> He shouldn't, but as a user of
> > 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
On Mon, 2007-02-19 at 03:38 -0500, Freddie Unpenstein wrote:
> > what you MUST do, is download the tarball and see if the maintainer
> > included any helpfull files to help you understand how to use
> > the library, one of those helpfull files is test-libglade.c, a full
> > fledged example of all t
Time to dip my oar in the water...
On Sat, 2007-02-17 at 13:18 -0500, Gerald I. Evenden wrote:
> 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 f
> what you MUST do, is download the tarball and see if the maintainer
> included any helpfull files to help you understand how to use
> the library, one of those helpfull files is test-libglade.c, a full
> fledged example of all the uses of libglade.
I haven't been following this thread all too c
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 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
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 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 site:developer.
On Sat, 2007-02-17 at 11:49 -0500, Gerald I. Evenden wrote:
> >From a gnome.org web page there are four example programs from which I will
> select example2 as an sample of incomplete/non-existant documentation. See
Having addressed your points below, I have to disagree that the
documentation is
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 o
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
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
This is a side thread but I think some important issues are in question
On Thursday 15 February 2007 2:48 pm, Brian J. Tarricone wrote:
> 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 t
Quoting "Gerald I. Evenden" <[EMAIL PROTECTED]>:
> 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 manu
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, tutori
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://de
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/li
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
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 suggested
22 matches
Mail list logo
