Some folks have brought up a request to possibly augment the PXML specification slightly. A little too much drama but hey, its the Internet :)
In discussion is .. preview pics and the concept of 'primary preview pic'; ie: If an applicatio nis to show only a single primary pic out of a number oif supplied ones, how does it know which one to present?
Traditionally (by which I mean minimenu and maybe a few other apps) the first preview pic has been shown. The 'repo' shows them all (in reverse order, perhaps until recently?).
XML data is I think assumed to be unordered (while HTML and SGML are ordered), as technically there shoudl be an ordering attribute.
Some options that fall out..
i) Add a note to the PXML spec to hard define that order is important, in that 'first preview pic mentioned' is 'preferred pic, if you only want one'; that lacks ordering after first, but at least defines first, and requires minimal changes to existing code.
ii) Add some ordering attributes to the elements; be it just 'primary' flag, or perhaps 'order=1' 'order=2' etc, some way to identify sequence. Or evej somethign goofy like "type='titlescreen' order='1'" .. but that seems extreme to me, when many don't care at all. Donmt' need to overdo it..
iii) Do nothing; leave it as a 'soup' of images, and no defined ordering.
Examples in other 'app store' type environments.. I don't recall offhand. I'm at work and sleepy right now :)
Implications: Changes may require code changes in libpjnd, minimenu, repo, milky, pndstore, pnd updatey thign from the compo, etc. So minimal or no changes are best, perhaps..
I'm okay with doing nothing, or the order of implying ordering by order in PXML seems goofy yet reasonable; we could also add a 1/2/3/4/54 type ordering number, but that implies code changes. I'm not really interested in going further than 1/2/3/4 type simple numbering.
Does anyone have an opinion here?
jeff
-- If everyone would put barbecue sauce on their food, there would be no war.