 | | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I agree, and prefer <> around all tags. (...) Ah, but what about leading blanks. ;^) Nevermind, I don't think you can create an absolute path that starts with leading blanks. (...) But wait. The reason given for looking in LDRAWDIR is for a (...) (21 years ago, 3-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 (...) (21 years ago, 3-Mar-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
Where to store the preferences? While I've been aware of this thread, I haven't actually been following it, so correct me if I've got the wrong end of the stick. (...) MacOS 9 and earlier is a single user environment and it was easy to place (and (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev, lugnet.cad.dev.mac)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Sorry to immediately respond to my own respond to my own reply, but I forgot one minor detail. The corallary to this bit is that to be safe, Windows programs should treat both / and \ as path separators any time they parse paths, and work (...) (21 years ago, 2-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 (...) (21 years ago, 2-Mar-04, to lugnet.cad.dev)
|
| |
| | 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 (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Oh. I didn't know it was as easy as: ~/MacOSX/environment.plist I guess that is one route. In Cocoa, which is what Andrew and I are both developing in now, it is really easy to grab prefs that have a unique name for the application. It isn't (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
"Don Heyse" <dheyse@hotmail.spam....away.com> schrieb im Newsbeitrag news:HtwMAE.3BM@lugnet.com... (...) Done, sorry about that - but it was a hard day at work :-( (...) As mentioned earlier in this thread ... we should go with: 1) Users Home (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev, lugnet.cad.dev.mac)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
Ok I hop on again ... "Lars C. Hassing" <sp.lars@am.hassings.dk> schrieb im Newsbeitrag news:Htnz7B.G2z@lugnet.com... (...) located (...) directories, (...) (URL) However, I suggest section name [LDrawSearch] which is more in line with [LDraw]. I (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Actually Environment variables work pretty well on OS X because they've set up a standard place to put them, and it's one of those plist files. See here for details. (URL) would be nice though to have a standard fallback location for the (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
One other thing. Environment variables work too, but only serious Unixy Mac OS X people actually modify them--that is, some developers, but no one else. Normal users would even know what they are. Heck, even I don't modify mine. For my l3p and (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) /etc would work, except it would require admin permission to install, which is something the Mac OS X community doesn't like for an installer/app that isn't a system modifying type of installer/app. Saving stuff in /etc/ will also not survive (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Oops, I forgot to add this. These sort of restrictions mean a user may be forced to put extra search directories in their home directory. Rather than recognize $HOME or %USERPROFILE% in an absolute path, it might be nice to add a <HOME> (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev, lugnet.cad.dev.mac)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I'm only willing to abandon environment variables if you're willing to go the distance and really try to work out a standard that we all can use. I, like Lars, was quite disappointed when you got impatient and cut short the previous discussion (...) (21 years ago, 1-Mar-04, to lugnet.cad.dev, lugnet.cad.dev.mac)
|
| |
| | Parts Tracker outages in preparation for release of 2004-01
|
|
Please expect some availability outages on the Parts Tracker today (and maybe for the next few days), as I work on the next parts update. If all goes well the 2004-01 update will be ready in the next few days. Chris Dee (LDraw Parts Admin) (21 years ago, 29-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I agree (although I did point something out in a response to Orion's response). Unix (and Unix-like) environments do often use the environment to control things, but they also use dot files. And while it wouldn't make sense to have an (...) (21 years ago, 28-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) Well, the ldraw directory itself can be specified in ldraw.ini. And while I agree that filling up the Windows directory is generally a bad thing, you can't have the file be in the LDraw directory if it is the file that specifies where to find (...) (21 years ago, 28-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I agree. I like the ini file solution over the environmet varible (...) I agree that putting the ldraw.ini the LDRAW dir would make much more sense (why it wasn't in the first place is puzzling) but the problem is that the programs the use it (...) (21 years ago, 28-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
I just start a new sub-thread to discuss two very important points where I thought over two nights now: The location of the ini file and environment variables! I would not recommend to go with both solutions, because its source for possible errors (...) (21 years ago, 28-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
|
(...) I think you are being a bit unreasonable. The discussion is about a fundamental functionality of LDraw, which has impact on all programs. Agreement is important to ease the life of the end user: *one* place for setup. We try to accomodate (...) (21 years ago, 27-Feb-04, to lugnet.cad.dev)
|
