colossus-developers Mailing List for Colossus (Page 2)

2015-08-26 21:54 GMT+02:00 Clemens Katzer <cle...@cl...>:

> > The current code cannot be compiled with java 6 unfortunately.
> Actually it can. The build file and the jnlp file say it needs 1.7, but
> there's nothing in the code that won't work with Java 5. As far as I
> know, at least :)
>

My java6 choked on "JComboBox<String>", isn't that new in 7?
I haven't done any java in a long time, I could be very wrong.

Cordially,

-- 
Romain Dolbeau

On 2015-08-26 21:54, Romain Dolbeau wrote:
> 2015-08-26 20:10 GMT+02:00 <sp...@ao... [1]>

...

> The current code cannot be compiled with java 6 unfortunately.

Actually it can. The build file and the jnlp file say it needs 1.7, but 
there's nothing in the code that won't work with Java 5. As far as I 
know, at least :)

So this one here was made by simply temporarily modifying build.xml and 
putting a jnlp file which says 1.5+ ...

http://www.play-colossus.net/colossus/play/


I went for 1.7 because I do not have 1.5 or 1.6 here, so I can't test 
anything with them, and (if I am not totally mistaken), even Java 7 has 
reached EOL. (so, in good old Colossus tradition, it's time to make this 
now the minimum requirement ;-)

I guess I will not enforce 1.7 then even yet, but I can't then test so 
well, so users using that version might encounter eventually strange 
issues....

Thx,
Clemens

2015-08-26 20:10 GMT+02:00 <sp...@ao...>

>       Your recent Java 7 upgrade makes me unable to play since I do not
> have anything more than Java 6 on this older computer.  Can you please post
> the old version using Java 6 on your web site again?
>
Colossus is one of the games me and my retired friends have been playing
> since we were a great deal younger.  If you can't do this, please accept
> our thanks for ages of delightful playing time.
>
>
The current code cannot be compiled with java 6 unfortunately.

However, the previous version is still available for download from SF.net:

<http://sourceforge.net/projects/colossus/files/Release-0.14.0/>

Download the ZIP file, unzip it, then double-click on "run.bat" inside the
newly create folder. I _think_ this should do the trick on Windows.

