 | | ...large project anyone?
|
|
--SNIP-- (...) I'm going to go a bit more general here so this is an answer to both parent and grandparent and probably other relatives too. -- Why does one person need to do the whole thing? We have a wealth of skills and experience in the Lego CAD (...) (19 years ago, 18-Jul-05, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: LSC - request for defining a WORKING connection database standard
|
|
(...) nod, yes. (...) Add to this the fact that to get a working connection-enabled tool, you need start with (or at least develop along the way) a working GUI-based editing tool. That really narrows the field of potential (...) (19 years ago, 18-Jul-05, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: LSC - request for defining a WORKING connection database standard
|
|
(...) Hi Willy, I think "working" needs a tool. 1. there is a tool 2. there is a developping database There is no chicken-egg problem: the tool always precedes the database. Would you model parts without MLCad, LeoCad or LDraw? I doubt anybody (...) (19 years ago, 18-Jul-05, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: LSC - request for defining a WORKING connection database standard
|
|
(...) Note that Rosco already did take a crack at a few, including generating some images for them, and in doing so, found a problem in one I created, and caused me to decide to add fields to the connectionTypeBox, which is goodness. Thanks! (...) I (...) (19 years ago, 18-Jul-05, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: LSC - request for defining a WORKING connection database standard
|
|
(...) While a connection database could be helpful, I just cant help thinking that a relationship/constrain system like solidworks and Pro/Engineer use could acheive a lot more. It could certainly be a start, then simplified - so the CAD (...) (19 years ago, 18-Jul-05, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: LSC - request for defining a WORKING connection database standard
|
|
I'm not sure where this standard definition is at these days, or whether it could be used to automate what I'm doing by a clever MetaWiki robot coder, but I (and others) started capturing some connection information in BrickWiki ( (URL) ) You can (...) (19 years ago, 17-Jul-05, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dev.org.ldraw)
|
| |
| | MBC 3 Trial and Plugins Developer Kit Trial
|
|
Gudday Mac and MBC users, I've been quiet for a few months now, during this time, MBC 3 has been one of the projects. Version 3 is an all new version with new ideas and functionality (eventually). New current features include: - Cut, Copy and Paste (...) (19 years ago, 25-Jun-05, to lugnet.cad.dev.mac)
|
| |
| | Re: Making easier to reinstall ldraw
|
|
(FUT lugnet.cad.dev, which is where this reply really belongs.) (...) isn't in the LDView 3 Beta 1 release, but all the unnoficial test releases I've made since then (Beta 1A through Beta 1E) use his code. And if you build LDView yourself from its (...) (19 years ago, 26-May-05, to lugnet.cad, lugnet.cad.dev, FTX)
|
| |
| | Re: Question for the LSC. Blanks in file names legal?
|
|
(...) Travis, I have done the same in LPub. Easier to implement it than explain it every time someone gets burned. Kevin (...) (19 years ago, 16-May-05, to lugnet.cad.dev)
|
| |
| | Re: Question for the LSC. Blanks in file names legal?
|
|
(...) (Note FUT lugnet.cad.dev) I realize that spaces are officially a no-no, but since I've also seen files that contain references to sub-models with spaces in the filenames, I'm adding support for this to the next LDView release. It will generate (...) (19 years ago, 15-May-05, to lugnet.cad, lugnet.cad.dev)
|
