| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 5,423
» Latest member: Andrei
» Forum threads: 6,246
» Forum posts: 52,227
Full Statistics
|
| Online Users |
There are currently 280 online users.
» 3 Member(s) | 272 Guest(s)
Applebot, Baidu, Bing, Google, Yandex, Rene Rechthaler
|
|
|
| Scott Wardlaw appointed as LDraw Colormaster |
|
Posted by: Willy Tschager - 2011-08-18, 14:36 - Forum: LDraw.org Announcements
- No Replies
|
 |
Hi folks,
in sync with "Section 6.08: Appointed Key Positions" of the LDraw Bylaws the LDraw Steering Committee has appointed Scott Wardlaw as LDraw Colormaster.
Scott has maintained the LDraw color file LDConfig.ldr since 2009 and will be from now on officially responsible for corrections and additions.
Congratulations!
Willy Tschager
On behalf of the LDraw SteerCo
|
|
|
| Datsville |
|
Posted by: Roland Melkert - 2011-08-14, 19:52 - Forum: MOCs (My Own Creations)
- Replies (87)
|
 |
Hi all, I've been playing around with datsville.
But somehow I thought it was bigger, I'm using the version from datsville.googlecode.com.
Anyone has a newer / bigger version?
Also why is everything stuffed in a gigantic MPD (33000 lines!) Not very efficient for use in svn.
|
|
|
|
| OMR Spec - Updated 8/14 |
|
Posted by: Orion Pobursky - 2011-08-14, 7:17 - Forum: Parts Authoring
- Replies (12)
|
 |
Here's the latest draft. Discuss!! (Note: there is a quote bug that's removing the text between <>. Be aware of that and restore the text if needed)
--
The Offical Model Repository Specification
Version: 0.2 (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>( <Optional Specifier> )-[main or alt<Number>]
Where:
<Set Number>: the number assigned on the container of the set
<Optional Specifier>: Sometimes different sets with the same number are released, the specifier will be a single digit number, in parentheses, that is different between different sets, to distinguish these sets from one another.
[main or alt<Number>]: The main model of the instructions (i.e. the model featured on the cover of the container) will have the word "main". For sets that feature more than one model on the front of the container (e.g. the Creator line), the largest or most prominent model is the main model. For alternate models that are detailed in instructions, the word "alt" and a single digit number starting at 1 will be used. 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 the main model MPD.
Example:
Set 4896 - Roaring Roadsters. This creator set has 3 models in the instructions. The roadster is featured prominently on the box. 4896 is the only set with that number. Therefore:
Roadster MPD: 4896-main.mpd
Dragster MPD: 4896-alt1.mpd
etc...
MPD File Structure:
-------------------
The MPD will conform to the MPD File Specification.
The naming of the individual files in the MPD 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 <MPD Filename> is required to be prepended to the file name of each individual file in the MPD
The only unofficial parts allowed to be referenced in the model files are those currently residing on the LDraw.org Parts Tracker. No part files shall be contained in the MPD.
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 Desciption>
0 Name: <MPD Filename> - <Filename>.ldr
0 Author: <Author Name>
0 !LDRAW_ORG Official Model Repository
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 name are highly desired but not required. If the full name is not provided, a first or last name, with or with out initials, is requested.
Optional commands are !THEME, !KEYWORDS, and !HISTORY
META commands:
--------------
The only META commands allowed in the model file are those associated with the header, 0 FILE (for MPD support) and 0 STEP. STEP commands not specifically required but they are highly desired. If included, the step commands should follow the instructions as closely as possible.
|
|
|
|
| "Go To New Post" vs. threading |
|
Posted by: Travis Cobbs - 2011-08-10, 2:33 - Forum: Website Suggestions/Requests/Discussion
- Replies (1)
|
 |
When you click on the red flag next to a topic, the forum takes you to the first new post in the topic since the last time you read that topic. Unfortunately, this doesn't work very well in the threaded view, since the definition of "first new post" is the first one chronologically, instead of the top new post visually. So you end up having to scroll through the whole threaded discussion looking for new posts no matter what you do.
Is there any possibility that "first new post" could be redefined to mean the top new one visually? The two are often the same, and doing it this way would make that link useful. (Note: I had this happen to me a few days ago, and stopped clicking the flag link. It's possible you already fixed this, but I'm assuming not.)
|
|
|
|
|
![[Image: 5484667276_61862c9e06_o.png]](http://farm6.static.flickr.com/5300/5484667276_61862c9e06_o.png)
