<!DOCTYPE UI><UI version="3.3" stdsetdef="1">
<!DOCTYPE UI><UI version="3.2" stdsetdef="1">
Anyway, since i'm using only QT 3.3, it's the recommended version; but I think it should work fine with QT 3.2. - Aug 07 2004
Ubication \U`bi*ca"tion\, Ubiety \U*bi"e*ty\, n. [NL. ubicatio,
ubietas, fr. L. ubi where.]
The quality or state of being in a place; local relation;
position or location; whereness. [R.] --Glanvill.
So, I think "Kubication" is a right name. - Aug 07 2004
Coincidences doesn't exist. I have this idea rounding my mind some time ago. In fact, I started writing Kubication before noticing the existence of netGo. First time I saw your app, I though there had somethings I liked and others I disliked. For example, I liked the UI; but I disliked the way it stores data, the way it hanleds process (always run as root using su or kdesu), and something more.
So, I decided to speed up the development of Kubication and made the application I wanted. I had designed the UI using only an ugly big window and, as I liked yours, redesigned it following your concepts.
As for other similarities, I don't see anymore and IMHO there are lots of differences:
- Kubication uses the standard ./configure; make; make install building process while netGo uses a Makefile generated by qmake, which doesn't permit almost any customization (in fact I need to edit your Makefile to avoid an internal compiler error)
- Kubication uses KConfig for storing data in the _user_ settings, netGo uses a plaintext file for storing the settings _globally_ in a non-standard directory.
- Kubication supports dhcpcd, dhclient and pump while netGo only supports the first two.
- Kubication supports both wireless extensions and linux-wlan-ng while netGo only supports the first.
- Kubication has support for changing the SMTP, netGo doesn't.
- Kubication executes commands as root only when necessary and netGo runs always as root.
- Kubication uses kdelibs and qt while netGo is a pure qt app.
- Kubication has systray support, netGo hasn't.
- Kubication lets the user enter any interface, netGo parses /proc/net/dev and shows the available interfaces. In that way, it doesn't permit the user to configure profiles with removable interfaces that are not present.
- Kubication can bring down other interfaces, netGo can't.
There are at least 10 differences versus 1 similarity. Of course, I'm talking about the last releases, I haven't mentioned any of the features that are only in my repository nor haven't looked to yours.
About if Kubication is a clone of netGo, I think no. They are apps which do the same thing, both are behind the same idea; but they do things in very different ways. Think in Konqueror and Mozilla, both are web browsers, both had tabs, both support fs and ftp browsing, etc... but nobody says one is a clone of the other.
In short, all I can say is go on writing netGo, I will go on writing Kubications and we'll let the user choose :). Freedom of choice is one of the Open Source Software benefits, it isn't?.- Aug 02 2004
Regards - Aug 02 2004
- Jul 15 2004