Re: Alternative to glade?

Rainer Weikusat <rweikusat@xxxxxxxxxxx> writes:

Joe Pfeiffer <pfeiffer@xxxxxxxxxxx> writes:
Joris Dolderer <stdio@xxxxxxxxxx> writes:
On Tue, 25 Mar 2008 10:11:53 -0600, Joe Pfeiffer wrote:
You've got a bit of an unusual set of requirements: GTK, UI-builder,
generating C code. Note that the reason glade-2 is unsupported is that
they have moved on to an xml description-based approach with glade-3; so
why are you set on having the gui-builder write the code?
My program would have one extra dependency (libglade), less performance
(don't know how much but might be a bit), more executed code -> A bigger
chance a bug is in it and an increased size if you include the libglade
dependency. And I don't know why I should use such a system if I could
use simple C code.

Larger, true, but it's arguable that since more people are using
libglade your probability of a bug is actually lower (compared to
rolling your own).

At best, such a statement could be made about the past, insofar
statistic data backing it would be available. A structurally similar
claim would be that 'because more people develop for Windows than
develop for Linux, the probability of Windows-libraries having bugs is
lower than the probability of 'Linux-libraries' having bugs'. Without
some additional premises, this is just a non-sequitur.

Well, sure, but the additional premise is just that the libglade
developers are acting on user bug reports.
.

Relevant Pages

  • Re: Alternative to glade?
    ... Note that the reason glade-2 is unsupported is that ... My program would have one extra dependency (libglade), ... chance a bug is in it and an increased size if you include the libglade ... the probability of Windows-libraries having bugs is ...
    (comp.os.linux.development.apps)
  • Re: Alternative to glade?
    ... Note that the reason glade-2 is unsupported is that ... My program would have one extra dependency (libglade), ... chance a bug is in it and an increased size if you include the libglade ...
    (comp.os.linux.development.apps)
  • Re: Why less emphasis on private data?
    ... misunderstanding of probability, not to mention a shocking lack of common ... a bug that results from following just one of those paths. ... more reliable than the hardware you run it on. ... This is too convenient - This lead developer is about as likely as ...
    (comp.lang.python)
  • Re: Why less emphasis on private data?
    ... misunderstanding of probability, not to mention a shocking lack of common ... a bug that results from following just one of those paths. ... If it were easy to fix, the developer wouldn't even have mentioned it. ... And that mean free path increases without limit as the volume of the ...
    (comp.lang.python)
  • Re: Primality testing
    ... And you may remember the infamous Pentium bug. ... But the OP asked for a primality test with zero error, ... sure that the probability of error is exactly zero. ... mainframe I once used developed a strange pattern of errors. ...
    (sci.crypt)