Subject:
|
Re: LPub 4 Status
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Mon, 24 Mar 2008 17:08:09 GMT
|
Viewed:
|
10514 times
|
| |
|
|
In lugnet.cad.dev, Kevin L. Clague wrote:
| |
In PLI’s, LPub displays the parts color name (from LDConfig), the part number
(yes, even on the Mac version Allan!), and the part title. Currently I get
these titles from PARTS.LST, but that is not sufficient, and it is a short
sighted implementation.
|
Is PARTS.LST the file that gets generated by some DOS utility in the original
LDraw distribution? You can’t rely on that being present. Not being able to rely
on a DOS utility, Bricksmith reads the part library and generates its own XML
parts list; I assume other programs do something similar.
| |
I got a Mac mini yesterday, so I’m at the bottom of the learning curve on
getting LPub going there. I know it is unix (which I know very well), but I
did not find make or the gcc tools (which I also know very well) using find.
I’m antsy to get going there. Any ideas on where to get started?
|
Congratulations! This is wonderful news for Mac LDraw users. I have fielded
numerous requests asking for an instruction-generation tool in Bricksmith, and
I’ve always been ashamed to respond that there isn’t one, never will be, and the
process of doing it manually is probably too hard for them to figure out. I
eagerly anticipate being able to direct people to a real solution. Thanks for
making the capital investment to support us!
As others have noted, in order to get the developer tools on your Mac, you need
to install the Xcode Tools package. It is found somewhere on your Mac OS
installer DVD. That installs the gcc toolchain, Apple’s graphical IDE, and lots
of other stuff.
Allen
|
|
Message has 2 Replies:
 | | Re: LPub 4 Status
|
| (...) As will LPub before it is made available to the public. Thus the comment about short sighted. Now that I have an example on what to do, I'll implement that instead. There is one class that will have to be changed, and no one else needs to know (...) (16 years ago, 25-Mar-08, to lugnet.cad.dev, FTX)
| | | Re: LPub 4 Status
|
| (...) <snip> LPub does not need a total list of parts, so it doesn't have to scan all the paths. It does need the titles of parts that are used however. Since parts.lst is a precomupted list of some of them, LPub reads it and puts the contents in an (...) (16 years ago, 27-Mar-08, to lugnet.cad.dev, FTX)
|
Message is in Reply To:
| | Re: LPub 4 Status
|
| (...) You are more knowledgable on this topic than I am. As far as the assembly images go, at least for now I'm at the mercy of LDGlite. I've made good use of the superb document and specifications on LDraw.org. I want to thank all involved in (...) (16 years ago, 23-Mar-08, to lugnet.cad.dev)
|
81 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
|
|
|
|
