What steps will reproduce the problem?
1. Play game until at least one predefined ship design become available (colony 
ship should be available from beginning).
2. Save game.
3. Load game.

What is the expected output?
Same ship designs prior and after loading game.

What do you see instead?
Available predefined ship designs are duplicated after loading game.

Proposition for following:

Building queue UI accepts changes in building queue on every kind of window 
closing, not just "accept" button.

Version 0.3 requirement

Division of planet size to surface size and orbit size.

Concept proposed mainly because of gas giants. Unlike rocky planets and 
asteroids, gas giants don't have colonizable surface. Instead they usually have 
large moons that can populated. To make gas giants less special case, moons and 
orbital habitation is proposed. It would be good to avoid explicit 
manifestation of moons and incorporate then in some simpler concept. In that 
manner division of planet size to surface and orbital size is proposed.

While planetary "surface" is colonizable from the beginning, colonizing orbit 
requires technology. Cost of living on surface is determined by atmospheric 
conditions and stellar radiation and can be regulated through terraforming and 
shielding. On the other hand orbit can't be terraformed (due the lack of terra 
part) and cost of living is dependant on orbital habitation technologies.

For rocky planets, "surface" is combined surface of planet and it's moons and 
"orbit" is orbit of both planet and moons. Asteroids in this proposal are 
considered purely orbital case with zero surface size. Gas giants have 
"surface" on moons and "orbit" around main planet body and moons. Although gas 
giants have considerable volume of atmosphere, to keep things simpler, it 
shouldn't not be taken in consideration.

By dividing planets to surface and orbit, concept of mining also needs to be 
updated. Orbits of rocky worlds should not be place to do mining while "orbits" 
of asteroids and gas giants can be. In this proposal asteroids are considered 
to be surfaceless orbit, but that doesn't mean they can't be mined. To cover 
that option mineral abundance of orbit is proposed. Gas giants can have solid 
core that can be mined too but only after overcoming crushing atmosphere. So, 
to cover that option too, condition on orbital mining ability is proposed. As 
surface mining has mining depth that interpolates between shallow and deep 
mining so should orbital mining be affected by some factor of capability.

Version 0.3 requirement.

- Issuing and performing interstellar travel.
- Generation and application of "starlanes".

Version 0.3 requirement

Support for multiple languages.

Version 0.2 requirement

Adding more pictures for planets and implementation of picture choosing 
algorithm. 1-NN (nearest neighbor) algorithm is proposed.

Version 0.4 requirement

When designing ship, multiple ship pictures should be available. It should be 
done as multiple images per ship hull size.

Currently component descriptions are displayed at two different places, 
technology library and ship designer and both use similar but separate code. 
That code should be extracted and made reusable.

Version 0.4 requirement

Colony info window should be redone in a way to show only important data. 
Details such as how is something calculated should be available by clicking or 
hovering mouse over already shown data.

Version 0.4 requirement

List of planets should be reworked to support more data per planet (development 
bar, picture, name, population)

Proposition for following:

Separate intelligence and cartographic data from Igrac class.

Version 0.3 requirement

Implementation of system wide effects (same way they are defined for colony and 
empire scope). Migration limit would be one of such effects. Some values might 
also be visible on GUI.

Proposition for redoing mining calculus.

Before implementing orbital habitation, concept of mining has to be redesigned. 
Currently miner efficiency is 1 + planet's ore abundance multiplied by industry 
worker efficiency. New model should resemble more to traditional model where 
miner efficiency is proportional to ore abundance on planet and unaffected by 
industry efficiency.

Also, habitation and building maintenance should have special treatment, like 
using less ore.

What steps will reproduce the problem?
1. Open fleet movement window
2. Click on empty spot on map

What is the expected output?
Nothing or map scrolling.

What do you see instead?
Null pointer exception is thrown. After mouse click code searches for nearest 
star in 0.5 ly radius (game/map coordinates :)) and sets it as fleet 
destination. If there is no star in 0.5 ly radius, null is returned.

Version 0.2 requirement.

