Re: Alternative to glade?

Joe Pfeiffer <pfeiffer@xxxxxxxxxxx> writes:
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.

There are more, at least that

- past libglade users used it in sufficiently similar ways
to the OP to have found all the bugs that could affect the
OP

- all those bugs have been reported correctly

- libglade developers have already (and correctly) fixed all
of those bugs in the release the OP would be using

- the OP is a 'bad enough' programmer with enough 'bad luck'
to write more bugs into a simple piece of code than the
libglader programmers wrote into a complicated piece of code

Another relevant aspect would be 'assuming the OP does encounter a
libglade bug, how much effort is need upon his part to understand the
more-general-than-needed code sufficiently well to fix the bug on his
own[*], vs how much effort would have to be spent fixing 'other bugs'
in code being both simpler and more familiar to him [because he wrote
it].

[*] Reporting bugs to 'OSS projects' will typically result in
being ignored or being flamed by someone presently feeling
bored or upset that 'someone else' dared to claim there would
be a bug. Therefore, using 'OSS code' necessitates to be
prepared to fix any potential issue as needed. Especially,
taking into account that being ignored or flamed is the usual
reaction to bug reports including patches, too.

Unless the 'OSS project' provides something which is
technically complicated enough that reimplementing the
actually needed parts of it would take 'a long time' (eg the
Linux-kernel or Samba), the IMO best course of action is to
not use the 'OSS project' unless one is specifically getting
paid to waste time quarrelling with non-desirables on public
mailing lists.
.

Relevant Pages

  • Re: Praise for Gfortran (finally)
    ... I think the typical way one gets deeply involved with gfortran ... One gets involved in fixing bugs ... One starts writting bigger patches & reviews other patches ... Bug reports and feature requests for ...
    (comp.lang.fortran)
  • Re: Attn : Dave Jones Re: I just want one more option in the FC Kernels (Dave Jones)
    ... they not only wouldn't be reporting the bugs but they wouldn't have ... > don't think that's the point of the Fedora Project itself. ... I have no complaints about the bugs being there in the first place). ... Then no one should complain about continuing to get bug reports about ...
    (Fedora)
  • Re: Jetico BestCrypt Volume Encryption
    ... the motivation behind the OSS project is not "to contribute to public" ... and the only time you see them fix critical things (e.g. reported ... or maintenance bugs still go uncleaned. ... Open source is better in that they fix the noteworthy bugs sooner than ...
    (sci.crypt)
  • Re: Microsoft tries to polish a turd
    ... schedule fixes. ... reports are not bugs, but user problems. ... Software companies expect a predictable number of bug reports from ... I have some rather specific issues with Vista. ...
    (sci.electronics.design)
  • [opensuse] Re: new man behavior: "ask questions instead of answer": HOWTO REVERT?
    ... I put alot more into bug reports than I usually ... But response is _better_ on SuSE projects & products ... But am generally a medium-core bug-filer, especially for bugs with no ... severity (annoyance & workaround provided), ...
    (SuSE)