To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 2190
2189  |  2191
Subject: 
Re: LDAO Suggestion Mark 2
Newsgroups: 
lugnet.cad.dev
Date: 
Thu, 1 Jul 1999 18:47:17 GMT
Viewed: 
828 times
  
In lugnet.cad.dev, Jeremy H. Sproat writes:
Steve Bliss wrote:
On Thu, 1 Jul 1999 06:31:21 GMT, Paul Gyugyi <paul@gyugyi.com> wrote:
Should we add a search path in the ldraw.ini file?
A definable search path would be good.  Some ideas:
1. An ini-file setting.

Definitely.

3. An environment variable.  This would be L3P-friendly.
4. A command-line option.  Not necessarily a good idea (how many people
launch LDLite from the command line?  I'd guess very few), but LDAO could
pass stuff this way.

Both IMHO are necessary.

One problem I have with the command-line option is that the command line is
already long enough.  But that doesn't mean that having the option is bad.

I do all my non-LDAO (which is quite a bit)
LDraw/LDLite stuff from the command-line.  VC++ doesn't make it *that* hard
to implement exotic command-line parameters, especially if one uses
getopt().

I was worried about the user more than the developer.

I don't know how VB handles it, though...

In VB, there's a function (or is it a pre-defined variable?) called COMMAND$.
It contains everything on the command line, except the program name.  You have
to write code to parse everything out, but you can define any parameter format
you like.

6. A meta-command, in the main model file.

I have another idea.

Good idea!

So what should the precedence be for each of these settings? Assuming they are
ever implemented, of course.  I'd suggest the following, going from high to
low:

1. Interactive selections (from Options menu)
2. Command-line options
3. 0 CMDLINE meta-statement
4. Ini-file setting
5. Environment variable

Steve



Message has 1 Reply:
  Re: LDAO Suggestion Mark 2
 
(...) Something to consider here is future expansion into a UNIX-ish (or Java, or Perl/TK, etc.) version of LDraw. The availability of setting startup parameters on the command-line in these cases is essential. (...) Oh. :-, I wonder if I'm a (...) (25 years ago, 1-Jul-99, to lugnet.cad.dev)

Message is in Reply To:
  Re: LDAO Suggestion Mark 2
 
(...) Definitely. (...) Both IMHO are necessary. I do all my non-LDAO (which is quite a bit) LDraw/LDLite stuff from the command-line. VC++ doesn't make it *that* hard to implement exotic command-line parameters, especially if one uses getopt(). I (...) (25 years ago, 1-Jul-99, to lugnet.cad.dev)

23 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
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR