 | | Re: We need an update NOW (Was: Parts Update?)
|
|
(...) Orion, you bring up a great idea that could solve the problem in the interum. Take all the parts you can find on Tore's tracker and in the parts newsgroup, put them in a self extracting archive or .zip file, and post the file somewhere like (...) (23 years ago, 1-May-01, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: We need an update NOW (Was: Parts Update?)
|
|
I've been playing with ldraw and all it's wonderful part for only a short time now. What I don't understand in this discussion is what is the difference in an 'offical' vs 'unoffical' part. Apart from whewre I can download offical part what is (...) (23 years ago, 30-Apr-01, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: We need an update NOW (Was: Parts Update?)
|
|
(...) Ummmm.... Isn't that what the lugnet.cad.dat.parts newsgroup (or Tore's temp parts tracker) is for? You go looking for the part you want and install it. That's what I've been doing. What I wanted when I asked my original question (which has (...) (23 years ago, 30-Apr-01, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: We need an update NOW (Was: Parts Update?)
|
|
(...) The bugger here is that we could play what-if with the schedule all year long. I won't do that. (...) Why not? Aren't the users why the whole LDraw thing happens, anyway? (...) I would, but only to get it done my way -- quick & cheap & dirty. (...) (23 years ago, 30-Apr-01, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: We need an update NOW (Was: Parts Update?)
|
|
I mostly agree so I mostly snipped... (...) How does that help? That is, suppose it would take 40 man hours of work to resolve the bottleneck and get the new process on line and running. If that 40 hours avoids 400 or 4000 hours of user effort, (...) (23 years ago, 30-Apr-01, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: We need an update NOW (Was: Parts Update?)
|
|
(...) Fine, okay, you can call it what you want. The fact remains, something needs to be done. I'm making it known the only way I know how. The delay in the parts update system is becoming pretty unpopular, and it begs the question: is this being (...) (23 years ago, 30-Apr-01, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: We need an update NOW (Was: Parts Update?)
|
|
(...) It can't be "justified", but stamping one's foot isn't going to help, Jeremy, and you know that. I think what we need is an unoffical update. Package them up as unofficial and tell people to take their chances. But realise that there is (...) (23 years ago, 30-Apr-01, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: We need an update NOW (Was: Parts Update?)
|
|
(...) This isn't really a matter of patience; it's been far too long than it needs to be. We need a better system. In the mean-time, the factors contributing to the delay can be addressed, and quickly. e.g. What are the factors holding back the (...) (23 years ago, 30-Apr-01, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: We need an update NOW (Was: Parts Update?)
|
|
"Sproaticus" <jsproat@io.com> wrote in message news:GCMJot.E07@lugnet.com... (...) this (...) Kinda unrelated statement, I intended it to reflect more the project as a whole. I think (and I accept that this will never be the case) that the whole (...) (23 years ago, 30-Apr-01, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: We need an update NOW (Was: Parts Update?)
|
|
(...) I'm not understanding here. The parts are available in file form in a some cluster in some repository somewhere, yes? Publishing them, even in an unofficial process, would simply consist of putting them on a server. There would be little-to-no (...) (23 years ago, 30-Apr-01, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
