[ggo-discussion] Re: A few newbee questions

* Peter Strempel wrote on Sun, Oct 05, 2003 at 01:13 +0200:
> On Sun, Oct 05, 2003 at 12:13:04AM +0200, Steffen Dettmer wrote:
>=20
> > I found GnuGo and from that, ggo as a nice client. I put
> > gnugo into /usr/local/bin (PATH is including it), but ggo
> > don't find it, no problem, I can set up the binary path at
> > the properties dialog.
>=20
> In theory gGo should find the "gnugo" command then. At least
> when you start it from the bash where $PATH is defined.

Yep, I do. From shell, gnugo starts in nice text mode :) For some
reason ggo seems to use a different PATH, at least not "my" PATH.
but anyway, not a problem so far.

> Maybe if you start it with an icon from KDE/Gnome the $PATH is
> skipped, no idea. However, no big deal, as you already wrote.

mmm... What's KDE? (just kidding)

> > Unfortunality, I don't know how to save the properties to a
> > file or how to create a properties file (by $EDITOR). Is
> > there a kind of example/template file?
>=20
> I don't exactly understand what you want to do.

Sorry. I just wanted ggo to remember my settings. Now I have to
enter the path and click the view settings each time I launch
it...

> gGo uses .properties files for the translations, but they ship
> with gGo already, bundled into the .jar file. No need for the
> end-user to edit these files. But I guess that's not what you
> had in mind, but I dont know what you had in mind. :)

No, I though there could be a file that holds e.g. the setting of
"path to gnu go" and the checkboxes of view options and so on.

When starting, I get a screen full of:
Failed to convert string to integer: java.lang.NumberFormatException: null
and
Failed to convert string to float: java.lang.NullPointerException
and though it's caused by a missing properties file or such.

> > "java.lang.OutOfMemoryError" occures in the .ggo.log (I think there is =
not
> > much someone can do about JDKs memory management
> > :(). Do I'm anything wrong? I use JDK-1.4.1.
>=20
> The default maximum memory for the JVM is 64 MB, which is more than
> sufficient to load and display Kogo.=20

mmm... Strange:

4124 steffen   16   0  105M 105M 17264 S     6.4 20.9   0:02 java

Now I set "-Xms256m -Xmx512m" (yeah, today's workstations have
512m phys mem...) and at it seems to work now... Well, who knows
why "my" JDK needs to much memory... mmm...

> Edit to:
> $JAVA -Xmx128m -jar /usr/local/gGo/lib/gGo.jar $@

THX, works for me.

> That would assign a maximum of 128 MB memory to the VM.
> However, I cannot explain why your system chokes with the
> default 64 MB. Even with Kogo, which sucks memory hard, 64 MB
> should be more than sufficient.

Java's memory management isn't working well I think... At work,
I have a CORBA component implemented in java. Basically, it has a
few (typical less than 100) hash maps with a few (10 - 50 each)
short (50 chars?) strings. Usually 64 MB ram or somewhat (after
weeks of uptime with heavily changing entries). So GC works, no
leaks... but sometimes, the 20th map creation gets an
outofmemory...  Really strange, really... Anyway, not the topic
here :)

> glGo is open source now, the latest release comes with
> sourcecode.=20

Ahh, nice :)

> You can try to compile yourself. :) The automake
> scripts are still a mess, I am trying to clean that up at the
> moment.  The new (and hopefully final) webpage for glGo is the
> old gGo project page at sourceforge: http://ggo.sourceforge.net

yep, this should help, I'll try it out when I'll find some time!
Thank you. BTW, autoconf/automake (especially autoconf) is always
a mess, isn't it :) ? But still the best tool out there I think...

> > Is the development of ggo affected by this or will it continue?
>=20
> gGo is currently quite dead. I cannot work on two clients on
> the same time.

yep, I see.

> I see glGo as a continuation of gGo, not as a really new
> client. My goal is basically to port the Java version
> completely to C++. Of course that will take much time. But I
> have no hurry. However, gGo 0.4 is pretty stable and usable.

oki, so glGo is a kind of successor.

> Maybe somebody wants to take over the gGo/Java development. But
> I simply lack the time and motivation to work on both. And
> blunty said, I dont feel obligated to work on any client at
> all. So if I dont want to, I dont do it. :)

Yep, you're perfectly right, that's the way it goes! Thank you
for every hour you already spent on providing this software to
the world!!

Thank you for your amazingly quick reply! Have a nice weekend!

oki,

Steffen

--=20
Dieses Schreiben wurde maschinell erstellt,
es tr=E4gt daher weder Unterschrift noch Siegel.

Other related posts: