> > I guess the same also applies for Components and Designs. > > True, but for designs (and to a lesser extent, Components), the issue of who > sets the media, and how.
For components I think it would be mainly defined by server and would probably be a good start. The only possible problem would be when creating a new design also adds a new component (such as when designing torpedoes). > One thing I have been thinking of is just how much information the media > holds. I used an example in the media mapping wiki page of planets, but the > argument applies to ships (ie, designs). The adage "a picture is worth a > thousand words" applies quite aptly. The problem described on the following Wiki page is clearly a server side/ruleset issue. - http://www.thousandparsec.net/wiki/Mapping_objects_to_media I don't think it effects the protocol, as a client will just display the media which the server specifies. I can imagine that some servers may even dynamic generate their media dependent on attributes. > > What do you think is the best way to add this? > > Resources media can be added easily to TP04. Could be added to Designs and > Components, but needs a discussion about who and how to set the media. Okay. Tim Ansell _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