Mechanism for upgrading ship designs as new technologies become available.

Proposition for following:

In current model, percentage of farmers is directly proportional with farmer 
productivity which in turn depends only on technologies and employment rate. 
Idea is to make farmer productivity (and consequently percentage of farmers) 
dependent upon population size. Larger population would require 
disproportionaly more farming effort.

Let's say that dropoff starts when number of farmers is greater then 1/10 of 
colony's base max. pop. Farmers working in second 1/10 would suffer penalty to 
their productivity, those working in third 1/10 would suffer even greater 
penalty and so on.

Example:
Let's chose something like 2^-x as dropoff function, let colony population and 
population limit be 100 and farmers initial productivity be 3 units of food per 
farmer. Current model would require 34 farmers.

In proposed model first group of farmers would be producing 3 units (1 + 2), 
second 2 units (1 + 2/2), third 1.5 (1 + 2/4), forth 1.25 units and so on. That 
specially treated one unit production is there to prevent starvation. This 
model would require about 60 farmers on colony from example. That is quite 
steep but with some balancing, it won't be so crippling and yet production 
penalty will matter. 

Proposition for following:

UI for easier navigation through colonies like buttons for jumping to next or 
previous colony.

In star system view selected planet (planet shown in planet view tab) should be 
highlighted.

Technology cost is calculated with one level lower then it should be. If player 
can research level _k_, cost for _k - 1_ is shown.

Proposition for following:

Refactor code to MVC design pattern where the game is model and GUI is view.

Proposition for following:

When ships are close enough (at most one slot away) attacker gains accuracy 
bonus from mobility. Idea is to add another benefit to close combat fighters 
and to enable bomb-like weapons that are ineffective at long range but good in 
close range.

Version 0.3 requirement

Current GUI looks ok on 1024x768 and even on same higher resolutions if 
computer user is less then 1m away from screen. Displays larger then default 14 
inch laptop LCDs are usually set to resolution higher then 1024x768 also due 
larger diagonal some users prefer greater distance between display and their 
eyes. In these conditions some parts of current GUI, specifically texts, are 
less visible. Since GUI in this project is based on Windows forms simple 
decrease in resolution (like in fullscreen games) can't be applied. Proposed 
method is to make an option to scale text font sizes (and size of GUI elements).

Completion of fleet view tab.

What steps will reproduce the problem?
1. Colonize planet with high colony maintenance.
2. Wait until ratio of employed and unemployed population drops.

What is the expected output?
Well, anything but negative numbers for industry and development.

What do you see instead?
Industry and development turns negative because more work force is needed for 
the maintenance than it is available.

Version 0.4 requirement

The AI will be divided to multiple levels, each managing certain part of it's 
empire. Lowest level manages colonies, next level manages star systems, next 
galaxy map and the highest manages technologies (and diplomacy and espionage).

Implementation of first two levels (colony and star system) of AI is the goal 
of this task.

Version 0.3 requirement

GUI:
- List of researched technologies.
- List of available ship components.

Logic:
- Multiline descriptions.

Currently there is no way of specifying new line in either technology 
description or ship components.

Proposition for following:

- Rename Prototip namespace to Zvjezdojedac.
- Add classes to corresponding namespaces (GUI to Zvjezdojedac.GUI, etc.)

Sub task for issue #36 (Space combat)

Ship design GUI has to be done anew. "Form" has to be as separate window, not 
as tab within a window as it is now and has to support space combat model 
described in documentation and should have better usability.

Version 0.2 requirement.

Player should be able to see planets only around explored stars. Also player 
should not be able see details on foerign colonies. 

New features:
- Details of planet without colony.
- Star exploration fundaments

Version 0.4 requirement

Move turn processing to non-GUI thread. Add textual progress indicator (what is 
being prcessed, colonies, combats or something else), let's say at top left 
corner of map.

Version 0.4 requirement

GUI for listing and accessing multiple colonies and star systems. Should 
support search filters (own, unclaimed, etc.) and sorting results by various 
attributes (name, max industry, habitability, etc.).

Proposition for following:

