To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.dev.macOpen lugnet.cad.dev.mac in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / Macintosh / 775
774  |  776
Subject: 
Re: LDView 3.1 on Mac OS X!
Newsgroups: 
lugnet.cad.dev.mac
Date: 
Thu, 1 Mar 2007 21:32:05 GMT
Viewed: 
5512 times
  
In lugnet.cad.dev.mac, Allen Smith wrote:
   I’m delighted to see another developer supporting the Macintosh.

  
  
   I’m glad that Bricksmith can make use of them. Does it have a UI to add new directories to the part search path?

Nope, so I had feared it might not be able to access them. However, I’ve checked and Unofficial is hard-coded as the unofficial parts directory name (in Source/Other/MacLDraw.h, for those following along at home). You can set the LDraw directory, of course, so it will just look for an “Unofficial” directory within that.

Interesting. I wonder if it was just a coincidence that we both chose the same hard-coded directory for Unofficial parts, or if Bricksmith’s author saw that I had used it. I suspect the former, since LDView didn’t work on the Mac.


Yeah, LDraw/Unofficial just seemed like the logical choice. That was feature that went nowhere, though. I never even documented it, because I didn’t think anyone else supported it. (L3P?) I really wish LDraw would define a standard Unofficial parts folder. Right now I just set the Finder’s label color to red for any unofficial parts and then blithely dump them in my LDraw folder.

Well the other thing to consider is that with the adoption of the standard header on DAT files, there really is no *need* to store unofficial files in a different sub-directory, because programs will be able to tell which files are unofficial from the header. (In fact it’s already possible, as this has been an “unofficial standard” for quite some time.)

Having said that, I can see the argument that it’s nice from a programming standpoint to keep them separate. However, I’m not sure that’s a strong enough argument (for me) to make it an official LDraw standard. For users, it makes little difference - if they are downloading unofficial files, they probably know what they’re doing anyway, and would possibly find it beneficial to have all DAT files together, so that programs that don’t support all standards (ie: directory search) can still access them easily.

And programs need to check the header anyway, because it’s easy for unofficial files to end up in the the standard parts directory, and vice versa. Programs can’t assume that all files in the standard parts directory are official, and all in the unofficial directory are unofficial.

So my current thinking is it should be an option that can be selected (in each program) by the user. And I think the default for programs that download them automatically should be to put them in the standard LDraw parts directory. And as such it shouldn’t be a standard enforced by the LDraw org.

ROSCO



Message has 1 Reply:
  Re: LDView 3.1 on Mac OS X!
 
It's me the user that wants to know which unofficial parts I've downloaded and am using, and thus which may require updating, deleting, or something. For me it is purely a user-management issue. My program doesn't really care if a part is Official (...) (18 years ago, 2-Mar-07, to lugnet.cad.dev.mac, FTX)

Message is in Reply To:
  Re: LDView 3.1 on Mac OS X!
 
I'm delighted to see another developer supporting the Macintosh. (...) Yeah, LDraw/Unofficial just seemed like the logical choice. That was feature that went nowhere, though. I never even documented it, because I didn't think anyone else supported (...) (18 years ago, 27-Feb-07, to lugnet.cad.dev.mac, FTX)

39 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