LDraw.org Discussion Forums

Full Version: Official Library File Format Restictions
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7
(2020-06-19, 14:49)Orion Pobursky Wrote: [ -> ]I also changed the extension portion and added a section about texture files.

I just noticed while cleaning up the code that the TEXMAP spec requires PNG. I've changed the texture text to reflect this.
(2020-06-19, 16:40)Orion Pobursky Wrote: [ -> ]I just noticed while cleaning up the code that the TEXMAP spec requires PNG. I've changed the texture text to reflect this.

Did you miss my other objections/corrections?
(2020-06-19, 20:46)Magnus Forsberg Wrote: [ -> ]Did you miss my other objections/corrections?

I forgot, sorry. They have been made.
when programming a ldraw loader and adding bevel edges automatically, I noticed that several parts don't follow those rules (T-junctions existed, overlapping surfaces etc.). Meaning the rules are not followed and I implemented some mesh operations to fix them on the fly. 

Looking at the rules, statements like "must be avoided, but still legal", don't help imo.

Is the plan to robustly identify them, do people go through them manually one by one to have them rebuilt etc.?
Are there tools that do this. Could the tools fix the parts directly? Like one sentence there can have a lot of consequences for the existing content, is that accounted for?
(2020-06-25, 13:53)Christoph Kubisch Wrote: [ -> ]when programming a ldraw loader and adding bevel edges automatically, I noticed that several parts don't follow those rules (T-junctions existed, overlapping surfaces etc.). Meaning the rules are not followed and I implemented some mesh operations to fix them on the fly. 

Looking at the rules, statements like "must be avoided, but still legal", don't help imo.

Is the plan to robustly identify them, do people go through them manually one by one to have them rebuilt etc.?
Are there tools that do this. Could the tools fix the parts directly? Like one sentence there can have a lot of consequences for the existing content, is that accounted for?

This is addressed in the intro. These rules have evolved over time. There will be some parts in the Official Library that don't conform. This document applies to all parts awaiting approval and any future official parts that are resubmitted to be fixed.
(2020-05-30, 7:24)Willy Tschager Wrote: [ -> ]Blanks in description
One thing that is a constant issue for newbies at the PT is the blank in the front of numbers in the description and I couldn't find the specs for it. (This would obviously go into header).


Thanks for adding this. However what IMHO is still missing in the example at https://www.ldraw.org/article/398.html:


***********************************************


General

This the descriptive name of the part. If the description contains dimensions, a leading space should be added to single digit numbers to aid in sorting.
Examples:
0 Brick  2 x  4
0 Brick  1 x 10
 (Note the lack of a leading space on the 2 digit number)

***********************************************

is how to deal with blanks in combinations with decimals as in sticker dimensions.

Sticker 3.1 x 3.1 Round

Furthermore this information should be mirrored to https://www.ldraw.org/article/339.html

***********************************************

The description of the part should begin with 'Sticker ...' followed by the dimensions ...

[color=rgba(0, 0, 0, 0.87)][size=small][font=Tahoma, Verdana, Arial, sans-serif]***********************************************[/font][/size][/color]

[color=rgba(0, 0, 0, 0.87)][size=small][font=Tahoma, Verdana, Arial, sans-serif]w.[/font][/size][/color]
(2020-06-19, 14:49)Orion Pobursky Wrote: [ -> ]I made the change to required all lower case. This involve removing the option for A-Z from the allowed characters and changing the note at the end of the paragraph. 

I also changed the extension portion and added a section about texture files.

https://www.ldraw.org/article/512.html

Code:
Extension

All files in the LDraw Parts Library are required to carry the .DAT extension.


.DAT has to be substituted by .dat. Otherwise the whole discussion will start over again at the next revision.

w.
https://www.ldraw.org/article/512.html#colours

Code:
where a line is being used for fine detail within a pattern and that pattern is re-used within many parts (and hence sub-parted) in different colours (for example, sub-part s/973p11a.dat)

We do no longer use emphasis lines. Should be deleted.

w.
A constant hassle for newbies is the usage of Metallic vs. Chrome in patterns. May be https://www.ldraw.org/article/512.html#ldconfig is the right place to address that in patterns only Metallic is used to represent shiny colors.

w.
(2020-06-06, 13:45)Willy Tschager Wrote: [ -> ]At the very end you should add this:

https://forums.ldraw.org/thread-22605-po...l#pid32133

w.

I still believe that the list what triggers a HOLD should be added and this:

https://www.ldraw.org/library/tracker/ref/l3pmsg/

should be deleted or updated.

w.
Pages: 1 2 3 4 5 6 7