 | | | | | | |
| |
|
In lugnet.cad.dev, Kevin L. Clague wrote:
> In lugnet.cad.dev, Willy Tschager wrote:
> > In lugnet.cad.dev, Kevin L. Clague wrote:
> >
> > Hi Kevin,
> >
> > > When you say unofficials and custom folders, what are you thinking? Since it
> > > uses ldglite, there are some rederer features I do not have control over.
> >
> > I was refering to the use of unofficial and custom parts and the possibilities
> > to include them into BI without the need to store them in the <LDRAWDIR>Parts
> > folder or include them in Parts.lst.
> >
> > w.
>
> 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 updating the specifications and website.
>
> I did not find any "official" specification for alternate pathing of parts. I'm
> very interested in implementing the standard, or the defacto standard, if I knew
> where to find an explanation.
>
> 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.
>
> I also get part length from the titles, so supporting unofficials is important.
>
> 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?
>
> Kevin
LDView and MLCad shows a way for solving this issue.
In the MLCad.ini you can define alternate search path for parts, so you do not
have to mix official and unofficial parts.
Also LDView has the possibility to search in different directories.
cu
mikeheide
| | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad.dev, Michael Heidemann wrote:
> LDView and MLCad shows a way for solving this issue.
> In the MLCad.ini you can define alternate search path for parts, so you do not
> have to mix official and unofficial parts.
> Also LDView has the possibility to search in different directories.
Additionally, LDView is hard-coded to look in the <LDrawDir>/Unofficial/Parts
and <LDrawDir>/Unofficial/p directories when it doesn't find a part in its
search path. It then attempts to download unofficial parts from the part
tracker into that directory if it can't find the part (assuming the user hasn't
disabled this feature).
It could be argued that the user should be able to configure where unofficial
parts get downloaded to, but I'm not sure I'll ever implement that. The way it
is now basically produces a de-facto standard for anyone using LDView, and
adding a configuration option for this would defeat that.
As it happens, BrickSmith on the Mac has these directories in its search path
also (which was purely coincidental; Allen and I didn't talk about it, and
neither of us was aware of the other's use of that directory at the time we did
our implementation).
Willy has a tutorial and sample MLCad.ini file that sets up MLCad to look in
these Unofficial directories.
--Travis
| | | | | | | | | | | | | | | | | | | | |
In lugnet.cad.dev, Travis Cobbs wrote:
> As it happens, BrickSmith on the Mac has these directories in its search path
> also (which was purely coincidental; Allen and I didn't talk about it, and
> neither of us was aware of the other's use of that directory at the time we did
> our implementation).
>
> Willy has a tutorial and sample MLCad.ini file that sets up MLCad to look in
> these Unofficial directories.
Hi Kevin,
I bet you've already found what Travis's talking about; if not the tutorial can
be found here:
http://www.holly-wood.it/mlcad/ini-en.html#scan
Initially I used <LDRAWDIR>Unofficial_Parts since MLCad was the first prog
supporting unofficial parts but agreed with Travis and Allen to change it to
<LDRAWDIR>Unofficial after the LSC had voted down the proposal.
w.
| | | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad.dev, Willy Tschager wrote:
> In lugnet.cad.dev, Travis Cobbs wrote:
> > As it happens, BrickSmith on the Mac has these directories in its search path
> > also (which was purely coincidental; Allen and I didn't talk about it, and
> > neither of us was aware of the other's use of that directory at the time we did
> > our implementation).
> >
> > Willy has a tutorial and sample MLCad.ini file that sets up MLCad to look in
> > these Unofficial directories.
>
> Hi Kevin,
>
> I bet you've already found what Travis's talking about; if not the tutorial can
> be found here:
>
> http://www.holly-wood.it/mlcad/ini-en.html#scan
>
> Initially I used <LDRAWDIR>Unofficial_Parts since MLCad was the first prog
> supporting unofficial parts but agreed with Travis and Allen to change it to
> <LDRAWDIR>Unofficial after the LSC had voted down the proposal.
>
> w.
Thanks Willy! I'll work on this very soon.
Kevin
| | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad.dev, Michael Heidemann wrote:
> In lugnet.cad.dev, Kevin L. Clague wrote:
> > In lugnet.cad.dev, Willy Tschager wrote:
> > > In lugnet.cad.dev, Kevin L. Clague wrote:
> > >
> > > Hi Kevin,
> > >
> > > > When you say unofficials and custom folders, what are you thinking? Since it
> > > > uses ldglite, there are some rederer features I do not have control over.
> > >
> > > I was refering to the use of unofficial and custom parts and the possibilities
> > > to include them into BI without the need to store them in the <LDRAWDIR>Parts
> > > folder or include them in Parts.lst.
> > >
> > > w.
> >
> > 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 updating the specifications and website.
> >
> > I did not find any "official" specification for alternate pathing of parts. I'm
> > very interested in implementing the standard, or the defacto standard, if I knew
> > where to find an explanation.
> >
> > 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.
> >
> > I also get part length from the titles, so supporting unofficials is important.
> >
> > 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?
> >
> > Kevin
>
> LDView and MLCad shows a way for solving this issue.
> In the MLCad.ini you can define alternate search path for parts, so you do not
> have to mix official and unofficial parts.
> Also LDView has the possibility to search in different directories.
>
> cu
> mikeheide
I understand and respect wisdom of the the LSC's decision to not define where to
store unofficial parts.
I was wondering if the LSC would consider defining how one defines the paths to
unofficial directories? At least that would give us some commonality to the
solution of unofficial parts.
Respectfully,
Kevin
| | | | | | |
