 | | 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 (...) (17 years ago, 27-Mar-08, to lugnet.cad.dev, FTX)
| | | | | Re: LPub 4 Status
|
| (...) I believe a MAC version mklist utility used to generate the PARTS.LST file comes bundled with the OS-X version of ldglite. Source code is available, so anyone can build it on whatever platform they like. There may be better ways to build the (...) (17 years ago, 27-Mar-08, to lugnet.cad.dev, FTX)
| | | | | Re: LPub 4 Status
|
| (...) Perfect - many thx! Don't think there is any need for "development" but "<LDRAWDIR>LSynth" wouldn't hurt. You could then store all constraints and synthesis parts in that folder without the need to mix them with the official parts or rebuild (...) (17 years ago, 27-Mar-08, to lugnet.cad.dev)
| | | | | Re: LPub 4 Status
|
| (...) I figured that Development would be use by parts authors. I was offering it as an alternative to D:work_in_progress. LSynth it is. Kev (17 years ago, 28-Mar-08, to lugnet.cad.dev)
| |
