Subject:
|
Re: Ldlite for OpenGL and Linux (and uppercase filenames)
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Wed, 19 Jan 2000 16:08:46 GMT
|
Viewed:
|
1002 times
|
| |
|
|
Don Heyse:
> In lugnet.cad.dev, Fredrik Glöckner writes:
> > Rui Martins <Rui.Martins@link.pt> writes:
> >
> > > Are you sure that was the problem, because Ledit runs on DOS, which
> > > doesn't care on filename case, it's case-insensitive, so it should always
> > > work in DOS.
> >
> > This is a special LEdit feature, not related to DOS at all. If the
> > STUD.DAT filename is uppercase, it is always displayed like a full
> > stud in LEdit, even if the user chooses to have "line for stud" to
> > save rendering time.
> >
> > Fredrik
> Let me restate MY preference (and since I'm a newcomer here, feel free to
> stomp all over me :^)
My preference is all lower-case (mostly from an aesthetic
point of view), which generally is more readable than upper-case.
> 1. DAT files in the P and PARTS directories should be stored in uppercase
> since they come out of the archives that way.
>
> 2. The P, PARTS, MODELS, BITMAPS, VEC directories should be uppercase since
> they seem to come out of the archives that way as well.
I don't think it would be difficult to switch this to
lower-case (if I can convince you guys to agree with me on
the benefits of lower-case).
> 3. Other DAT files can be stored in whatever case you
> like. For example: MyModel.dat, MYMODEL.DAT,
> mymodel.dat. Just don't put it in the P or PARTS
> directories in anything but UPPERCASE. And don't
> expect to see it if you include it in MyScene.dat with
> different capitalization.
Bad idea.
People working on case-insensitive file systems will happen
to write the file name with one capitalisation, and store it
on the file system with another one. It will work for them,
but it will not work for people working on case-sensitive
file systems.
People working on case-sensitive file systems will happen to
make two files with the same name, except for the
capitalisation. It will work fine for them, but when the
model is copied to a case-insensitive file system one of the
two files will disappear.
Both of these two problems can be avoided by sticking to
either upper or lower case.
> 4. You can include bricks and primitives from the P and PARTS directories
> in whatever case you like and they will be UPPERCASED by the programs
> before opening the files. Any special behavior determined by the case
> can be done before the filename is UPPERCASED. I'm not quite sure if
> we have some more stringent standards for what goes on inside the bricks
> and primitives files in the PARTS and P directories. It sounds like we
> do based on the special LEDIT behavior mentioned above.
Not exactly a bad idea. Here is my reformulation:
No matter how file and directory names are written in
LDraw files, they shall be converted to lower-case
in comunication with the operating system and other
programs.
> 5. Automatic UPPERCASING inside the program will ONLY happen for DAT files
> in the P and PARTS directories and their subdirectories.
Disagree.
> 6. I'm still not thrilled with this because it makes the DAT file caching
> scheme in Ldlite trickier, but I can't think of a better solution...
If all files are stored with lower-case names, the caching
in LDLite doesn't have to be (much more) complicated.
Play well,
Jacob
------------------------------------------------------------
-- E-mail: sparre@cats.nbi.dk --
-- Web...: <URL: http://hugin.ldraw.org/LEGO/Tog/ > --
------------------------------------------------------------
|
|
Message has 2 Replies:
 | | Re: Ldlite for OpenGL and Linux (and uppercase filenames)
|
| (...) If you go way back to the beginning of this thread you'll see that my PERSONAL preference is also lower case, because it's easier to type, easier to read, etc. But I seem to recall a debate a while ago about the rights to distribute modified (...) (25 years ago, 19-Jan-00, to lugnet.cad.dev)
|
Message is in Reply To:
40 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