(all public builds are still available from <
http://sourceforge.net/projects/colossus/files>)

Cordially,

-- 
Romain Dolbeau

Hello,
 
      Your recent Java 7 upgrade makes me unable  to play since I do not 
have anything more than Java 6 on this older  computer.  Can you please post 
the old version using Java 6 on your web  site again?  Colossus is one of the 
games me and my retired friends have  been playing since we were a great 
deal younger.  If you can't do this,  please accept our thanks for ages of 
delightful playing time.
 
Steve

Hi all,

I have made a new build "20150805-01" (no real "versioning" at the 
moment).

Please give it a try!


All the Best,
Clemens

Thanks,

that's good to know!

Cheers,
Clemens


On 2015-08-01 19:57, John David Galt wrote:
> On Sun, 12 Jul 2015 at 13:56:26 -0400,
> David Ripton <dr...@ri...> wrote:
>> Rules say everyone gets the tower he rolled.  There is no choosing.
>
> True, but modified by options like "evenly spaced towers" which I 
> always
> use.  (Usually the way that works is that the first player in a 2 or 
> 3
> player game, or the first two in a 4 player game, determine *their*
> towers normally, and that tells everyone else which towers will not 
> be
> available as starting towers that game.
>
> Example: 4 player game.  First two players roll 5 and 1.  Therefore
> towers 3 and 6 will not be anyone's starting towers.)
>
> On Sun, Jul 12, 2015 at 23:13:15 +0300,
> Clemens Katzer <cle...@cl...> wrote:
>> Is there some "some towers are clearly [better] than others?"
>
> Towers 100 and 400 are the worst because on a roll of 2 or 5, two of 
> the
> three spaces you can move to are Swamp or Desert, so you get only one
> recruit.
>
> 200 and 500 are the best (in my view) because, at least against 
> computer
> players, I split my gargoyles, and on a 5 I can move one stack to 
> Brush
> and one to Jungle, recruiting with both.  2 is still a bad roll.
>
> 300 and 600 are in between.  Yes, on a 2 you can move to Jungle, but 
> to
> recruit with both stacks you have to send the other one to Hills or
> Woods (getting another tower creature) which is inferior no matter 
> how
> you split your legions.  In a 6 player game 600 has a second
> disadvantage -- no empty tower to teleport into.
>
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Colossus-developers mailing list
> Col...@li...
> https://lists.sourceforge.net/lists/listinfo/colossus-developers

On Sun, 12 Jul 2015 at 13:56:26 -0400,
David Ripton <dr...@ri...> wrote:
> Rules say everyone gets the tower he rolled.  There is no choosing.

True, but modified by options like "evenly spaced towers" which I always
use.  (Usually the way that works is that the first player in a 2 or 3
player game, or the first two in a 4 player game, determine *their*
towers normally, and that tells everyone else which towers will not be
available as starting towers that game.

Example: 4 player game.  First two players roll 5 and 1.  Therefore
towers 3 and 6 will not be anyone's starting towers.)

On Sun, Jul 12, 2015 at 23:13:15 +0300,
Clemens Katzer <cle...@cl...> wrote:
> Is there some "some towers are clearly [better] than others?"

Towers 100 and 400 are the worst because on a roll of 2 or 5, two of the
three spaces you can move to are Swamp or Desert, so you get only one
recruit.

200 and 500 are the best (in my view) because, at least against computer
players, I split my gargoyles, and on a 5 I can move one stack to Brush
and one to Jungle, recruiting with both.  2 is still a bad roll.

300 and 600 are in between.  Yes, on a 2 you can move to Jungle, but to
recruit with both stacks you have to send the other one to Hills or
Woods (getting another tower creature) which is inferior no matter how
you split your legions.  In a 6 player game 600 has a second
disadvantage -- no empty tower to teleport into.

The rules state :
"5.1 Each player rolls one die to determine which Tower Land his Legion
will begin in.  If players roll the same number or roll the number of a
Tower Land already assigned to another player, they must roll again."

So in your example :
> If there is a tie, let's say, 4, 6, 4, 3, ...
  then Players 1 and 3 re-roll until they roll a number other than 3 and 6
(and each other).

Whenever we played, we used to put chits 1 to 6 face down in the box lid,
and blindly pick one to allocate a tower (all that die rolling was
festerous in a 6-player game).

Cheers,
Brent.



Date: Sun, 12 Jul 2015 20:13:08 +0300
> From: Clemens Katzer <cle...@cl...>
> Subject: [Colossus-developers] Choosing towers
> To: Colossus DevelopersList
>         <col...@li...>
> Message-ID: <12e...@cl...>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
>
> Hi,
>
> just wondering (perhaps I'd implement it for Colossus), what is the
> "official" procedure for choosing towers? I remember we did it sometimes
> different ways
>
>     "everybody gets the tower of the number he rolled" vs.
>     "highest roll player can choose first."
>
> If there is a tie, let's say, 4, 6, 4, 3, then #2 can choose his tower
> already, #1 and #3 roll again until they roll differently, and when they
> have chosen then #4 can chose?
>
> Right?
>
> (will #2 choose already immediately, or are first all rolls done to
> determine order??)
>
>
>
> In such a "players choose themselves" scenario, is there use of
> enforcing balanced towers?
>       (or rather, is it somewhere practice to do so?)
> i.e. when first two chose  600 and 400, the other two can only take 100
> and 300?
>
> Otherwise, if #3 would take 200 (would he? or is 200 a rather bad
> starting tower?), whatever #4 chooses, it's a rather bad start for three
> players and one has good possibilities?
> ((Actually I believe he would, otherwise he is "for sure part of the 3
> beside each other crowd", but when he takes 200 he has a 33% chance of
> ending up as with best start chances...))
>
>
> Thx,
> Clemens
>

On Sun, Jul 12, 2015 at 23:13:15 +0300,
  Clemens Katzer <cle...@cl...> wrote:
>
>Is there some "some towers are clearly bwettere than others?"
3 and 6 are liked because having a jungle 2 away makes 2s a more
tolerable first roll. Higher numbers are better for getting first 
shot at recruiting.

On Sun, Jul 12, 2015 at 23:10:13 +0300,
  Clemens Katzer <cle...@cl...> wrote:
>
>
>On 2015-07-12 23:08, Clemens Katzer wrote:
>> All right, thanks for clarification!
>>
>> So if two towers are set, next player rolls... he might need to roll
>> several times until he has a number for a tower that is still free?
>>
>
>(sent too early)
>
>or would one then "if available" use dice with 4 sides ands map them to
>the 4 remaining free towers?

Yep. 20 siders could be used to roll for both when there are 5 and 4 
towers left. There probably better than 4 siders as they roll better. 
4 siders tend to land and stick.

On Sun, Jul 12, 2015 at 23:08:27 +0300,
  Clemens Katzer <cle...@cl...> wrote:
>
>All right, thanks for clarification!
>
>So if two towers are set, next player rolls... he might need to roll
>several times until he has a number for a tower that is still free?

If you are going by the rules literal. Most people will just make a 
high/low roll when at that point, so that you only need to roll once. 
However you should always make it clear what exactly you are rolling 
for before rolling, so that people don't think you are choosing schemes 
after the roll in order to gain an advantage.

Is there some "some towers are clearly bwettere than others?"

Theres something in my backhead,  600 is best, 400 and 200 little 
worse, but 100, 300.500  all three of them a significat disadvantage 
against the even numbers?

my memory anywhere overlapping with reality here....?  :-)

-Clemens


  2015-07-12 20:56, David Ripton wrote:
> On 07/12/2015 01:13 PM, Clemens Katzer wrote:
>
>> just wondering (perhaps I'd implement it for Colossus), what is the
>> "official" procedure for choosing towers? I remember we did it 
>> sometimes
>> different ways
>>
>>     "everybody gets the tower of the number he rolled" vs.
>>     "highest roll player can choose first."
>
> Rules say everyone gets the tower he rolled.  There is no choosing.

On 2015-07-12 23:08, Clemens Katzer wrote:
> All right, thanks for clarification!
>
> So if two towers are set, next player rolls... he might need to roll
> several times until he has a number for a tower that is still free?
>

(sent too early)

or would one then "if available" use dice with 4 sides ands map them to 
the 4 remaining free towers?



>
>
> On 2015-07-12 20:56, David Ripton wrote:
>> On 07/12/2015 01:13 PM, Clemens Katzer wrote:
>>
>>> just wondering (perhaps I'd implement it for Colossus), what is the
>>> "official" procedure for choosing towers? I remember we did it 
>>> sometimes
>>> different ways
>>>
>>>     "everybody gets the tower of the number he rolled" vs.
>>>     "highest roll player can choose first."
>>
>> Rules say everyone gets the tower he rolled.  There is no choosing.

All right, thanks for clarification!

So if two towers are set, next player rolls... he might need to roll 
several times until he has a number for a tower that is still free?



On 2015-07-12 20:56, David Ripton wrote:
> On 07/12/2015 01:13 PM, Clemens Katzer wrote:
>
>> just wondering (perhaps I'd implement it for Colossus), what is the
>> "official" procedure for choosing towers? I remember we did it 
>> sometimes
>> different ways
>>
>>     "everybody gets the tower of the number he rolled" vs.
>>     "highest roll player can choose first."
>
> Rules say everyone gets the tower he rolled.  There is no choosing.

On 07/12/2015 01:13 PM, Clemens Katzer wrote:

> just wondering (perhaps I'd implement it for Colossus), what is the 
> "official" procedure for choosing towers? I remember we did it sometimes 
> different ways
> 
>     "everybody gets the tower of the number he rolled" vs.
>     "highest roll player can choose first."

Rules say everyone gets the tower he rolled.  There is no choosing.

-- 
David Ripton    dr...@ri...

On Sun, Jul 12, 2015 at 20:13:08 +0300,
  Clemens Katzer <cle...@cl...> wrote:
>
>Hi,
>
>just wondering (perhaps I'd implement it for Colossus), what is the
>"official" procedure for choosing towers? I remember we did it sometimes
>different ways
>
>    "everybody gets the tower of the number he rolled" vs.

You get the tower you roll, not the one you choose.

>    "highest roll player can choose first."
>
>If there is a tie, let's say, 4, 6, 4, 3, then #2 can choose his tower
>already, #1 and #3 roll again until they roll differently, and when they
>have chosen then #4 can chose?
>
>Right?
>
>(will #2 choose already immediately, or are first all rolls done to
>determine order??)

In the above case the second roller will be in tower 6, the fourth player 
in tower 3 and the first and third rollers need to roll again.

This procedure is equivalent to the first roller getting one of 6 with 
equal probability, the second roller gets one of the remaing five towers 
with equal probability and so on. In practice many people use this system 
rather the the one in the rules to prevent haven't to roll lots of dice 
to get the last few towers. (If they don't dice with sides divisible by 
5 or 4, the second and/or third rollers may have to do rerolls, but 
fourth, fifth and sixth won't.)

Hi,

just wondering (perhaps I'd implement it for Colossus), what is the 
"official" procedure for choosing towers? I remember we did it sometimes 
different ways

    "everybody gets the tower of the number he rolled" vs.
    "highest roll player can choose first."

If there is a tie, let's say, 4, 6, 4, 3, then #2 can choose his tower 
already, #1 and #3 roll again until they roll differently, and when they 
have chosen then #4 can chose?

Right?

(will #2 choose already immediately, or are first all rolls done to 
determine order??)



In such a "players choose themselves" scenario, is there use of 
enforcing balanced towers?
      (or rather, is it somewhere practice to do so?)
i.e. when first two chose  600 and 400, the other two can only take 100 
and 300?

Otherwise, if #3 would take 200 (would he? or is 200 a rather bad 
starting tower?), whatever #4 chooses, it's a rather bad start for three 
players and one has good possibilities?
((Actually I believe he would, otherwise he is "for sure part of the 3 
beside each other crowd", but when he takes 200 he has a 33% chance of 
ending up as with best start chances...))


Thx,
Clemens

> usually this makes Eclipse take care of such things.
>

Oh. No, it doesn't. It puts the braces right if they are there ... but 
does not enforce them to be there :-/

Sorry for the misleading comment.

-C.


On 2015-06-30 16:37, Clemens Katzer wrote:
>> I think the coding standard is to always wrap blocks in curlies.
>
> Yep:
>
> http://colossus.sourceforge.net/docs/CodingStandards.html
>
>
>
> http://colossus.sourceforge.net/
>   =>   "The readme has more information.      The full docs are 
> here."
>         ==>     http://colossus.sourceforge.net/docs/index.html
>                 ===> "For Developers", item #2."
>
>
> Please try to enable "use project specific settings", usually this
> makes Eclipse take care of such things.
>
>
> Thx,
> Clemens
>
>
>
>
> On 2015-06-30 16:28, Barrie Treloar wrote:
>> In Colossus/core/src/main/java/net/sf/colossus/ai/SimpleAI.java [1]:
>>
>>> @@ -1845,6 +1845,10 @@ public SummonInfo summonAngel(Legion
>> summoner, List<Legion> donors)
>>>
>>> for (Legion legion : donors)
>>> {
>>> + // Do not summon an angel out of a small Titan stack
>>> + // (Late game it could be desirable, but this is a good start)
>>> + if (legion.hasTitan() && legion.getHeight() <= 5)
>>
>> I think the coding standard is to always wrap blocks in curlies.
>>
>> --
>> Reply to this email directly or view it on GitHub [2].
>>
>> 	*
>>
>> Links:
>> ------
>> [1]
>> https://github.com/cleka/colossus-titan/pull/2#discussion_r33571951
>> [2] https://github.com/cleka/colossus-titan/pull/2/files#r33571951
>
>
> 
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Colossus-developers mailing list
> Col...@li...
> https://lists.sourceforge.net/lists/listinfo/colossus-developers

> I think the coding standard is to always wrap blocks in curlies.

Yep:

http://colossus.sourceforge.net/docs/CodingStandards.html



http://colossus.sourceforge.net/
  =>   "The readme has more information.      The full docs are here."
        ==>     http://colossus.sourceforge.net/docs/index.html
                ===> "For Developers", item #2."


Please try to enable "use project specific settings", usually this 
makes Eclipse take care of such things.


Thx,
Clemens




On 2015-06-30 16:28, Barrie Treloar wrote:
> In Colossus/core/src/main/java/net/sf/colossus/ai/SimpleAI.java [1]:
>
>> @@ -1845,6 +1845,10 @@ public SummonInfo summonAngel(Legion
> summoner, List<Legion> donors)
>>
>> for (Legion legion : donors)
>> {
>> + // Do not summon an angel out of a small Titan stack
>> + // (Late game it could be desirable, but this is a good start)
>> + if (legion.hasTitan() && legion.getHeight() <= 5)
>
> I think the coding standard is to always wrap blocks in curlies.
>
> --
> Reply to this email directly or view it on GitHub [2].
>
> 	*
>
> Links:
> ------
> [1] 
> https://github.com/cleka/colossus-titan/pull/2#discussion_r33571951
> [2] https://github.com/cleka/colossus-titan/pull/2/files#r33571951

Hi folks,

I thought it's obvious, but to make "official": if anybody of the 
earlier developers wants to contribute "directly", just let me know, 
then I add him (somewhere ;-)

I just didn't want to add everybody by default, replicating the 
situation we had at sourceforge - 10 people listed as developers and 
nobobdy (me included) actually doing anything :)


All the best,
Clemens

 

 You can safely ignore that xset stuff. It's only to supress some
"beep" in the shell (I think ;-)

 The other looks like you compiled it
with/for Java 1.7 but try to run it with a Java 1.5. JRE. You can
probably get rid of that by "locally" editing the target version numbers
in "build.properties". (I changed it to 1.7 recently, which one do you
have? Did you do git pull recently?) 

 Thx,
 Clemens

On 06/15/2015
02:08 PM, Brent Jackson wrote: 

> Thanks for that.
> Got my cygwin set
up and can now "ant" to compile.
> However, "run" (and "./run") doesn't
work. It produces :
> 
>> ./run: line 1: xset: command not found
>>
java.lang.UnsupportedClassVersionError: net/sf/colossus/appmain/Start :
Unsupported major.minor version 51.0
>> at
java.lang.ClassLoader.defineClass1(Native Method)
>> at
java.lang.ClassLoader.defineClassCond(Unknown Source)
>> at
java.lang.ClassLoader.defineClass(Unknown Source)
>> at
java.security.SecureClassLoader.defineClass(Unknown Source)
>> at
java.net.URLClassLoader.defineClass(Unknown Source)
>> at
java.net.URLClassLoader.access$000(Unknown Source)
>> at
java.net.URLClassLoader$1.run(Unknown Source)
>> at
java.security.AccessController.doPrivileged(Native Method)
>> at
java.net.URLClassLoader.findClass(Unknown Source)
>> at
java.lang.ClassLoader.loadClass(Unknown Source)
>> at
sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
>> at
java.lang.ClassLoader.loadClass(Unknown Source)
>> Could not find the
main class: net.sf.colossus.appmain.Start. Program will exit.
>>
Exception in thread "main" ./run: line 3: xset: command not found
> So I
guess something's not right in my java set up.
> But I can double-click
on Colossus.jar to run it okay.
> So now to start reading me some
code.
> Regards, Brent.
> 
> On 10 June 2015 at 19:39, Clemens Katzer
<cle...@cl... [3]> wrote:
> 
>> On 2015-06-10 05:50, Brent
Jackson wrote:
>> 
>>> Hi. I am interested in doing some work on the
Colossus code.
>> 
>> Jippie!
>> 
>>> I have been unable to find any
information on the steps involved in
>>> getting involved.
>>> 
>>> To
date I have signed up to github, cloned the repository onto my
>>>
computer, and downloaded and installed Ant.
>>> 
>>> Now I should be
able to (compile and ?) run my local copy but I'm not
>>> sure how to do
that. I can run Ant in a shell, but I was expecting a
>>> GUI
interface.
>> 
>> Nope. It's really just ant. Although, some others run
Colossus from inside Eclipse, but I never got into the habit of doing
so.
>> 
>> Basically it is really simply:
>> 
>> git clone
gi...@gi...:cleka/colossus-titan.git [1]
>> cd
colossus-titan/Colossus/
>> ant clean jar
>> ./run
>> 
>> e.g.:
>> 
>>
[clemens@zotac tmp]$ git clone gi...@gi...:cleka/colossus-titan.git
[2]
>> Cloning into 'colossus-titan'...
>> remote: Counting objects:
56578, done.
>> remote: Compressing objects: 100% (2985/2985), done.
>>
remote: Total 56578 (delta 23), reused 23 (delta 23), pack-reused
53570
>> Receiving objects: 100% (56578/56578), 39.57 MiB | 1.38 MiB/s,
done.
>> Resolving deltas: 100% (28517/28517), done.
>> Checking
connectivity... done.
>> [clemens@zotac tmp]$ cd
colossus-titan/Colossus/
>> [clemens@zotac Colossus]$
>> [clemens@zotac
Colossus]$ ant clean jar
>> Buildfile:
/home/clemens/tmp/colossus-titan/Colossus/build.xml
>> 
>> cleanjars:
>>

>> clean:
>> 
>> init:
>> [mkdir] Created dir:
/home/clemens/tmp/colossus-titan/Colossus/build/ant/classes
>> [mkdir]
Created dir:
/home/clemens/tmp/colossus-titan/Colossus/build/ant/testresults
>> 
>>
compile:
>> [javac] Compiling 278 source files to
/home/clemens/tmp/colossus-titan/Colossus/build/ant/classes
>> [javac]
warning: [options] bootstrap class path not set in conjunction with
-source 1.7
>> [javac] 1 warning
>> 
>> compileVariants:
>> [javac]
Compiling 17 source files to
/home/clemens/tmp/colossus-titan/Colossus/build/ant/classes
>> [javac]
warning: [options] bootstrap class path not set in conjunction with
-source 1.7
>> [javac] 1 warning
>> 
>> jar:
>> [jar] Building jar:
/home/clemens/tmp/colossus-titan/Colossus/Colossus.jar
>> [jar] Updating
jar: /home/clemens/tmp/colossus-titan/Colossus/Colossus.jar
>> [jar]
Updating jar: /home/clemens/tmp/colossus-titan/Colossus/Colossus.jar
>>

>> BUILD SUCCESSFUL
>> Total time: 6 seconds
>> [clemens@zotac
Colossus]$ ./run
>> [clemens@zotac Colossus]$
>> 
>> Greetings,
>>
Clemens 
>> 
>>> 
> 
>
------------------------------------------------------------------------------
>

> _______________________________________________
>
Colossus-developers mailing list
>
Col...@li...
>
https://lists.sourceforge.net/lists/listinfo/colossus-developers



Links:
------
[1] mailto:gi...@gi...:cleka/colossus-titan.git
[2]
mailto:gi...@gi...:cleka/colossus-titan.git
[3]
mailto:cle...@cl...

Thanks for that.

Got my cygwin set up and can now "ant" to compile.

However, "run" (and "./run") doesn't work.  It produces :

> ./run: line 1: xset: command not found
> java.lang.UnsupportedClassVersionError: net/sf/colossus/appmain/Start :
> Unsupported major.minor version 51.0
>         at java.lang.ClassLoader.defineClass1(Native Method)
>         at java.lang.ClassLoader.defineClassCond(Unknown Source)
>         at java.lang.ClassLoader.defineClass(Unknown Source)
>         at java.security.SecureClassLoader.defineClass(Unknown Source)
>         at java.net.URLClassLoader.defineClass(Unknown Source)
>         at java.net.URLClassLoader.access$000(Unknown Source)
>         at java.net.URLClassLoader$1.run(Unknown Source)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at java.net.URLClassLoader.findClass(Unknown Source)
>         at java.lang.ClassLoader.loadClass(Unknown Source)
>         at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
>         at java.lang.ClassLoader.loadClass(Unknown Source)
> Could not find the main class: net.sf.colossus.appmain.Start. Program will
> exit.
> Exception in thread "main" ./run: line 3: xset: command not found
>

So I guess something's not right in my java set up.

But I can double-click on Colossus.jar to run it okay.

So now to start reading me some code.

Regards,
Brent.

On 10 June 2015 at 19:39, Clemens Katzer <cle...@cl...> wrote:

>
>
> On 2015-06-10 05:50, Brent Jackson wrote:
>
>> Hi.  I am interested in doing some work on the Colossus code.
>>
>
>
> Jippie!
>
>  I have been unable to find any information on the steps involved in
>> getting involved.
>>
>> To date I have signed up to github, cloned the repository onto my
>> computer, and downloaded and installed Ant.
>>
>> Now I should be able to (compile and ?) run my local copy but I'm not
>> sure how to do that.  I can run Ant in a shell, but I was expecting a
>> GUI interface.
>>
>
> Nope. It's really just ant. Although, some others run Colossus from inside
> Eclipse, but I never got into the habit of doing so.
>
> Basically it is really simply:
>
> git clone gi...@gi...:cleka/colossus-titan.git
> cd colossus-titan/Colossus/
> ant clean jar
> ./run
>
>
> e.g.:
>
> [clemens@zotac tmp]$ git clone gi...@gi...:cleka/colossus-titan.git
> Cloning into 'colossus-titan'...
> remote: Counting objects: 56578, done.
> remote: Compressing objects: 100% (2985/2985), done.
> remote: Total 56578 (delta 23), reused 23 (delta 23), pack-reused 53570
> Receiving objects: 100% (56578/56578), 39.57 MiB | 1.38 MiB/s, done.
> Resolving deltas: 100% (28517/28517), done.
> Checking connectivity... done.
> [clemens@zotac tmp]$ cd colossus-titan/Colossus/
> [clemens@zotac Colossus]$
> [clemens@zotac Colossus]$ ant clean jar
> Buildfile: /home/clemens/tmp/colossus-titan/Colossus/build.xml
>
> cleanjars:
>
> clean:
>
> init:
>     [mkdir] Created dir:
> /home/clemens/tmp/colossus-titan/Colossus/build/ant/classes
>     [mkdir] Created dir:
> /home/clemens/tmp/colossus-titan/Colossus/build/ant/testresults
>
> compile:
>     [javac] Compiling 278 source files to
> /home/clemens/tmp/colossus-titan/Colossus/build/ant/classes
>     [javac] warning: [options] bootstrap class path not set in conjunction
> with -source 1.7
>     [javac] 1 warning
>
> compileVariants:
>     [javac] Compiling 17 source files to
> /home/clemens/tmp/colossus-titan/Colossus/build/ant/classes
>     [javac] warning: [options] bootstrap class path not set in conjunction
> with -source 1.7
>     [javac] 1 warning
>
> jar:
>       [jar] Building jar:
> /home/clemens/tmp/colossus-titan/Colossus/Colossus.jar
>       [jar] Updating jar:
> /home/clemens/tmp/colossus-titan/Colossus/Colossus.jar
>       [jar] Updating jar:
> /home/clemens/tmp/colossus-titan/Colossus/Colossus.jar
>
> BUILD SUCCESSFUL
> Total time: 6 seconds
> [clemens@zotac Colossus]$ ./run
> [clemens@zotac Colossus]$
>
>
>
> Greetings,
> Clemens
>
>
>
>
>> Is Ant the right tool ?  The build.xml file in the repository says
>> so, but that may well be out of date.
>>
>> Regards,
>> Brent.
>>
>
>

On 2015-06-10 05:50, Brent Jackson wrote:
> Hi.  I am interested in doing some work on the Colossus code. 


Jippie!

> I have been unable to find any information on the steps involved in
> getting involved.
>
> To date I have signed up to github, cloned the repository onto my
> computer, and downloaded and installed Ant.
>
> Now I should be able to (compile and ?) run my local copy but I'm not
> sure how to do that.  I can run Ant in a shell, but I was expecting 
> a
> GUI interface.

Nope. It's really just ant. Although, some others run Colossus from 
inside Eclipse, but I never got into the habit of doing so.

Basically it is really simply:

git clone gi...@gi...:cleka/colossus-titan.git
cd colossus-titan/Colossus/
ant clean jar
./run


e.g.:

[clemens@zotac tmp]$ git clone gi...@gi...:cleka/colossus-titan.git
Cloning into 'colossus-titan'...
remote: Counting objects: 56578, done.
remote: Compressing objects: 100% (2985/2985), done.
remote: Total 56578 (delta 23), reused 23 (delta 23), pack-reused 53570
Receiving objects: 100% (56578/56578), 39.57 MiB | 1.38 MiB/s, done.
Resolving deltas: 100% (28517/28517), done.
Checking connectivity... done.
[clemens@zotac tmp]$ cd colossus-titan/Colossus/
[clemens@zotac Colossus]$
[clemens@zotac Colossus]$ ant clean jar
Buildfile: /home/clemens/tmp/colossus-titan/Colossus/build.xml

cleanjars:

clean:

init:
     [mkdir] Created dir: 
/home/clemens/tmp/colossus-titan/Colossus/build/ant/classes
     [mkdir] Created dir: 
/home/clemens/tmp/colossus-titan/Colossus/build/ant/testresults

compile:
     [javac] Compiling 278 source files to 
/home/clemens/tmp/colossus-titan/Colossus/build/ant/classes
     [javac] warning: [options] bootstrap class path not set in 
conjunction with -source 1.7
     [javac] 1 warning

compileVariants:
     [javac] Compiling 17 source files to 
/home/clemens/tmp/colossus-titan/Colossus/build/ant/classes
     [javac] warning: [options] bootstrap class path not set in 
conjunction with -source 1.7
     [javac] 1 warning

jar:
       [jar] Building jar: 
/home/clemens/tmp/colossus-titan/Colossus/Colossus.jar
       [jar] Updating jar: 
/home/clemens/tmp/colossus-titan/Colossus/Colossus.jar
       [jar] Updating jar: 
/home/clemens/tmp/colossus-titan/Colossus/Colossus.jar

BUILD SUCCESSFUL
Total time: 6 seconds
[clemens@zotac Colossus]$ ./run
[clemens@zotac Colossus]$



Greetings,
Clemens


>
> Is Ant the right tool ?  The build.xml file in the repository says
> so, but that may well be out of date.
>
> Regards,
> Brent.

>> Yes, Ant is still the right tool.

Yes.

I did some minor changes to build.xml to make it build with less 
warnings, and the thing is now mainly targeting for Java 1.7, trying to 
minimize warning noise related to that aspect, but that's about all.


>> Did you have a look in the htdocs directory?
>>
>> e.g.
>>
> 
> https://github.com/cleka/colossus-titan/blob/master/Colossus/htdocs/Building.html
>> [2]
>>
>> Having a look at those instructions it still talks about SVN, so a
>> really good first pull request would be to try and follow those docs
>> (and its great you are new) and enhance them to be relevant for
>> github and for current versions of tooling.

Yes, that would be one idea.

Though question is, is it better to first adjust the pages to reality 
and then
change tooling (use maven, perhaps use github jenkins, ... )  or vice 
versa  :>)


> I wonder whether it would be an opportunity to also use
> https://pages.github.com/ [4] for hosting those html pages?

Sure.

In case it's not obious, the status of all this is:

"I merely managed to move the trunk of the whole directory tree from 
Sourceforge-SVN to GitHub-git."

Even branches and tags I dropped, also Jani's "new Website" 
subdirectory.


So - all of that work of bringing documentation en par with reality is 
waiting for volunteers.

There were tentative plans to move to maven, not sure whether or when 
that will happen.

I, for myself, at the moment only add some features for which users on 
the public servers had asked.

(let me say it that way: for 1-2 years I had difficulties to motivate 
myself / find time
for *anything* related to Colossus, so for me it's important to keep 
going with something where
I am really motivated for; forcing myself now "to make the migration 
pretty" would most likely
get me stuck and not do anything for next 2 years again.)


Doing the sf => git part took me 3 weeks for something that could 
perhaps be done in 3 hours.

[though I spent lot of time trying whether / how to take branches and 
tags with, not really coming to an end result that I liked, so I dropped 
the idea. I am very bad at dropping history or throwing *anything* away, 
still in this case I, at the end, went for that approach. So it's not 
like I did only 3 hours, in practice I spent like 20 hours on it in 
those 3 weeks; still, in our age and stage of life ( 40+, family ;-) 
it's hard to scrap up 20 hours for a hobby thingy.....]


And that was motivated primarily by: "if it stays with svn, I am even 
less likely to bring up the patience to deal with it". So I would 
perhaps not do anything to it until I have really nothing else to do. 
Like, when I reach pension age, in about 20 years *gggg*



> I guess they are still browsable from a cloned repository, but they

Actually all those htdocs are browsable on the homepage:

http://colossus.sourceforge.net/


> The readme has more information.      The full docs are 
> ______here______.

http://colossus.sourceforge.net/docs/index.html



> aren't browsable from github in the browser - as it just displays the
> html as source.
>
> (Am I missing something)

:-)


(yes: the point what those pages are: they are that what is uploaded to 
home page, just version controlled here.

That, BTW, I was considering, could be changed, those docs could be a 
separate sub project).

> It is probably not worth turning them into markdown... but that would
> make them natively display in github.
>

Review and rewrite them, throwing the 50% obsolete stuff away would be 
better ;-)

Thx,
Clemens

On 10 June 2015 at 14:07, Barrie Treloar <bae...@gm...> wrote:

>
>
> On 10 June 2015 at 12:20, Brent Jackson <sal...@gm...> wrote:
>
>> Hi.  I am interested in doing some work on the Colossus code.  I have
>> been unable to find any information on the steps involved in getting
>> involved.
>>
>> To date I have signed up to github, cloned the repository onto my
>> computer, and downloaded and installed Ant.
>>
>> Now I should be able to (compile and ?) run my local copy but I'm not
>> sure how to do that.  I can run Ant in a shell, but I was expecting a GUI
>> interface.
>>
>> Is Ant the right tool ?  The build.xml file in the repository says so,
>> but that may well be out of date.
>>
>
> Yes, Ant is still the right tool.
>
> Did you have a look in the htdocs directory?
> e.g.
> https://github.com/cleka/colossus-titan/blob/master/Colossus/htdocs/Building.html
>
> Having a look at those instructions it still talks about SVN, so a really
> good first pull request would be to try and follow those docs (and its
> great you are new) and enhance them to be relevant for github and for
> current versions of tooling.
>

I wonder whether it would be an opportunity to also use
https://pages.github.com/ for hosting those html pages?

I guess they are still browsable from a cloned repository, but they aren't
browsable from github in the browser - as it just displays the html as
source.
(Am I missing something)

It is probably not worth turning them into markdown... but that would make
them natively display in github.