|
The it would be slick to have the LCD info in the dat file, but
it might complicate issues being dicussed by the Ldraw committee : (
It seems that pov style includes aren't allowd in official files either
so maybe keeping it seperate for a while will be easier...
I'd be willing to take a stab at writing some "click" files : )
Actually, I was thinking of writing a quick vb app that parsed dat files
and automatically genrates LCD info for parts that have stud and tube
primitives. I bet that'd save a lot of time.
LMKWYT
-JSM
Dan Boger wrote:
> On Tue, Jun 22, 2004 at 01:40:04PM +0000, Dan wrote:
>
> > To see the standard so far take a look at:
> >
> > http://www.mr-bucket.co.uk/GLIDE/LCD_File_Format.html
>
>
> Should the format perhaps be changed so that LCD info could be included
> inline in a valid DAT file? Perhaps make all the lines start with a "0
> LCD" before anything else? Then, when reading a DAT file, a program can
> recognize and parse LCD info, in addition to looking for the .lcd file.
>
> Does that make sense? Do you think it's worth the effort?
>
> I think connection data is really cool, and we should try to make it
> part of the standard library.
>
|
|
Message has 2 Replies:
Message is in Reply To:
35 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
|
|
|
|