Tore Eriksson Wrote:
-------------------------------------------------------
> I really want to keep my library
> of boxed DATs as small as possible, but this makes
> it so interesting that I might let it explode in
> size (and thus, the POV output files generated by
> L3P...) by adding those so far not needed extra
> lines.
I've got it working now without the need for header information, but it's still guessing and so it can guess wrong, like for example the town0-1.ldr has this line:
1 7 540 0 -800 0 0 0.50 0 0.50 0 -0.50 0 0 baihous1.ldr
The whole house is scaled down (to datsville scale I guess?). This will cause my 'improved' guessing code to handle the whole town0-1.ldr as a single part. But it can be corrected by fixing the header of town0-1.ldr only instead of all the boxed parts.
>
> Besides the file size factor, I've been hesitating
> to use the Name !LDRAW_ORG in vain for my own
> private, unofiffcial files. My understanding of "0
> !LDRAW_ORG Unofficial_Part" is:
> * Property of LDraw.org. You may use it under this
> and that Licence Agreement if you agree with this
> and that.
> * This file meets header standards and all other
> silly specs the LSC have come up with. At least it
> did when released.
> * This part is in the Parts Tracker, waiting to be
> part of the Official LDraw Parts Library.
> * In other words: Don't use this line at home! It
> is reserved for a few chosen Admins trusted with
> it.
> No, that's not really my understanding of it.
> But it's sure what it's signaling.
>
You right about the !LDRAW_ORG it implies it's part of the library official or not. But as far I can find there is no other way of marking the nature of a ldraw file. I think I'm going to bring this up in the LSC.
> And, like I said, if the main file resides
> somewhere in LDraw\Parts, that information itself
> should be sufficient(?) to determine that you're
> dealing with a part.
>
You are right but there are exceptions for example shortcuts threading them as parts will double used resources for the referenced 'real' part, and don't get me started about the fixed color parts, they would plunder VGA resources like locus.
> /Tore
-------------------------------------------------------
> I really want to keep my library
> of boxed DATs as small as possible, but this makes
> it so interesting that I might let it explode in
> size (and thus, the POV output files generated by
> L3P...) by adding those so far not needed extra
> lines.
I've got it working now without the need for header information, but it's still guessing and so it can guess wrong, like for example the town0-1.ldr has this line:
1 7 540 0 -800 0 0 0.50 0 0.50 0 -0.50 0 0 baihous1.ldr
The whole house is scaled down (to datsville scale I guess?). This will cause my 'improved' guessing code to handle the whole town0-1.ldr as a single part. But it can be corrected by fixing the header of town0-1.ldr only instead of all the boxed parts.
>
> Besides the file size factor, I've been hesitating
> to use the Name !LDRAW_ORG in vain for my own
> private, unofiffcial files. My understanding of "0
> !LDRAW_ORG Unofficial_Part" is:
> * Property of LDraw.org. You may use it under this
> and that Licence Agreement if you agree with this
> and that.
> * This file meets header standards and all other
> silly specs the LSC have come up with. At least it
> did when released.
> * This part is in the Parts Tracker, waiting to be
> part of the Official LDraw Parts Library.
> * In other words: Don't use this line at home! It
> is reserved for a few chosen Admins trusted with
> it.
> No, that's not really my understanding of it.
> But it's sure what it's signaling.
>
You right about the !LDRAW_ORG it implies it's part of the library official or not. But as far I can find there is no other way of marking the nature of a ldraw file. I think I'm going to bring this up in the LSC.
> And, like I said, if the main file resides
> somewhere in LDraw\Parts, that information itself
> should be sufficient(?) to determine that you're
> dealing with a part.
>
You are right but there are exceptions for example shortcuts threading them as parts will double used resources for the referenced 'real' part, and don't get me started about the fixed color parts, they would plunder VGA resources like locus.
> /Tore