Xml And Game Transactions

[bpuk]

OK, time to look at the schema for buying/selling

 

At the moment we have price/upkeep defined invididually in combatants.xml, crafts.xml and facilities.xml

 

no prices defined for items.

 

Should all the prices and upkeeps go in a transactions.xml file, or should I add (optional)price to the schema for items?

 

Also - which file should I be putting costs for scientists/engineers in?

 

Ta

Ben

[bpuk]

OK - I'm going with a transactions.xml - at least for items and personell, crafts/facilities may be added later (if needed)

<transactions>
   <action name="ActionName" keys="Ctrl-T"/>
   <transaction name="PERSONELL_ENGINEER" category="PERSONELL">
       <price purchase="75000" sell="0"/>
       <upkeep cost="2000"/>
   </transaction>
   <transaction name="PERSONELL_SCIENTIST" category="PERSONELL">
       <price purchase="75000" sell="0"/>
       <upkeep cost="2000"/>
   </transaction>    
   <transaction name="ITEM_PISTOL" category="SMALLARMS">
       <price purchase="5000" sell="2000"/>
       <upkeep cost="0"/>
   </transaction>    
     .... etc.
</transactions>

 

Figures, per usual, off the top of my head.

 

Comments?

 

Ta

Ben

Edited August 17, 2005 by bpuk

[UnFleshed One]

 

What's that?

 

BTW, I think upkeep cost can be included into price

<price purchase="75000" sell="0" upkeep="2000"/>

Unless there is a reason for separating.

[bpuk]

<action name="ActionName" keys="Ctrl-T"/>

 

What's that?

 

BTW, I think upkeep cost can be included into price

<price purchase="75000" sell="0" upkeep="2000"/>

Unless there is a reason for separating.

<{POST_SNAPBACK}>

 

*cough* copy-paste error...

 

OK, integrated into schema - upkeep optional. Slight changes (on further consideration)

 

<transactionTable>
<transaction name="PERSONELL_ENGINEER" purchasable="yes" buildable="no">
 <price purchase="75000" sell="0" upkeep="2000"/>
</transaction>
<transaction name="PERSONELL_SCIENTIST" purchasable="yes" buildable="no">
 <price purchase="75000" sell="0" upkeep="2000"/>
</transaction>    
<transaction name="ITEM_PISTOL" purchasable="yes" buildable="no">
 <price purchase="5000" sell="2000"/>
</transaction>  
</transactionTable>
<transactionCategories>
<category name="SMALLARMS">
 <item name="ITEM_PISTOL"/>
</category>
<category name="PERSONELL">
 <item name="PERSONELL_SCIENTIST"/>
 <item name="PERSONELL_ENGINEER"/>
</category>
</transactionCategories>

 

Splitting the categories is much easier to parse when it comes to building the buy/sell lists

 

Ta

Ben

[bpuk]

Sorry for (repeated) double post...

I've stripped the categories out of the [temp] schema for the moment, need to think on the best way of handling them. Possibly in a second file

 

Added transactions.{xml,xsd}

 

added core/transactions/transactions.{cpp,h} (Yes, I do have a reason for putting it here. There'll probably be another class pair, and possibly a third. Could be wrong though - if so, feel free to move it to staticdata and tell me off )

 

class Transaction is the xenocide interface to the transaction.xml file

 

Basic testing done only, some old (commented) code still in there - will be modified and corrected in next patch.

 

Patch attached

 

Ta

Ben

 

EDIT 1: Found (stupid) mistake in attachment - removed

EDIT 2: Corrected stupid mistake - attached

transactions_xml_corrected.zip

Edited August 17, 2005 by bpuk

[red knight]

Has this patch been integrated already?

 

Greetings

Red Knight

[bpuk]

Has this patch been integrated already?

 

Greetings

Red Knight

<{POST_SNAPBACK}>

 

Doesn't look like it has.

 

Ta

Ben

 

P.S. This should be the last 'core' patch before getting visible changes in buy/sell

Edited August 20, 2005 by bpuk

[red knight]

Could not merge, missing line. Can you update and repost?

 

Greetings

Red Knight