 | | Re: Part Numbering Crisis in LDraw
|
|
(...) I concur. Part of the beauty and flexibility of LDraw is that you can model with parts in colors that those parts don't come in. Once we start down the road of having parts hard coded only in the color(s) they really exist in, we limit our (...) (26 years ago, 27-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Java LDraw/LDLite
|
|
[lugnet.cad removed from Newsgroups header] (...) Yes, it's fairly easy to write an HTTP daemon in Perl. Pre-forking and load balancing and shared memory for optimal usage is a little more difficult. But in either case, it's just a one-liner in the (...) (26 years ago, 27-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Quality of authored parts
|
|
(...) Your output reflects this high standard. You are always willing to take criticism on your parts and try to improve them where needed. No one is offended, inspired, if anything. -John Van (26 years ago, 27-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Part Numbering Crisis in LDraw
|
|
(...) Is it not possible to say in the definition of 410etc., like: top half yellow, lower half yellow underneath. That way, the only information in the 410etc file is the color, and which constituents parts there are. Then if anything needs to (...) (26 years ago, 27-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Java LDraw/LDLite
|
|
(...) You can use FastCGI ((URL) to have one process (or a fixed group of processes) serving CGI requests so you don't have the overhead of restarting the process (interpreter or otherwise) for each request. I used it for the Lego set database I (...) (26 years ago, 27-Feb-99, to lugnet.cad.dev)
|
