I'm not particularly keen on there being implicit meaning in the sequence of metadata lines in the config file.
Would something like this work? Two positional parameters to describe the level of detail and the folder name, then free text to the end of the line for the description(which can include spaces)
The polygon edge count would be used to sequence the entries and would describe how circular elements are coded, but wouldn't prevent other primitives existing in the same folder.
The description would be used by tools as a standard way of presenting the detail levels in selection lists.
How should 16 be defined as the default within the metadata? Or will applications need to assume that - it is the only folder that is guaranteed to include a version of each primitive?
This is the right time to incorporate support for the logoed stud, but I'm not sure how it would fit into this schema.
Would something like this work? Two positional parameters to describe the level of detail and the folder name, then free text to the end of the line for the description(which can include spaces)
Code:
0 // !PRIMITIVE-DETAIL <Polygon edge count> <folder name> <description>
0 !PRIMITIVE-DETAIL 0 p/0 Ultra-low resolution
0 !PRIMITIVE-DETAIL 8 p/8 Low resolution
0 !PRIMITIVE-DETAIL 16 p Standard
0 !PRIMITIVE-DETAIL 48 p/48 High resolutionThe polygon edge count would be used to sequence the entries and would describe how circular elements are coded, but wouldn't prevent other primitives existing in the same folder.
The description would be used by tools as a standard way of presenting the detail levels in selection lists.
How should 16 be defined as the default within the metadata? Or will applications need to assume that - it is the only folder that is guaranteed to include a version of each primitive?
This is the right time to incorporate support for the logoed stud, but I'm not sure how it would fit into this schema.
Chris (LDraw Parts Library Admin)