 | | Re: L3P Warnings
|
|
(...) I'm guilty of that blank-space-deletion in my own parts, I confess. I do most of my authoring in Excel, and sometimes it becomes helpful to sort by linetype. This has the effect of stripping out the blank lines or at least moving them around (...) (14 years ago, 7-Jul-10, to lugnet.cad.ray)
|
| |
| | Re: L3P Warnings
|
|
(...) I agree to some extent. But now it's there, like it or not. I have very little (if any?) use of it and yes it annoys me a little. The deleting of extra blank lines (used to group lines some way related to eachother) that makes the dat code a (...) (14 years ago, 7-Jul-10, to lugnet.cad.ray)
|
| |
| | Re: LDraw.org 2010-02 Parts Update Now Available
|
|
(...) HUGE thanks, guys!! i've been using ldraw since the beginning and it's always a little exciting to see what new parts are coming out. i've been wrestling with the lego digital designer software (not as an alternative to ldraw but because i (...) (14 years ago, 7-Jul-10, to lugnet.cad)
|
| |
| | Re: L3P Warnings
|
|
(...) For me, the argument comes back to process vs. product, as was discussed in the previous thread. Additionally, it raises the question of whether LDraw is a tool for the end-users or a tool for the reviewers. The extended period of discussion (...) (14 years ago, 7-Jul-10, to lugnet.cad.ray)
|
| |
| | Re: L3P Warnings
|
|
(...) I'm intrigued - the only point in that last sentence that differentiates the "indecipherable gobbledygook" from the inline POV is that the latter "yields a greatly superior output image". It's certainly no less invisible to the end-user, nor (...) (14 years ago, 7-Jul-10, to lugnet.cad.ray)
|
