Re: Versasoft dBMAN for Linux
From: Christopher Browne (cbbrowne_at_acm.org)
Date: 31 Aug 2004 22:52:53 GMT
The world rejoiced as email@example.com wrote:
> In article <2pj8m2Flon5uU1@uni-berlin.de>, Christopher Browne says...
>>You may want to look at something available in "open source" form
>>rather than proprietary stuff like Kylix. Kylix only works with
>>specific Linux distribution releases with particular combinations of
>>libraries, and you might readily get into the same problem again five
>>years from now.
>>It would be most unfortunate to jump out of the dBMAN "frying pan"
>>into a fire...
> Good point Chris. I believe you have stabbed the heart of my
> delima. One of my several "starts" on this project was programming
> my UI under GNOME. I got a good start, but gave up when I didn't
> know how to connect to an SQL engine. Well I learned a lot about
> PostgreSQL while messing with Kylix. Now with Kylix only working
> with old and unsupported distributions, the embers of that fire you
> mentioned are flaring up!
> As for an up-to-date DB engine, this is a single user app. I think
> it could even be put on a Knoppix CD! But still the same issue of
> "five years from now" sounds much better for GNOME and PostgreSQL.
What's entirely regrettable is that it's a bit of a tough call on the
"GUI framework" side, too.
-> GNOME and KDE, with attendant GUI toolkits GTK and Qt, both
have the merit of being available as "free software," which
means you _should_ always be able to compile support libraries;
-> On the other hand, both have been evolving pretty quickly,
encouraging older versions to be treated as obsolescent,
which does some "boding ill."
I'd commend keeping in mind the thought:
"If I can't compile, from scratch, all of the components that this
depends on, then I'm at risk of getting severely screwed at some
That doesn't mean having to go with the "Slackware mentality" of
having to compile everything by hand from scratch; it just means being
sure that you _can_ recompile if need be. Debian packages, RPMs, or
BSD Ports are all decent ways to automate the "recompile stuff" part.
If I were writing a GUI application that I wanted to still be usable
five years from now, I might _slightly_ bias to GTK, over Qt, but only
by a bit.
-- output = ("cbbrowne" "@" "ntlug.org") http://www3.sympatico.ca/cbbrowne/linuxxian.html Signs of a Klingon Programmer #9: "Indentation?! -- I will show you how to indent when I indent your skull!"