Subject:
|
Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Mon, 1 Mar 2004 18:25:38 GMT
|
Viewed:
|
5597 times
|
| |
|
|
Ok I hop on again ...
"Lars C. Hassing" <sp.lars@am.hassings.dk> schrieb im Newsbeitrag
news:Htnz7B.G2z@lugnet.com...
> In lugnet.cad.dev, Don Heyse wrote:
> > In lugnet.cad.dev, Travis Cobbs wrote:
> > > In lugnet.cad.dev, Michael Lachmann wrote:
> > > > Good idea, so how about
> > > >
> > > > [LDRAW_SEARCH]
> > > > 1=SHOW <MODELDIR>
> > > > 2=HIDE <LDRAWDIR>P
> > > > 3=SHOW <LDRAWDIR>Parts
> > > > 4=SHOW <LDRAWDIR>Models
> > > > .
> > > > .
> > > > .
> > > > 20=SHOW "C:\A special path with blanks"
> > > >
> > > > Keywords <MODELDIR> ... actual directory where the project/file is • located
> > > > <LDRAWDIR> ... what it tells us
> > > > and finaly paths starting with anything different from "<" as beeing
> > > > absolute paths as beeing designed for the operating system
> > > >
> > > > I think two keywords for predefined paths should be enough.
> > >
> > > It looks good to me.
>
> Me too. I think it is a good idea with a separate section for the search • directories,
> it allows shorter keys than suggested in • http://news.lugnet.com/cad/dev/?n=9510
> However, I suggest section name [LDrawSearch] which is more in line with
[LDraw].
I can agree nothing would speak against that.
<SNIP> Section of environments <SNIP>
I'm happy with any solution here, but I will not read it - so I don't want
to hinder anything beeing
agreed here.
> > However, I'm undecided whether to require
> > a HIDE or SHOW tag, or use only <HIDE> and make SHOW the default. Will
> > anyone else be using the environment variable, and if so do you have
> > a preference?
>
> I suggest <HIDE> and <SHOW> as prefixes, <SHOW> as default if none • specified.
> Using < > may become useful later for other flags.
> If your program doesn't understand the tag <xxx> then it can simply ignore • it.
> Flags as <PARTS> and <PRIMITIVES> could be used for classifying any file • in a given
> directory not having an "official" file type header.
> (classifying is important, at least to L3P, for determining e.g. when to
use seams)
I'm talking on file level now, I still would prefer the syntax like style of
HIDE and SHOW but we can also see it as an
option in which case I would take them into brackets.
So if it is easier or better when using in environment variables go for it -
but we should get them equally processed in variables and files.
>
> Quotation marks should not be necessay if we use the < >.
You are right but I still would allow them for the rare case of blanks at
the end of a directory name.
>
> Also I suggest a \ after <LDRAWDIR>: "2=<HIDE><LDRAWDIR>\P"
> Unix platform should of course convert to /.
I cannot see any reason for this but we could eliminate it later on
anyway. - at least Windows doesn't care about single or double backslashes.
>
> In the week end I plan to write a small library (in C) for reading the env • vars and LDraw.ini's
> to set up the directories. I'll also write an LDrawSetup application with • a GUI for editing LDraw.ini.
> All open source, if you want to save the effort yourself.
> /Lars
>
>
I will have to write it myself - MLCad is not open source!
Michael
|
|
Message has 3 Replies:
 | | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
| (...) That's not exactly true. I'm sure you can work out an arrangement with Lars. After all, L3P is not entirely open source, and the benefit of all the LDRAW tools using an identical parts search strategy is probably more useful than having you (...) (20 years ago, 1-Mar-04, to lugnet.cad.dev)
| | | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
| (...) I believe that this isn't entirely true. We had a problem at work where a program didn't work right in Windows 9x (I think it was 98, but I'm not entirely sure), but worked fine in Windows NT and Windows 2000. After some careful debugging, I (...) (20 years ago, 2-Mar-04, to lugnet.cad.dev)
| | | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
| (...) The data contained in either environment variables or ini files should have exactly the same format. (...) Trailing blanks are preserved in both env var and ini files. So I still don't think quotation marks are necessary... (...) I didn't mean (...) (20 years ago, 3-Mar-04, to lugnet.cad.dev)
|
Message is in Reply To:
132 Messages in This Thread:
(Inline display suppressed due to large size. Click Dots below to view.)
- 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
|
|
|
|
