| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 2,472
» Latest member: farikadol
» Forum threads: 3,154
» Forum posts: 26,914
Full Statistics
|
| Latest Threads |
Lego Overwatch
Forum: Off-Topic
Last Post: Reuben Pearse
Yesterday, 21:21
» Replies: 0
» Views: 83
|
Technic 2014
Forum: Official Models
Last Post: Shih-I Yang
Yesterday, 17:17
» Replies: 8
» Views: 4,292
|
Technic Series
Forum: Official Models
Last Post: Shih-I Yang
Yesterday, 9:51
» Replies: 33
» Views: 17,882
|
cannot access private mes...
Forum: General LDraw.org Discussion
Last Post: Orion Pobursky
Yesterday, 0:05
» Replies: 1
» Views: 237
|
LDraw All-In-One-Installe...
Forum: LDraw.org Announcements
Last Post: Willy Tschager
2018-10-19, 20:37
» Replies: 2
» Views: 2,734
|
Technic 2018
Forum: Official Models
Last Post: Philippe Hurbain
2018-10-19, 14:41
» Replies: 42
» Views: 33,871
|
Ldcad - "buffer exchange"...
Forum: LDraw Editors and Viewers
Last Post: Johann Eisner
2018-10-19, 13:26
» Replies: 3
» Views: 494
|
Call for LDCad 1.6 bug re...
Forum: LDraw Editors and Viewers
Last Post: Philippe Hurbain
2018-10-19, 8:38
» Replies: 17
» Views: 6,044
|
Creator
Forum: Official Models
Last Post: Lasse Deleuran
2018-10-16, 18:19
» Replies: 16
» Views: 9,810
|
Lego models with fusion 3...
Forum: General LDraw.org Discussion
Last Post: stephane ramauge
2018-10-13, 16:36
» Replies: 0
» Views: 527
|
|
|
| UTF8 encoding bug in part u588p02c03.dat? |
|
Posted by: Roland Melkert - 2011-12-01, 23:15 - Forum: Parts Authoring
- Replies (7)
|
 |
During fixing of utf8 handling in LDCad I stumbled on this part: "u588p02c03.dat".
One of the keyword lines seems mangled. Even in utf8 editors (it comes out partly Korean or something).
This can't be right?
The line above it (with elephant etc) does contains valid utf8 coding though.
|
|
|
| [Sticky] Parts for urgent review |
|
Posted by: Tim Gould - 2011-12-01, 22:50 - Forum: Parts Authoring
- Replies (39)
|
 |
I've made this a sticky thread. Please add parts whose absence makes a major gap in the library. Try to stick to older parts (more than 1 year on the PT) but if a new part is important and appears to be overlooked (eg. new basics like tiles, plates and bricks) add it too.
And for those who wish to help review but don't know how, try this tutorial.
For example:
The 4.5V and 12V have been on the PT for a long time.
|
|
|
|
| Thanks for this forum! |
|
Posted by: Philippe Hurbain - 2011-12-01, 15:35 - Forum: General LDraw.org Discussion
- Replies (11)
|
 |
I must admit that I was skeptical to move discussions from Lugnet/cad to here, but seeing the huge activity here now, and all the new guys appearing, it was a wise move! So many thanks to all involved in the creation of this new LDraw home!!!
|
|
|
|
| forum notification e-mail |
|
Posted by: Steffen - 2011-12-01, 14:44 - Forum: Website Suggestions/Requests/Discussion
- Replies (4)
|
 |
Currently, the forum notifications via e-mail have "webmaster@ldraw.org" as sender.
I'd like to ask if this could be changed to something more specific/simpler, like e.g.
ldraw.org Forums Notification
or
LDraw.org Forums
or
LDraw.org Forum Notificator Script
or
LDraw.org Forum Notificator
That would allow me to better sort my e-mails.
The general sender webmaster@ldraw.org should IMHO not be used for this specific task.
(Of course, the "From" text setting can be configured independently from its associated mail address,
so of course the mail address behind the From: text can stay as it is now.
I just want the displayed text in the notification mails changed to something more specific.)
|
|
|
|
| Applescript droplet to generate png previews using LDView |
|
Posted by: Ramón Figueroa-Centeno - 2011-12-01, 10:01 - Forum: LDraw Editors and Viewers
- No Replies
|
|
Aloha,
The following saved as an application from the AppleScript Editor generates png previews:
Code: property ldview : "/Applications/LDView/LDView.app/Contents/MacOS/LDView"
on run
set root to choose folder with prompt "Please select folder."
generatepreview(root)
end run
on open root
if folder of (info for root without size) is true then
generatepreview(root)
end if
end open
on generatepreview(root)
set suffix to "\\( -iname \"*.ldr\" -o -iname \"*.mpd\" -o -iname \"*.dat\" \\)"
set root to (POSIX path of root) as string
set root to quoted form of ((characters 1 through -2 of root) as string)
set ldrs to do shell script "find " & root & " -type f " & suffix
repeat with ldr in paragraphs of ldrs
try
set dirname to do shell script "dirname " & quoted form of ldr
set png to ((characters 1 through -5 of ldr) as string) & ".png"
do shell script "cd " & dirname & "; " & ldview & " " & quoted form of ldr & " -SaveSnapshot " & quoted form of png
end try
end repeat
end generatepreview
It assumes that LDview is in the application folder. Modify the "ldview" property otherwise.
Ramón
|
|
|
|
| Streamlining the exchange of models that use unofficial parts |
|
Posted by: Jim DeVona - 2011-12-01, 2:41 - Forum: LDraw File Processing and Conversion
- Replies (14)
|
|
A common issue with sharing LDraw models seems to be unofficial parts usage. To recap the problem, since unofficial parts are subject to changes in origin, orientation, filename, etc., models built with unofficial parts may appear incorrectly or incomplete to users with different (or no) versions of that part. The recommended solution (see recent examples) is to include needed unofficial parts as MPD submodels, so the version used will always be available to others viewing the file. This is a good solution, but I don't think it is an obvious solution to the larger community of casual users. Plus, if you use certain unofficial parts frequently (or have downloaded all of them), I find it easy to forget that they are even unofficial - and there may be prerequisite unofficial subparts or primitives needed as well.
So:
- Are there any editors or utilities that currently support saving models with unofficial parts (and dependencies) included as sub models? For example, a save dialog option or insert menu command to "Include unofficial parts as sub models", or a single-purpose utility to do the same for existing files. I suppose unofficial parts would be identified by looking for "Unofficial_" in the !LDRAW_ORG header line (or any non-compliance with the official library header specs, for that matter), or also, obviously, if they are housed in the "Unofficial/" subdirectory of the LDraw library.
- Imagine if the Part Tracker kept a version history of the actual part files (like source code version control), not just an event log. (Does it?) Conceivably, this could then be used to retrieve the unofficial parts used to create models found in the wild - perhaps even programmatically, based on file creation date. I can imagine a number of cases where this strategy might break down, but maintaining a full version history seems like it might be useful anyway. (Moving forward, it could probably even be implemented as a third party mirror that monitors the main part tracker's activity log and commits copies of each new change...)
Thoughts and comments?
|
|
|
|
|
