|
|
| (3 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| '''Please add your suggestions for the LDraw wiki below.'''
| | {{TalkRedirect}} |
| | |
| And please remember to sign them using four tildes (<nowiki>~~~~</nowiki>) to give a date as well. This way we can keep track of things more easily. If you respond to a suggestion remember to indent your response using one or more colons (:) at the start of each paragraph.
| |
| | |
| There is also an [[LDraw.org:discussion]] page.
| |
| | |
| | |
| ==Suggestions==
| |
| [example] I would like to see more suggestions on this page. [[User:Timgould|Timgould]] 07:56, 25 May 2007 (EDT)
| |
| :[example response] So would I [[User:Timgould|Timgould]] 07:57, 25 May 2007 (EDT)
| |
| | |
| == Spammers ==
| |
| Spammers have found this place, I think... I've blanked two pages so far, see recent changes. Probably need to block the affected ID and keep a closer watch, whoever the admins are. ++[[User:Lar|Lar]]: [[User_talk:Lar|t]]/[[Special:Contributions/Lar|c]] 06:57, 24 August 2007 (EDT)
| |
| :Another one. That page probably needs deleting. ++[[User:Lar|Lar]]: [[User_talk:Lar|t]]/[[Special:Contributions/Lar|c]] 11:02, 9 July 2008 (EDT)
| |
| | |
| ==Use of leading space for numbers==
| |
| The reason for using leading space in front of numbers lower than ten (10) is the sort order in listings.<br />
| |
| '''Example: (wrong order)'''<br />
| |
| <font face=courier>
| |
| Brick 10 x 10<br />
| |
| Brick 2 x 2<br />
| |
| </font>
| |
| These two description would be in a list just the wrong way because the seventh character (as it is the first different) will decide about the sort order.<br />
| |
| So if we add a whitespace in front of the 2 we have "whitespace" and "1" at the seventh character. Because the "whitespace" has a lower internal value as the "1" the correct sorting order will be visible.<br />
| |
| To show it visually here I had to substitude the whitespace by underscore.<br />
| |
| '''Example: (correct order)'''<br />
| |
| <font face=courier>
| |
| Brick__2_x__2<br />
| |
| Brick_10_x_10<br />
| |
| </font>
| |
| | |
| As this has not been considered from the beginning of the library there are little inconsistances in the library.<br />
| |
| I like to mention here what I had discovered so far that does not follow the simple rule - "''If number is used and number is lower than 10 use a second whitespace in front of that number''":<br />
| |
| '''at parts and subparts'''<br />
| |
| * if the word 'type' is the last word before that number (Baseplate 32 x 32 Road 9-Stud Landing Pad Type 1 (Orange) - [http://www.ldraw.org/library/official/parts/6099p04.dat])
| |
| * if the word 'Road' is the last word before that number and the letters '-Studs' are direct attached to the number (Baseplate 32 x 32 Road 9-Stud Landing Pad Type 1 (Orange) - [http://www.ldraw.org/library/official/parts/6099p04.dat])
| |
| | |
| My earlier resumee at this place has been wrong. The real old part with L, V, H and / direct after the number do have a leading whitespace. And that makes sense to me because of the sort order.(2011-06-25)<br />
| |
| | |
| '''at primitives'''<br />
| |
| * if word 'Torus' is in the description only the first of the numbers needs a leading whitespace
| |
| * if word 'Circle' is in the description none of the numbers needs a leading whitespace
| |
| * if word 'Cylinder' is in the description none of the numbers needs a leading whitespace
| |
| * if word 'Cone' is in the description only the first of the numbers needs a leading whitespace
| |
| * if word 'Ring' is in the description only the first of the numbers needs a leading whitespace
| |
| * if word 'Disc' is in the description none of the numbers needs a leading whitespace
| |
| * if word 'Chord' is in the description none of the numbers needs a leading whitespace
| |
| | |
| If you have an original part that does not fit into this scheme please inform us. Please do not use the parts on the PT as reference because there are parts that follow not these rules maybe because of the usage of DATHeader. <br />
| |
| To bring DATHeader in a good condition I like to have this cleared if possible.<br />
| |
| '''The soon coming version 3.0.8.0 of DATHeader will act as described here but without a correct check on the primitives.'''
| |
| | |
| --[[User:Mikeheide|Mikeheide]] 16:32, 24 June 2011 (EDT)
| |