>> If needed, I can build a downloadable release; if that's desired.
>> [Philo, are you willing to ascertain whether there are any bugs that
>> make it unshippable before I do; once I figure out the 6.0 issue for
>> you?]
>>
>Leonardo already answered... Though building the last version is
>interesting to see where LeoCAD is heading for us hard core users, it is
>definitely not good yet for general release (pending modifications in
>submodels).
Well, John wanted to see a alpha or beta. I figured others might, too.
I've gotten spoiled by Travis and his LDView releases :)
>> In the meantime, Leonardo, do you think ldconfig.ldr support is a
>> good idea? I'd like for LeoCAD to use TLG naming, with perhaps a
>> switch to LDRAW naming on demand if the user wants (after all, you
>> use your own format now anyway, so sticking with LDRAW naming seems
>> not-entirely-necessary).
>>
>> What do you think?
>Since I have to cope with MLCad (you know I hate that ;o) also for LPub
>renderings, I definitely don't want to have to deal with two different
>names for each piece!
Not piece names, color names.
With ldconfig.ldr support, you could have any names you liked -- it will all
still use LDRAW numberings (there's no way I'm going to convince anyone to
get away from that), you could swap out the ldconfig.ldr I'd like to supply
with
the "official" one on LDRAW.org, and have all their names for your LeoCAD
implementation, even.
What I was suggesting was that LeoCAD support both official naming for
colors, as well as LDRAW naming for those who wanted to turn that on, and
was asking for feedback on making official naming the default mode.
ldconfig.ldr
support puts total control of the naming and color values ultimately in the
hands
of end-users; I was talking about having LeoCAD go the "step further" and allow
a switch between naming systems within the software with no extra work.
What I'm advocating is a Good Thing. It's standards-compliant, and
end-user-friendly to the extreme.
As someone who has been generating his own element images for quite a long
time now, I have to say; switching to official color values has a huge impact
on
the realism factor when viewing one's LEGO work (CAD-wise, the realism jump
from using POVray is another topic). My original intent was simply
to work with Leo to get the right RGB values into LeoCAD, but then people
have been asking for "more" colors (I wouldn't mind seeing this myself), and my
mind started to go wild: one could set LeoCAD to not show discontinued colors,
or only "permanent status" colors, or even only the colors that go with a
certain
product-line area (such as: don't show me DUPLO-only colorings). That last
part I don't readily have the data for (yet), but I do have all the other info
readily
available to work from.
-- joshua
_______________________________________________
Leocad mailing list
[email protected]
https://list.gerf.org/listinfo/leocad
