|
From: Vlad J. <vj...@au...> - 2004-01-25 03:52:31
|
Hi Cpt. and all. =20 I started to write the answer with critics, but it did not look good. So = I added this line here :-) Critics are below. Overall, I think that layout looks really well. However, I did not like = the <content> and <transfer> sections. I think they should be combined. The = item in content must have more information about it status, where content is = one of them. Let=92s say you have a gun in stores. So, the status of it is =91stored=92 or something. Then you transfer it to another base, the = item changes the base it belongs to and its status is =91transferred=92. We = might even have the number of hours till arrival. Then for some specific content entries, for example scientists, we would definitely want more information. But those are details which could be flushed out later.=20 More major issue is that whether contained items must be described = within container or base itself. For example, crafts. There is a section in the <base> which lists crafts, but then there is a reference to them from <hangar>. From programming point of view it is just difference in one = method of Base class: either retrieve list of crafts within Base object itself = or create a list of crafts from the crafts from all hangars. I would prefer that crafts would be listed inside the hangars =96 the XML would be = clearer. But that is different for stores or living quarters: it is not important what store the pistol is in or what barrack John Doe is in =96 we are = not going to display them differently or provide that kind of info for = players.=20 =20 Regards mamutas --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.560 / Virus Database: 352 - Release Date: 1/8/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.560 / Virus Database: 352 - Release Date: 1/8/2004 =20 |