 | | Re: OMR Planning - Almost There
|
|
(...) Yes. That AND the sort of data you are fetching. In certain cases, a DB engine that has cached the results of queries, coupled with a requesting program that can use the results straightaway, can be faster than a raw filesystem, even if the (...) (25 years ago, 4-Jan-00, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Update 9906
|
|
(...) Looks like both John and I mistakenly assumed that s\973s01.dat is the torso missing the front surface - in fact it is missing the back as well to cater for those rare torsos with decoration on the back. I sent a corrected version of 973p34 to (...) (25 years ago, 4-Jan-00, to lugnet.cad.dev)
|
| |
| | BlockCAD version 2.1 is out!
|
|
Hi all! I'm happy to announce version 2.1 of BlockCAD, my LEGO building program! BlockCAD: (2 URLs) The big thing in this release is that pieces can be placed anywhere in X, Y and Z, not limited to a stud width/height increment anymore. This makes (...) (25 years ago, 4-Jan-00, to lugnet.announce, lugnet.build, lugnet.cad)
|
| |
| | Re: OMR Planning - Almost There
|
|
(...) I have to wonder about that assertion in a really skeptical way. In either case, assuming the filesystem and the database aren't poorly written, the amount of RAM in the server is really the gating factor. If you have 50 MB of static files and (...) (25 years ago, 4-Jan-00, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: part 2951, some questions
|
|
(...) I'd say that's a good place to put the origin. On the other hand, the user is fairly likeliy to tilt the bucket off an axle in either the upper or the lower pegholes, so centering the part in the centre of either the upper or lower pegholes (...) (25 years ago, 4-Jan-00, to lugnet.cad.dev)
|
