I really, really, really hope this project isn't dead. If this project were to evolve into a KDE equivalent to XQF, that would be just SO awesome.
Oh, and for the record:
I like your current layout just fine, though I don't have a problem with XQF's.

minimize to systray and a splash screen would be nice :)

of course, both of them should be optional (via config menu).

see ya

I've just check your CVS changelog, downloaded your soft and it compiles like a charm now :)

As soon as you give us a new release, I'll create RPM's for Conectiva Linux and I'll send you the .spec file so you can distribute it with your code if you want to.

BTW: I've noticed that your app doesn't create a KDE menu entry. If you want to, I can create one and send it to you.

Thanks for the soft :)

Nice to have such program written in QT. I've just installed it and I have some comments for you:)
1. Maps SF Sandstorm and MOUT McKenna are always displayed no matter if I select them in map filter or not (it's displayed even if I don't select any map in map filter at all).
2. It would be nice to have separate columns: current players and max players, so the list can be sorted by each of this values.
3. I think there also should be a column for server version.

That's just my two cents. Good job soldier;)

is it possible to integrate the rest of the linux-native multiplayer games?

or to integrate your work into XQF (http://www.linuxgames.com/xqf/index.shtml).?

or to integrate XQF into your work :P ?

the point is: XQF is alredy there, but it's a GTK app. Now, don't get me wrong, but it doesnt make much sense to have TWO game server browsers (one that supports almos every game and other that supports only one...).

Yours looks quite better (too similar to the All Seeing Eye, which is fine by me!), but XQF is more complete, rock solid, has alredy been translated into many languages and it supports, basically, the rest of the online games (and then some more).

I think that if you could integrate your work with that of the XQF team THEN we have ONE KILLER APP.

Just an opinion ...

Anyways, while traying to create an RPM package for aabrowser, I came across this:

if g++ -DHAVE_CONFIG_H -I. -I. -I.. -DPACKAGE_DATA_DIR=\"/usr/lib/kde3/share/aabrowse\" -I/usr/lib/qt3/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -MT browsewindow.o -MD -MP -MF ".deps/browsewindow.Tpo" \
-c -o browsewindow.o `test -f 'browsewindow.cpp' || echo './'`browsewindow.cpp; \
then mv -f ".deps/browsewindow.Tpo" ".deps/browsewindow.Po"; \
else rm -f ".deps/browsewindow.Tpo"; exit 1; \
fi
browsewindow.cpp: En constructor `BrowseWindow::BrowseWindow()':
browsewindow.cpp:92: error: `setDisabled' undeclared (first use this function)
browsewindow.cpp:92: error: (Each undeclared identifier is reported only once
for each function it appears in.)
browsewindow.cpp: En member function `void BrowseWindow::checkActions()':
browsewindow.cpp:373: error: `setDisabled' undeclared (first use this function)
if g++ -DHAVE_CONFIG_H -I. -I. -I.. -DPACKAGE_DATA_DIR=\"/usr/lib/kde3/share/aabrowse\" -I/usr/lib/qt3/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -MT gsmsXMLdoc.o -MD -MP -MF ".deps/gsmsXMLdoc.Tpo" \
-c -o gsmsXMLdoc.o `test -f 'gsmsXMLdoc.cpp' || echo './'`gsmsXMLdoc.cpp; \
then mv -f ".deps/gsmsXMLdoc.Tpo" ".deps/gsmsXMLdoc.Po"; \
else rm -f ".deps/gsmsXMLdoc.Tpo"; exit 1; \
fi
browsewindow.cpp: En member function `void BrowseWindow::findServer(QString,
QString)':
browsewindow.cpp:641: error: `setDisabled' undeclared (first use this function)
browsewindow.cpp: En member function `void
BrowseWindow::serverRMB(QListViewItem*, const QPoint&, int)':
browsewindow.cpp:1483: error: `setDisabled' undeclared (first use this
function)
make[2]: *** [browsewindow.o] Error 1
make[2]: *** Se espera a que terminen otras tareas....
make[2]: Leaving directory `/home/gnemmi/paquetes/aabrowse/BUILD/aabrowse-0.0.7/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/gnemmi/paquetes/aabrowse/BUILD/aabrowse-0.0.7'
make: *** [all] Error 2
error: Bad exit status from /home/gnemmi/paquetes/aabrowse/BUILDROOT/rpm-tmp.32278 (%build)


RPM build errors:
Bad exit status from /home/gnemmi/paquetes/aabrowse/BUILDROOT/rpm-tmp.32278 (%build)

see ya :)

I'll fix those errors in CVS. It's supposed to compile with Qt 3.2 but I must be using something that was added in Qt 3.3

My app doesn't really add a lot compared to XQF, mainly the ability to fetch server lists from the gamespy master server and the Americas army specific filtering options. I'm guessing qstat doesn't support the gamespy master because you need to use some reverse engineered code to get it respond.

I'm thinking of starting a KDE server browser, as I prefer the ASE approach rather than XQF. Not sure if that will ever get anywhere though.

I would hate to see you stop developing on this application. We have needed a game browser for kde for a long time... and this easily looks like the best. That and I like the Gamespy/XQF style better than the all-seeing eye approach.

Please keep up the good work. I will be happy to send bug reports and patches if you are interested.

Bobby

"My app doesn't really add a lot compared to XQF ..."

I think it does !
* it's QT based :)
* extremly friendly to those who come from windows and are used to ASE (personally, and even though I really like XQF, I don't think it's THAT friendly for win newcomers)
* REALLY improves and boosts the whole gaming experience, which is a MUST on the whole Linux world.

"I'm thinking of starting a KDE server browser as I prefer the ASE approach rather than XQF"

Given the development state in wich XQF is, wouldn't it be better to work on it (port it/transform it/adapt it/uname it), than starting a whole new app?

I don't like the heavy qstat dependecy (given that qstat's development peace is rather slow and as a matter of fact it has been stalled for almost a year now or hasn't seen any major improvements) but still it certainly manages to get the job done.

Anyway, count me in for translations, rpm packaging, kde menus, bug reporting and whatever a non developer can help in :)

"Not sure if that will ever get anywhere though."

That would be REALLY REALLY REALLY (did I say REALLY?) sad indeed ...
You surely seem to have what it takes to develop that much needed ASE for Linux (KDE).

thanks for your kind attention
regards
gonzalo