From: Stefan F. <ste...@we...> - 2012-09-02 14:03:39
|
Erik: the underlying TreeSet allows to optionally specify a Comparator which deviates from the natural ordering. Thus it is easy to add a different ordering to the IPO portfolio. But thanks for reminding me of that, do you know other cases where the ordering of a "portfolio" in Rails 1.x is important for game mechanics? Stefan On 09/02/2012 12:41 PM, Erik Vos wrote: > Stefan, > >> * PublicCertificates are sorted by >> i) President or not >> ii) CertificateType (and those are sorted by number of shares inside) >> iii) CertificateId >> >> This keeps the PresidentShare at position zero of each portfolio without >> requiring any code to keep it there. And it keeps the multi-shares at the > top >> of a list of certificates. > > How will you then handle the 1835 double shares that must appear at the > *bottom* of the IPO stack (BA, WT and HE)? > Currently, specification order determines IPO order. > > Erik. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |