On Wed, 21 Nov 2007, Brett Nash wrote: > <Lists> > > > To make a list which can only have one item selected, a "total maximum" > > argument will be added (got no idea why we left that off the first > > time). > > Silly question... is it worth adding a 'weight' field and changing the > total maximum to be a total weighted maximum? > > So that sum of each items #selected * weight < total weighted maximum.
Note that weight is integer, so some fun math might be necessary to adjust the
total weighted max.
> I'm just thinking this takes the normal case for building stuff really
> nicely... So building ships and stuff can be done automatically in the
> client in an easy way?
So, yes the refsys "type" field is necessary...
> Also trading games with different cargo units can work with the list
> easily too.
How well will total weighted max work with both resource "size" and "mass"?
Could there be a problem there? IE, hitting the max size OR the max mass?
> Obviously doesn't solve all cases, but it works instantly with RFTS and
> trading games.
>
> Otherwise... all good.
>
> > This means that the list order parameter structure will look like,
>
> Updated version by nash:
> > List - A list in which one or more items can be selected
> > The possible selections,
>
> * A list of:
> * a UInt32, read only, id of what can be selected
> * a String, read only, String Name of can be
> selected
> * a SInt32, read only, maximum number of can to be
> selected, -1 means no limit
> * an UInt32, read only, weighting.
> 0 means doesn't count to limit
> * a GRS list, read only, What this item refers too
Why a list?
> * a SInt32, read only, the total weighted maximum number of
> things which can be selected, -1 means no limit.
>
> The selection, A list of:
> * a UInt32, read write, id of the selection
> * a UInt32, read write, number of the selection
It does appear that the List Order parameter doesn't have enough information
currently. I don't see the need for a list of GRS refs. So why not use this:
List Order Parameter:
* int32 GRS reftype (ie, object, design, etc) (read only)
* list of (all read only):
* uint32 id (forming a full reference with the reftype)
* string name (not necessary maybe?)
* item limit
* weight
* uint32 weight total max (read only)
* selection list:
* uint32 id
* uint32 quantity
Can you think of any use that would require the name field, multiple ref
types, or multiple refs per item?
> Regards,
> nash
Later
Lee
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
