 | | | | | | |
| |
|
In lugnet.cad, Leonardo Zide writes:
> In lugnet.cad, Tim Courtney writes:
> > >
> > > This is pretty amazing. Once you get the hang of it, you can add parts to a
> > > model so quickly. Also, once two parts are "connected," moving or rotating
> > > one part moves both parts together, like a submodel.
>
> Looks pretty good, I haven't had much time to try it (at work now) so I
> didn't understand very well how to connect 2 bricks but somehow I was able
> to connect them and it looked nice.
>
> > This is cool! I'd love to see this develop further. Leo - if you're reading,
> > are you coming to BricksWest?? I'd love to sit down face to face again and
> > discuss the future of LeoCAD.
>
> When/where is it going to be?
>
> > > Now if I could just figure out the LeoCAD GUI better...
>
> What's confusing about it? I'd like to hear what other people think and
> fix the problems.
Leonardo:
Two comments:
1. One of my fellow BayLUG members is a *very* pro-Linux.
Much to my suprise he wound up using MLCAD to do his
MOC instruction manuals. When I asked him "why?",
his response has that LeoCAD could not read and write
files that interoperated with MLCAD. My gut reaction
to this statement, is that it should be almost trivial
to get LeoCAD to read MLCAD generated files and write
files that MLCAD can subsequently read.
2. I never found the LeoCAD GUI to be particularly hard, but
I did notice that I never wanted to move bricks around
with the mouse; instead, I always used the keyboard because
I couldn't precisely position anything any other way. It
may be sufficient to add a mode to LeoCAD to allow people
to use LDraw/MLCAD keyboard bindings.
My $.02,
-Wayne
| | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Wayne Gramlich writes:
>
> 1. One of my fellow BayLUG members is a *very* pro-Linux.
> Much to my suprise he wound up using MLCAD to do his
> MOC instruction manuals. When I asked him "why?",
> his response has that LeoCAD could not read and write
> files that interoperated with MLCAD. My gut reaction
> to this statement, is that it should be almost trivial
> to get LeoCAD to read MLCAD generated files and write
> files that MLCAD can subsequently read.
What do you mean by that? LeoCAD has been able to read/write .dat files
for years.
> 2. I never found the LeoCAD GUI to be particularly hard, but
> I did notice that I never wanted to move bricks around
> with the mouse; instead, I always used the keyboard because
> I couldn't precisely position anything any other way. It
> may be sufficient to add a mode to LeoCAD to allow people
> to use LDraw/MLCAD keyboard bindings.
I use the keyboard exclusively too but I never thought that following the
LEdit keys was so important to other people. I'll work on that.
Leonardo
| | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Leonardo Zide writes:
> In lugnet.cad, Wayne Gramlich writes:
> >
> > 1. One of my fellow BayLUG members is a *very* pro-Linux.
> > Much to my suprise he wound up using MLCAD to do his
> > MOC instruction manuals. When I asked him "why?",
> > his response has that LeoCAD could not read and write
> > files that interoperated with MLCAD. My gut reaction
> > to this statement, is that it should be almost trivial
> > to get LeoCAD to read MLCAD generated files and write
> > files that MLCAD can subsequently read.
>
> What do you mean by that? LeoCAD has been able to read/write .dat files
> for years.
Alas, I did not know that. After your telling me, I dug
around the http://www.leocad.org/ site and found:
http://leocad.org/faq.htm#G4
I must have read that a long time ago and forgotten it.
Maybe a GUI tweak to specify the save format? I don't
know.
I will tell my friend that .DAT file reading and writing
are very possible. I will see if that changes his mind.
This should be interesting. I'll report back what I find out.
[...]
-Wayne
| | | | | | |
