America's Army game browser - this one actually works!!

Message

feld · Post by **feld** » Tue Oct 19, 2004 5:15 pm

i reccomend you get aabrowse. this browser actually works. it communicates with the Gamespy servers and gets a list, and for an even more comprehensive list than what can be retrieved from them, there is an optional master server that is downloaded off of a text file which displays the current servers up. i dont know how it works, but someone scripted a way to use a way the game communicates with the master server and outputs it to a text file very regularly.

aabrowse 0.0.6 is on portage, but 0.0.7 is out. i just modified the ebulid with all references to 0.0.6 and changed them to 0.0.7 and saved as 0.0.7 and it works, just ebuild -filename.ebuild- digest and emerge it!

supports buddy list, filtering by map, game version, official and stuff, east west euro, etc. gives very accurate pings for me!

go get it!

-Feld

John5788 · Post by **John5788** » Tue Oct 19, 2004 11:42 pm

why do I need qt for this?

firephoto · Post by **firephoto** » Wed Oct 20, 2004 3:29 am

John5788 wrote:why do I need qt for this?

Because it is a Qt application.

Looks good, it's not picking up on some West servers but it could be a gamespy issue.

feld · Post by **feld** » Wed Oct 20, 2004 4:52 am

change Gamespy to the other one that starts with an "A"

it gets TONS of servers

-Feld

grover · Post by **grover** » Wed Oct 20, 2004 5:07 am

Emerge it with USE=geoip and it will display country flags for servers too.

I'm the author by the way

John5788 · Post by **John5788** » Wed Oct 20, 2004 5:09 am

grover wrote:Emerge it with USE=geoip and it will display country flags for servers too.

I'm the author by the way

could u possibly do a GTK version of it ??

grover · Post by **grover** » Wed Oct 20, 2004 5:23 am

No

I've never written anything with gtk before and don't have the time to learn at the moment.

The only real advantage aabrowse has over xqf is the ability to talk to the gamespy master server. I guess qstat doesn't include this because the code is reversed engineered and I'm not sure if its entirely legal. Should be fairly simple to add that support to qstat with a patch though. If I get bored on my uni holidays I might look into it.

firephoto · Post by **firephoto** » Wed Oct 20, 2004 5:47 am

I had an old ~/.aabrowse folder from the last time I tried it out so I think there was something in there it didn't like. I just deleted it and started fresh and I get the W servers it looks like now. I re-emerged it with the geoip flag too and that's really nice feature it adds to it. I love how Qt apps fit in so well with KDE, gives it a nice look n feel and this works really good too.

Excellent work!

plainzwalker · Post by **plainzwalker** » Thu Oct 28, 2004 12:33 pm

This doesnt want to emerge for me... I remember having problems with 0.0.6 as well... Here is what the end of the emerge with the error:

Code: Select all

ialog.moc.o gspyquery.moc.o newgspyquery.moc.o searchdialog.moc.o gsms.moc.o retrydialog.moc.o settingsdialog.moc.o buddylist.moc.o  -lqt-mt  -lz -lpng -lz -lm -lXext -lX11  -lSM -lICE -lpthread -lX11
make[2]: Leaving directory `/var/tmp/portage/aabrowse-0.0.7/work/aabrowse-0.0.7/src'
make[2]: Entering directory `/var/tmp/portage/aabrowse-0.0.7/work/aabrowse-0.0.7'
make[2]: Leaving directory `/var/tmp/portage/aabrowse-0.0.7/work/aabrowse-0.0.7'
make[1]: Leaving directory `/var/tmp/portage/aabrowse-0.0.7/work/aabrowse-0.0.7'
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-games-util_-_aabrowse-0.0.7-11153.log"

open_wr:   /usr/qt/3/etc/settings/.qtrc.lock
open_wr:   /usr/qt/3/etc/settings/.qtrc.lock
--------------------------------------------------------------------------------
root@plainzwalker aabrowse #

Any ideas?

Thanks
Jeff

nmcsween · Post by **nmcsween** » Thu Oct 28, 2004 7:23 pm

sandbox in your features? take it out.

plainzwalker · Post by **plainzwalker** » Thu Oct 28, 2004 7:44 pm

Nope, heres my Features section of make.conf

Thanks
Jeff

Code: Select all

# Advanced Features
# =================
#
# MAKEOPTS provides extra options that may be passed to 'make' when a
#     program is compiled. Presently the only use is for specifying
#     the number of parallel makes (-j) to perform. The suggested number
#     for parallel makes is CPUs+1.
#MAKEOPTS="-j2"
#
# AUTOCLEAN enables portage to automatically clean out older or overlapping
#     packages from the system after every successful merge. This is the
#     same as running 'emerge -c' after every merge. Set with: "yes" or "no".
#AUTOCLEAN="yes"
#
# FEATURES are settings that affect the functionality of portage. Most of
#     these settings are for developer use, but some are available to non-
#     developers as well. 'buildpkg' is an always-on setting for the emerge
#     flag of the same name. It causes binary packages to be created of all
#     packages that are merged.
FEATURES="candy"

# RSYNC_RETRIES sets the number of times portage will attempt to retrieve
#     a current portage tree before it exits with an error. This allows
#     for a more successful retrieval without user intervention most times.
#RSYNC_RETRIES="3"
CONFIG_PROTECT="/etc/init.d /etc/conf.d/net /etc/fstab /etc/apache /etc/samba"

firephoto · Post by **firephoto** » Thu Oct 28, 2004 8:58 pm

Add "-sandbox" to your features, it's most likely getting pulled in from somewhere else. You can do an "emerge info" to see if it's in there and I'm sure it is since the error was a sandbox error.

I did the same thing for another package a few weeks ago and and haven't turned the sandbox back on for whatever good or bad that might be.

plainzwalker · Post by **plainzwalker** » Thu Oct 28, 2004 9:30 pm

thank you firephoto, that did the trick.

Jeff

nmcsween · Post by **nmcsween** » Sat Oct 30, 2004 7:27 am

firephoto wrote:Add "-sandbox" to your features, it's most likely getting pulled in from somewhere else. You can do an "emerge info" to see if it's in there and I'm sure it is since the error was a sandbox error.

I did the same thing for another package a few weeks ago and and haven't turned the sandbox back on for whatever good or bad that might be.

sandboxing makes it so when building xyz it doesn't spit files all over the place