From kde-devel Tue Jan 18 18:20:00 2000 From: "Michael J. Bedy" Date: Tue, 18 Jan 2000 18:20:00 +0000 To: kde-devel Subject: Re: Kash (joining the program in progress.) X-MARC-Message: https://marc.info/?l=kde-devel&m=94821973310334 I am not a database person either. This is why it took me a month to figure out what's going on :-) I think the documentation could be a little better organized, but that is a minor complaint. Compared to most free software it has outstanding documentation. I am using 1.24. I have not had any problems (that were not caused by myself.) I had to change a macro called METHOD to DBMETHOD so that it did not conflict with QT. - Mike On Tue, 18 Jan 2000, Roberto Alsina wrote: > On Tue, 18 Jan 2000, Michael J. Bedy wrote: > > > It might help to see what I mean if you browse through the readme.html > > file in the gigabase directory. It is very long, but the Introduction > > describes what it does. > > Well, some things in the file are a bit hard to get (say, the references > part?) maybe because I don't know enough DB stuff (or tyhe author's > english is not so good, it sure beats my russian anyway :-) > > Since we are in the topic of gigabase: what version are you using? > I am stuck at 1.1.15 because I get strange segfaults when trying to switch > to 1.1.24. Perhaps we should put together a package that builds gigabase > as a shared library? Something like kdesupport, probably. > > Gigabase is a really cool thing, and there are many places in KDE where > KConfig is being abused to do things Gigabase can do much better[1], it > needs to be known to more people! > > [1] Wherever you use KConfig to store the state of a class that has more > than, say, 2 or 3 members stored. > > ("\''/").__..-''"`-. . Roberto Alsina > `9_ 9 ) `-. ( ).`-._.`) ralsina@unl.edu.ar > (_Y_.)' ._ ) `._`. " -.-' Centro de Telematica > _..`-'_..-_/ /-'_.' Universidad Nacional del Litoral > (l)-'' ((i).' ((!.' Santa Fe - Argentina > KDE Developer (MFCH) > Not mad, but bound more than a madman is (Romeo and Juliet, Act I Scene II) >