The divide between market and goods

[Itangalo]

Which methods should belong to the Market class, and which to the Goods class?

[Itangalo]

Markets currently have the following relevant methods:

• restock (all or selected resource)
• setPrice (of a selected resource)
• setQuantity (of a selected resource)
• getQuantity (of a selected resource)
• getBuyableItems
• getBalance (when potentially buying a selected resource)
• buy (a selected resource)
• resolve (a selected resource)

Not yet implemented:

• sell (a given amount of a selected resource)
• buyMultiple (of the same resource)
• something to handle auctions
• something to handle flexible costs

One possible line between Market and Goods is that anything dealing with a single goods type belongs to the Goods class, the rest to the Market. Another is that anything that makes sense to come with the ownership of a goods belongs to the Goods class – making it easy to call from wherever the goods is transfered. I lean towards the latter – you go to the market to buy something, not to the goods. You ask the market how much sheep there is.

If so, all the current methods should be left on the Market, and only sell and resolve should be added to the resource. Let's try that.

[Itangalo]

Done.