LDraw.org Discussion Forums
parts.lst: what currently maintained programs use it? - Printable Version

+- LDraw.org Discussion Forums (https://forums.ldraw.org)
+-- Forum: Models and Parts (https://forums.ldraw.org/forum-18.html)
+--- Forum: Parts Authoring (https://forums.ldraw.org/forum-19.html)
+--- Thread: parts.lst: what currently maintained programs use it? (/thread-4877.html)

Pages: 1 2


parts.lst: what currently maintained programs use it? - Orion Pobursky - 2012-05-13

Since Tim Gould has been working on revising mklist, I'm curious what modern LDraw programs actually rely on mklist. The only one I can think of off the top of my head is MLCad.


Re: parts.lst: what currently maintained programs use it? - Roland Melkert - 2012-05-13

I currently don't use it for LDCad, but if the new version is going to include some very dynamic filtering capabilities, i could add support for it so people can share (some of) the bin content with other software.

I'm thinking multiple lists in a dedicated ldraw sub folder (or just the one parts.lst), which will be parsed and used to generate (a) part bin group(s) in LDCad.


Re: parts.lst: what currently maintained programs use it? - Tim Gould - 2012-05-13

If you have any features you'd like me to add please let me know in the thread.

Tim


Re: parts.lst: what currently maintained programs use it? - Roland Melkert - 2012-05-14

I'm not really looking for features myself, more a reason for me to support the file(s) mklist generates.

One being: shared part bin content among software. But the one giant parts.lst isn't that interesting for a single bin group's content, so the possibility to generate multiple files, based on some sort of rule set (or bat oriented multiple calls) would be very powerful in combination with e.g. regular expressions etc.

Any software could then look in e.g. in "<LDraw>" (or some specific subfolder) and read *.lst files for generating (additional) bin content.


Re: parts.lst: what currently maintained programs use it? - Tim Gould - 2012-05-14

I think one file with multiple subsections might be easier.

eg.
Code:
parts.lst:
XXXX.dat    Description
XXXX.dat    Description
XXXX.dat    Description
XXXX.dat    Description
XXXX.dat    Description
unoffical.lst:
XXXX.dat    Description
XXXX.dat    Description
XXXX.dat    Description
XXXX.dat    Description
primitives.lst
XXXX.dat    Description
XXXX.dat    Description
etc.

This would require a major rewrite of my code but could be done I think.

Tim


Re: parts.lst: what currently maintained programs use it? - Roland Melkert - 2012-05-14

Such a format works for me too, if that's the way you prefer it.

But will mlcad and other software skip those lines?

If not you could consider an 'index' kinda setup, a separate file holding the additional 'section' information.


Re: parts.lst: what currently maintained programs use it? - Orion Pobursky - 2012-05-14

The reason I ask is because I feel that this method of doing business is sorely in need of a update. Unfortunately our hands are tied since MLCad is by far the most popular Windows LDraw program and it's not even close to being actively developed. If only Michael would either open source it or hand the reins off to someone more active...


Re: parts.lst: what currently maintained programs use it? - Tim Gould - 2012-05-15

I'd probably do it in another file. eg. LDParts.lst

Tim


Re: parts.lst: what currently maintained programs use it? - Tim Gould - 2012-05-15

Totally agree. I wrote this to ensure I could still use MLCad even if the long descriptions broke it. And then I got carried away.

Tim


Re: parts.lst: what currently maintained programs use it? - Scott Wardlaw - 2012-05-15

I started doing this a while back, but almost nobody cared...

http://forums.ldraw.org/showthread.php?tid=2747&pid=2747#pid2747