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-05, 11:18)Philippe Hurbain Wrote: [ -> ]Speaking of canvas... I think it would be a good thing to rename formed cloth from ...c0x to ...-fx ?

Yes, I think so.
I think we need to rename this document. How about:

Official Library Part Guidelines

or

Official Library Policies and Procedures
(2020-06-05, 10:47)Willy Tschager Wrote: [ -> ]There is nothing on patterned parts and the requirment of their plane counterpart in the library.

There is now text to this effect.
(2020-06-05, 19:15)Orion Pobursky Wrote: [ -> ]I think we need to rename this document. How about:

Official Library Part Guidelines

or

Official Library Policies and Procedures

Perhaps something like "Additional Specifications for Official Parts"? As a new user browsing through the documentation, I found it unclear at first that there is a distinction between the LDraw file format itself, and the stricter standards for the parts library. I think those two core functions of LDraw are somewhat conflated and interchangeable in the mind of the casual user.
(2020-06-05, 16:58)Orion Pobursky Wrote: [ -> ]I know we hashed this out already in the closed discussion. I'd like to hear from the larger community

I would agree that shortcuts for stickered bricks are not necessary. They make sense for resale sites like Bricklink, where stickered bricks might exist as physical units in a seller's inventory, but for digital modeling purposes there's no such requirement since stickers can be assembled or disassembled just like any other part.

To me the purpose of shortcuts is so that parts that ship pre-assembled can appear that way in parts lists and set inventories.
(2020-06-05, 19:41)N. W. Perry Wrote: [ -> ]Those two core functions of LDraw are somewhat conflated and interchangeable in the mind of the casual user.

We're not necessarily catering to the "casual user". In fact, the casual user probably never has need to read either document. Or maybe you mean something different and I'm just misunderstanding.
(2020-06-05, 20:47)Orion Pobursky Wrote: [ -> ]We're not necessarily catering to the "casual user". In fact, the casual user probably never has need to read either document. Or maybe you mean something different and I'm just misunderstanding.

The not-already-familiar-with-LDraw-but-looking-to-become-more-so user, perhaps. The person whose interest in LEGO exceeds their familiarity with computers and programming languages, but find the need to move beyond the capabilities of LDD and Studio.
At the very end you should add this:

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

w.
(2020-06-05, 10:47)Willy Tschager Wrote: [ -> ]Nothing on canvas/fabric/cloth - guess it should go into the part numbering and we should address a convention when Canvas or Cloth is used.

What I'm talking about is this:

https://forums.ldraw.org/thread-23171.html

and:

https://forums.ldraw.org/thread-23089.html

I think as for sticker, we should somehow formalize them. We have
  • Sheet Cardboard
  • Sheet Fabric
  • Sheet Plastic
As category but nothing about proper naming and we still have:

https://www.ldraw.org/cgi-bin/ptscan.cgi...escription
https://www.ldraw.org/cgi-bin/ptscan.cgi...escription
https://www.ldraw.org/cgi-bin/ptscan.cgi...escription

all over the library along with:

https://www.ldraw.org/cgi-bin/ptscan.cgi...escription

w.
(2020-06-04, 15:25)Orion Pobursky Wrote: [ -> ]Stugs have been moved to the Part Number spec. I moved the LDConfig paragraph under the Colour Restictions heading.

Id like more comment. Particularly I'd like comments on the general rules for shortcuts.

For the sake of completeness, could you add to the STUD numbering the need for the "fast-draw" and the "MLCAD Fallback" Stud? i.e. the reduce resolution for p/8 and the "stu8xx"?

I could not find this in the doc.
Pages: 1 2 3 4 5 6 7