I was adding to protocol.xml when I noticed some mistakes. On Mon, 05 May 2008, Tim Ansell wrote: > On Sat, 2008-05-03 at 02:11 +1200, Lee Begg wrote: > > On Fri, 18 Jan 2008, Tim Ansell wrote: > > > I think this suggestion (which is basically a reordered version of > > > nash's) is a good idea, > > > > > > * A List of, (these define the maximums) > > > * UInt32, read only, Limit for this 'resource' > > > * a GRS list, read only, thing this resource refers to
This list above is duplicated in the list below. Limit == maximum. > > > * A list of, (these are the possible selections) > > > * a UInt32, read only, id of what can be selected > > > * a String, read only, name of what can be selected > > > * a SInt32, read only, maximum that can be selected (-1 == no > > > limit) * a GRS list, read only, thing this item selection refers too * > > > A List of, > > > * UInt32, read only, Weight for this resource There is nothing to test the weights against. > > > * A list of, (these are the selections) > > > * a UInt32, read write, id of the selection > > > * a UInt32, read write, number of the selection > > > > > > Tim 'Mithro' Ansell > > > > Is this what you want? I will add is shortly, if you want. I think it's > > unwieldy. > > I think it works pretty well. It will support a wide variety of > different order types and give the client UI a lot of information on > how to display them. > > Tim 'Mithro' Ansell 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
