Subject:
|
Re: LDraw File Format Spec 1.0 DRAFT - Call for Public Comments
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Tue, 21 Aug 2007 22:28:21 GMT
|
Viewed:
|
3136 times
|
| |
|
|
In lugnet.cad, William Howard wrote:
> Like all previous LSCs, the 2006/7 LSC was charged with ratifying the LDraw File
> Format 1.0 specification.
>
> After much work checking, and ratifying as necessary, all linked specs and
> language extensions, and many months of dicussions about the actual spec, the
> LSC would now like to invite public comment on the final draft spec.
>
> William Howard
> On behalf of the 2006/7 LSC
I'm new to this community, and am just learning 3D graphics, but I will comment
on this as someone who will eventually use this file format to read in and
render these parts in 3D.
1. Character encoding - for a file spec, not specifying this seems potentially
problematic. Every text file has a character encoding, whether or not it's been
explicitly stated. If you save a text file and haven't taken any special steps
to specify it, it will most likely use whatever your "default" encoding is for
the computer you are using.
And if you open a text file and don't specify the encoding, your default
encoding will be used. This can cause problems when say someone in Greece saves
a part file and sends it to someone in the US.
Since all the parts files in the official LDRAW repository are already saved in
a specific character encoding, why not specify what that is in the spec?
2. Filenames - why just "discourage" use of white space in file names? Why not
prohibit it?
3. Comment lines - if the "//" is the preferred usage, why not just get rid of
the other usage? It won't break anything, if both forms are acceptable now. (And
if they're not both acceptable now, then there are programs already broken.)
Tightening up the spec makes it simpler, which is always a good thing.
4. Meta commands - I'm curious, what backwards-compatibility issues are there
with having some files NOT use the "!" for meta-commands? Since you control the
spec and the parts files, can't you update whatever few official commands that
do not start with a "!" to include it?
5. Line Types - in the summary at the top of page 3 you call Type 1 the
"Sub-file reference" , but at the bottom of page 3 you state "Line type 1 is a
file reference." Is there a reason these two descriptions are different?
6. Colour is spelled wrong. (Ok, this one is a joke)
7. Why doesn't the main spec mandate consistent vertex windings? Either CC or
CCW, but at least make them all the same. Or at least the same withing a given
file. If it's a problem with inconsistent windings in the current parts files,
can't they be updated via a batch script to use consistent windings?
8. The write, print, clear, pause, and save commands don't seem to really belong
in a file that describes geometry. I understand they were used in the early
LDraw days, but today, are any modern applications using these commands during
the rendering process? If not, why not remove them?
That's my input ;)
And thanks for all your work to create such a useful standard!
Rob
|
|
Message is in Reply To:
 | | LDraw File Format Spec 1.0 DRAFT - Call for Public Comments
|
| Like all previous LSCs, the 2006/7 LSC was charged with ratifying the LDraw File Format 1.0 specification. After much work checking, and ratifying as necessary, all linked specs and language extensions, and many months of dicussions about the actual (...) (17 years ago, 20-Aug-07, to lugnet.cad) !
|
55 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
