I am pleased to announce that the LDraw Parts Tracker has been updated to render its images using LDView, instead of ldglite.

Thanks to Travis Cobbs for building a version of LDView on the server and to Don Heyse for all his previous support for ldglite.

Chris

Yes - let's collect requirements here. Then I can build a web interface as part of the Parts Tracker. It should be linked to the Parts Tracker to facilitate automatic removal when an unofficial version gets submitted. There is Parts Tracker functionality that can be re-purposed for this.

Questions:
- Should each user have a limit on how many parts than can have on their "I request this" list?
- Should each user have a limited number of "I support this votes"?
- Should there be a hierarchy of votes (Urgent/Important/Useful/Nice to have)

LDraw Parts Request System Requirements:
- page listing requested parts (sortable by part number, description, vote tally), linking to
- page for each requested part, containing
- link to part image (peeron/Bricklink/personal URL)
- username of requestor
- usernames of supporters
- username of volunteer author
- comments/activity log (like on the Parts Tracker)
- links for "I support this", "I am authoring this", "Comment"

- page listing (for current user) of requested and supported parts

- admin functionality to edit/rename/delete entries

Chris

Here's the latest version. Discuss!!
--

The Offical Model Repository Specification
Version: 0.5 (will turn 1.0.0 upon ratification by the LSC)
Author: Orion Pobursky

Purpose:
--------
The Official Model Repository (OMR) is a database of file in the LDraw File Format describing models that are released as sets by LEGO®.

For consistency between models and ease of indexing by software, a standard for the file headers, names, and hierarchy in the OMR is needed. This document will outline the extra requirements (in addition to those set forth in the current LDraw File Format specification) for a model to be included in the OMR

Base Requirements:
------------------
All files in the model will conform to the current LDraw File Format

Base File Naming:
-----------------
Each model in the OMR will consist of several files that are packaged together into a single MPD file. For sets that include instructions for multiple models, each model will have its own MPD file. Each MPD for the set will be named in the following manner:

<Set Number> - <Set Name> - <Sub Model Name>

Where:
<Set Number>: the number assigned on the container of the set
<Set Name>: The name of the set printed on the container in Australian English
<Sub Model Name>: This is Optional in most cases. This is required for alternate models that are detailed in instructions (e.g. the Creator theme). In this case the naming is left to the discretion of the author but should be descriptive of the model contained in the MPD.

For playsets or other sets where there are multiple models that are part of an integral whole, all of the submodels will be contained in one MPD.

Example:
The creator set 4896 - Roaring Roadsters has 3 models in the instructions:
Set 4896 - Roaring Roadsters - Roadster.mpd
Set 4896 - Roaring Roadsters - Dragster.mpd
etc...

MPD File Structure:
-------------------
The MPD will conform to the MPD File Specification.

Each filename will have the structure:
<Set Number> - <Optional Qualifier> - <Individual filename>
Where:
<Set Number> is the the number printed on the model's container
<Optional Qualifier> is a suqential number, starting with 1, added if there are more than one sets that could be assigned <Set Number>.
<Individual filename> is up to the discretion of the author with the following guidance:
- A logical naming scheme is highly desired.
- Individual models in the set (e.g. a vehicle or minifig) shall have their own separate file inside the MPD.
- Minifig file name should have the name of the character, if known

The unofficial parts are allowed to be used. The filename of the unofficial part is subject to the naming rules above (e.g. 33056.dat would be renamed to <MPD Filename> - 33956.dat). It is highly encouraged that any parts created for use in a OMR file be submitted to the LDraw.org Parts Tracker.

If a part is unavailable either officially or on the LDraw.org Parts Tracker, a suitable substitution may be made. If the unavailable part is a patterned part with an unpatterned version available use the unpatterned version. A comment should be inserted stating that a substitution has been made or, if no substitution is available/suitable, that a piece has been omitted. Reference the step and page number of the instructions if possible.

Example:
0 // The next piece should have the Star Wars Hatch pattern per step X on page Y
or
0 // Bionicle piece X should go here per step Y on page Z

File Headers:
-------------
Each individual model file in the MPD must have a standard header format.

Standard Header:
0 FILE <MPD Filename> - <Filename>.ldr
0 <MPD Filename> - <File Description>
0 Name: <MPD Filename> - <Filename>.ldr
0 Author: <Author Name>
0 !LDRAW_ORG Model -OR- 0 !LDRAW_ORG Unofficial_Model
0 !LICENSE Redistributable under CCAL version 2.0 : see CAreadme.txt

0 !THEME Theme name
0 !KEYWORDS words, more words,…,
0 !KEYWORDS words in second row, …, final words

0 !HISTORY YYYY-MM-DD [<Author Name>] Free text description of change. This can wrap to a
0 !HISTORY YYYY-MM-DD [<Author Name>e] second row with the same date if necessary. However authors should lean toward writing longer
0 !HISTORY YYYY-MM-DD [<Author Name>e] single !HISTORY lines(and not feel constrained to the historic 80-character limit on line length)

