<snip>
> > So resources are already there as things used in the performing of this
> > order.
>
> But there is no way of knowing in the client how much the order/object
> WILL cost until it's sent?
No there is no way, which I agree with nash is a bad thing.
<snip>
But all this is off the point.
Lee was suggesting the following structure for "resource list" order
parameter.
Resource list:
* List of selectable:
* id, resource id
* max quantity
* max mass
* max volume
* List of selected:
* id, resource id
* quantity
Which makes sense as we already know the mass and volume of each unit of
resource. It is also extensible if we add more information to the
resource description.
I still think the other generic order list is needed, but this is much
cleaner for the resources special case.
Tim 'Mithro' Ansell
_______________________________________________
tp-devel mailing list
[email protected]
http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
