 | | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) hmm ... probably it's due to a non-proper knowledge of the english language but now I'm even more confused! as far as I understand we have Ldraw members, which are not part of the community, community members which are not Ldraw members, (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) [snip everything else, good stuff] I think I wasn't clear enough. As you read it, I don't agree either. I meant - this proposal is yet another catalyst to the issue of further organizing and defining LDraw.org. It isn't the LSC's job, but the (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) I don't think that what Kyle is describing is what I have in mind. LDraw.org is the natural group to designate that their will be an LSC committee. The committee is made up of "technically qualified" members. Only members of LDraw.org that are (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) formats. (...) ... (...) I interpret the "set in stone" statement to refer to the language as defined in 027 version of LDraw/LEdit. It is my belief that all the nuances (nucances :^) you mentioned should be described in the 0.27 document. The (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
In lugnet.cad.dev.org.ldraw, Tim Courtney writes: hi tim, (...) could you please sort this out in more detail? does it mean that the "Ldraw.org" file format will support, say 256 colors, no longer required to put dithered colors in subfiles, "set in (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) I think this looks very comprehensive - and I think the idea of choosing a small group of dedicated people to actually take the proposal forward is the way to go. I think this proposal is definitely a step in the right direction. ROSCO (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Resolution
|
|
(...) For general features, the standard rule of thumb is to model details which are 1LDU or larger. To cleanly model some features, you certainly can run into decimal places -- I typically go to 2 or 3 decimal places in part files. Any use of the (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) Dan, there seems to be some confusion here on your part. Hopefully other posters have cleared it up for you, but I want to go on record here on what the vision was. If it wasn't clear from the proposal, that's at least partly my fault since I (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) Sorry, I should have said, "how LDraw.org should function as an organization in the future." -Tim (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) I think you're misunderstanding, perhaps I wasn't clear enough in the proposal. The leaders who set up the LSC are only setting it up, they aren't the initial members of the LSC. These people were self-selected two years ago, based on the fact (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) You're mostly right. I suppose the proposal/message wasn't clear enough (and this is the part I was afraid of it not being clear enough in, so I tried to disclaim it). A couple years ago, the four of us posted this message: (URL) - sometime (...) (21 years ago, 23-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) Hi Dan, (...) Unless I mis-read something, I think this initial group of 5 is the (parent organization) LDraw.org's leadership doing double duty as the initial Ldraw.org Stnadards Comitee for the sole purpose of setting up how the Standards (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Standards Committee (LSC) Draft Proposal
|
|
(...) right. I was saying that the LSC needs to be qualified (as Orion pointed out), AND that the LSC needs more representation from the programmers. Currently, as far as I can tell, it has (from the stats I could gather): Jacob: parts author, (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) Not to worry, combining things is more of a stretch goal (if you'll pardon the pun). Just one is good enough for now. (...) Maybe that's the way to go. I think actually I would go with Band and then hand edit away the 1/2 (of the synthesized (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) Thanks Mike. Meanwhile I just installed make-3.79.1 and it makes lsynthcp OK without needing to install MSys. Gotta think about whether I want Cygwin or not... it's not like I don't have a bazillion other things I should be working on instead. (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) I'll have to scope it out. (...) :^) by your ownb admission you have more experience than me, because I've never done it at all! If you would please I would be eternally gratefull. Kevin (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) You read undocumented code quite well! (...) Yup. But unfortunatly you want to combine open things (tubes) with closed loops (bands), and the program is fundamentally *not* written for that. Bummer. (...) Will the element do for now? Maybe we (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) I think I'll email it to you first this time. It looks like I must have implemented some of the changes mentioned in this thread here. (URL) a fix for the UPPERCASING bug and some stuff for UNITS, LENGTH and subfile NAMEs, but I don't remember (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
"Larry Pieniazek" <lpieniazek@mercator.com> wrote in message news:HDrH7u.1FKp@lugnet.com... [ ... snipped ... ] (...) You can get a full complemnt of Unix utilities for your PC (including Make) by installing Cygwin (which is free): (URL) It has a (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
| |
| | Re: Use of arbitrary elements with LSynth
|
|
(...) OK, I did a little digging. If I understand what I am reading, the various types of things that can be synthesized are defined with constants in the lsynth.h include. Elsewhere in the code these constants are checked (driven by what's found in (...) (21 years ago, 22-Apr-03, to lugnet.cad.dev)
|