During new turn calculation, colonies that have more workers assigned to colony 
development then the colony in question can use, surplus work force should be 
used in other areas (research and system construction). Same for star systems, 
surplus should be assigned to research. That assignment must not "move the 
sliders", in other words it should be temporary, effective only during new turn 
calculation.

GUI for new turn messages needs improvement. Inclusion of completed 
construction messages required.

Proposition for following:

Convert IgraZvj class to singleton.

Proposition for following:

Something along this line: http://xkcd.com/558/

Zvjezdojedac is full of large numbers and displaying them in scientific 
notation can be confusing. Instead, all numbers within given context should be 
displayed with same magnitude prefix. For example:

current format
18.9 M
4.23 G

proposed format
0.018 G
4.23 G

Proposition for following:

Put FormFlote.Dizajner class to separate file.

Proposition for following:

Setting up notifications for construction items. At building queue add options 
for setting notification option for each item. Options could be:

"do not notify"  - do not produce message at new turn report when item is built
"normal" - report only when built
"report progress" - produce message every turn

Version 0.4 requirement

Bottom panel has to be cleared. For start, controles like "technologies" button 
and zoom should be moved to menu at the top. Button "end turn" should be placed 
at lower right corner (yeah, MoO 1&2 style).

Enableing colonization feature required.

Proposition for following:

User should be able to close report window (new turn reports) more easily, such 
as by pressing escape or enter. 

Window should not pop up if there is no messages after applying players message 
type filter.

Message count of each message type. Value can be shown at filter's check box on 
report window.

What steps will reproduce the problem?
1. Put in building queue any repeatable building (colonization or 
industrialization).
2. Press end turn.
3. See new turn report.

What is the expected output? 
No new building messages for buildings that can be built next turn. Only if 
repeatable building has reached capacity limit message should be generated.

What do you see instead?
Reports that repeatable buildings are built, every turn.

Version 0.3 requirement

In previous a versions, the starting population and the planet for the first 
colony were defined in a definition of starting star system. New implementation 
have to separate definition of planets in the starting star system and 
definition of starting colonies. Colonies are settled on best suitable planets 
(ie. with lowest maintenance cost) while colony count and population size are 
selected in same way as map size.

Version 0.3 requirement

If planets natural growth would exceed population limit, surplus population 
should be transported to other colonies within same star system. Amount of 
population than can migrate within system would be defined by population 
capacity of population transport and colony ships in that system. There is also 
idea of buildings such as spaceports that would increase migration limit.

Version 0.4 requirement

Design and implementation of space combat.

When parsing, negative numbers are recognized as variables rather then 
constants.

Problem can be corrected by parsing constants with NumberStyles.Float parameter 
in double.TryParse.

LFROM operator is not limiting value correctly. Limiting is performed when 
interpolation parameter is outside [min, max] while it should be limited when 
outside [0, 1].

Map generator can generate "starlanes" that lead to "no star" type of stars.

Version 0.4 requirement

Managment of star system is going to be implemented. Colonies will no longer 
have 2 building queues (military constraction is about to be removed). Colonies 
will have one slider that determines how much labor is available for research 
and star system projects. 

Version 0.2 requirement.

Adding saving and loading game functionality.

Proposition for following:

New attribute for buildable items, maximum buildable quantity per turn. 

Colonization for example has two quantity constrains, it can't exceed 
population limit and it can't push population growth to more than doubled the 
natural growth. So far, that effect was accomplished with single "max count" 
attribute. Also there was a problem of detecting is building complete or should 
the item stay in building queue.

Proposition for following:

Kind of. To reduce boilerplate code, collections such as List and Dictionary 
should be extended with PendRemove and ApplyPendind methods.

PendRemove - marks object for removal from collection but doesn't remove on 
it's own

ApplyPending - removes from collection all marked objects

Proposition for following:

For easier modding, I propose language with default text values. Ie. if the 
currently selected language doesn't have a requested key in it's string table 
than value from default string table is used. Idea is that a modder don't have 
to make entries for every language, if he or she is not familiar with, but only 
in default.