Debug Flags

[ianfhunter]

I think we should have some debug options when running the game, a lot of output is generated, and will probably continue to be generated later on, so it'd be good if we could reduce that.

Opinions? Is this a good/bad idea?

Made this for release 1.3 as it is very non-essential

[scottcunningham]

I agree, the app is very noisy and nothing really relevant to the user. On 18 Feb 2014 17:58, "Ian Hunter" notifications@github.com wrote:

I think we should have some debug options when running the game, a lot of output is generated, and will probably continue to be generated later on, so it'd be good if we could reduce that.

Opinions? Is this a good/bad idea?

Made this for release 1.3 as it is very non-essential

Reply to this email directly or view it on GitHubhttps://github.com/ianfhunter/TeamCrab/issues/16 .

[lardnerl]

Sure - all of the print commands are purely to see what is going on for debug purposes or just to see that stuff was happening before there was a ui. Removing them may mean we want to add more detail to the UI in terms of what is happening - so some way you can see either % of task done or number of man hours done / to do

On 18 February 2014 17:59, Scott Cunningham notifications@github.comwrote:

I agree, the app is very noisy and nothing really relevant to the user.

On 18 Feb 2014 17:58, "Ian Hunter" notifications@github.com wrote:

I think we should have some debug options when running the game, a lot of output is generated, and will probably continue to be generated later on, so it'd be good if we could reduce that.

Opinions? Is this a good/bad idea?

Made this for release 1.3 as it is very non-essential

Reply to this email directly or view it on GitHub< https://github.com/ianfhunter/TeamCrab/issues/16>

.

Reply to this email directly or view it on GitHubhttps://github.com/ianfhunter/TeamCrab/issues/16#issuecomment-35413283 .

[scottcunningham]

Decided in meeting that we'd add a class for debug printing that draws config from a command-line argument.

Pushing this forward to a later iteration.

On 18 February 2014 18:17, lardnerl notifications@github.com wrote:

Sure - all of the print commands are purely to see what is going on for debug purposes or just to see that stuff was happening before there was a ui. Removing them may mean we want to add more detail to the UI in terms of what is happening - so some way you can see either % of task done or number of man hours done / to do

On 18 February 2014 17:59, Scott Cunningham <notifications@github.com

wrote:

I agree, the app is very noisy and nothing really relevant to the user.

On 18 Feb 2014 17:58, "Ian Hunter" notifications@github.com wrote:

I think we should have some debug options when running the game, a lot of output is generated, and will probably continue to be generated later on, so it'd be good if we could reduce that.

Opinions? Is this a good/bad idea?

Made this for release 1.3 as it is very non-essential

Reply to this email directly or view it on GitHub< https://github.com/ianfhunter/TeamCrab/issues/16>

.

Reply to this email directly or view it on GitHub< https://github.com/ianfhunter/TeamCrab/issues/16#issuecomment-35413283>

.

Reply to this email directly or view it on GitHubhttps://github.com/ianfhunter/TeamCrab/issues/16#issuecomment-35415221 .

[ianfhunter]

Delaying this until next iteration(aka release1). Unless anyone explicitly wants to do it.

[ianfhunter]

Have implemented this as a command-line argument -q or --quiet. Currently suppresses all process simulator output & time. We might come back to this later, but it's done for now