Where:
<MPD Filename>: The name of the containing MPD
<Filename>: The name of the file
<Author Name>: The name of the author. Real full names (first and last) are required by the LDraw.org Contributer's Agreement
Optional commands are !THEME, !KEYWORDS, and !HISTORY

Example:
To Be Inserted Later

META commands:
--------------
All META commands are allowed in the model file but not specifically required except as specified for the header. If included, any META commands used should enable any instructions generated to be as close to the official instructions as possible.

I was trying to build this:
http://peeron.com/inv/sets/6336-1?showpic=10452

but, I found out that there was no
http://www.peeron.com/inv/parts/3068bpx113
in LDraw parts library.

As I checked, there are only 2 LEGO models, where this part is used and in 2 accessories pack, so it's very rare.

Anyway, does anyone in any chance have that part?

It's a simple part, just a tile with radar scope on it, I thought I could make it myself, but I don't understand, how to use those weird LEGO CAD programs. They are just like made for program developers themselves. But I would appreciate if anybody could give a tutorial, that is not only for LEGO CAD program developers.

The text I entered below doesn't contain any semicolons, but Phorum adds one:

Cross-post from the announcements for discussion and replies:

Quote:Following the establishment of the LDraw Contributor Agreement in 2004 many authors have helped to re-develop the LDraw Parts that we did not have agreement to redistribute. Of the 90 original "Non-CA" files only 24 now remain and all except three have been re-developed, and are sitting in the Parts Tracker awaiting review.

I would like to get these into the next Parts Update to remove the need for this complication in the LDraw library. To help prioritize their review I have added a "Review Summary" page to the LDraw Parts Tracker. This includes the re-worked files and any dependents. It would be good if reviewers could take a look at this and prioritize their activities on these files.

In addition volunteers to re-develop the three remaining parts, would be most welcome.
http://www.ldraw.org/cgi-bin/ptdetail.cg...s/2873.dat
http://www.ldraw.org/cgi-bin/ptdetail.cg...039p33.dat
http://www.ldraw.org/cgi-bin/ptdetail.cg...26bps8.dat

Thanks in anticipation, Chris

(LDraw Parts Library Admin)

I found this article. There described way how to convert some parts. For automatic separation this long string to groups of 9 numbers you can use text editor with function of RegEx (I used EmEditor because I had problems with them in Notepad++)
In your program you have to find

I uploaded an upgrade to Phorum 5.3.17. Let me know if there are any issues related or if it fixes any of the bugs we've noted.

Following the establishment of the LDraw Contributor Agreement in 2004 many authors have helped to re-develop the LDraw Parts that we did not have agreement to redistribute. Of the 90 original "Non-CA" files only 24 now remain and all except three have been re-developed, and are sitting in the Parts Tracker awaiting review.

I would like to get these into the next Parts Update to remove the need for this complication in the LDraw library. To help prioritize their review I have added a "Review Summary" page to the LDraw Parts Tracker. This includes the re-worked files and any dependents. It would be good if reviewers could take a look at this and prioritize their activities on these files.

In addition volunteers to re-develop the three remaining parts, would be most welcome.
http://www.ldraw.org/cgi-bin/ptdetail.cg...s/2873.dat
http://www.ldraw.org/cgi-bin/ptdetail.cg...039p33.dat
http://www.ldraw.org/cgi-bin/ptdetail.cg...26bps8.dat

Thanks in anticipation, Chris

Hi,

I'd like to put down a list of the known bugs in the current 3.3 version. Feel free to add:

• If I go to MLCad setting, tab Rendering and choose "Background color" in that color dialog I can not browse through the colors - http://news.lugnet.com/cad/mlcad/?n=2305
  
  
• In some cases I cannot manipulate the rotation matrix because the angle value in the vector field (which I never saw much use of anyhow) is something like -9.223372 * 10^n and MLCad does not understand it. So whenever I try to open up the rotation matrix field I get a dialog saying that the angle should be between -180 and 180 and the field remains disabled. What's worse, the same is for the vector fields and thus I cannot reset the angle! All I can do is reset the matrix manually in LDDP. *Highly* annoying - http://news.lugnet.com/cad/mlcad/?n=2307
  
  
• There is a bug in the generated partslist when using a new color. For example when I use a part with color 81 Metalic_Green it reports as Chrome_Black. See: http://www.binarybricks.nl/test/colorerror.gif Can this be resolved with a change in ldconfig or is a real bug in MLCad 3.30? - http://news.lugnet.com/cad/mlcad/?n=2343
  
  
• File > Scan parts generates a Parts.lst file that breaks long filenames:
  75174p01c01.daAnimal Dragon Oriental w. Chr.Gold Head and Tr.Red Wings (Comp.)
  
  
• Copying a color to the colorbar the statusbar will always show the default color name from 1 - 16.