 | | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) This problem is not due to the Swedish character set, but rather a problem with the Lugnet web interface. The Lugnet web interface does not support RFC2047 encoded header fields, that explains the problems with the subject line. I have (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw Versioning (Was Re: Backwards Compatibility)
|
|
[snip] (...) Tim: For those who do not know, W3C stands for World Wide Web Consortium and it is the organization that is responsible for web standards such as HTTP, URL, HTML, XML, etc. Before I get into the details of how W3C operates, let me start (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw Versioning (Was Re: Backwards Compatibility)
|
|
Ok...replying to myself here... (...) Also, Wayne, since we're on the topic of standards bodies, would you mind sharing with the community some of your thoughts about this, based on your past term(s) as Sun's representative to the W3C? Guys - (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw Versioning (Was Re: Backwards Compatibility)
|
|
Ok, picking up where I left off with the previous post. (...) The group charged with working on this was Steve Bliss, Jacob Sparre Andersen, Terry Keller, Larry Pieniazek, and myself. There hasn't been much activity among the four of us as of late, (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw Versioning (Was Re: Backwards Compatibility)
|
|
(...) I think you picked a great spot to come in at. (...) Yep: format evolution = good. (...) Good idea. I'd also like to add that such a standards body should be relatively few in number. Not to be exclusionary, but to maintain focus. The number 7 (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) True. That's why I suggested a strong recommendation of using whatever comment prefix we will agree on. Then let's say the future L3P -check will raise a warning for omitting that prefix. /Tore (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw Versioning (Was Re: Backwards Compatibility)
|
|
This thread has grown so much since Friday it's hard to know exactly where to interject.... so I just picked a spot. I'll have more to say later after reading the thread again but wanted to throw a few comments out. (...) YES! Exactly. And one could (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) As Steve would say - LDraw and LEdit exist as a benchmark. I would add - for the _original_ LDraw spec - that is, everything LDraw/LEdit can do. 1.0.0 spec, which is essentially what Kevin is working on - documenting all meta-commands up to (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) We already have a standard comment prefix: 0. For better or for worse, meta-commands are just comments that get interpreted to have meaning. I think it's unrealistic to expect users to remember to add a second comment prefix in addition to the (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
Orion Pobursky wrote: What are we going to do when DOS support in PC OS's goes away completely? I have run into this problem with Windows XP, not so much with LEdit and LDraw--I use L3P more often. Thankfully, there is still a Win98 SE computer in (...) (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw Versioning (Was Re: Backwards Compatibility)
|
|
(...) Excellent suggestion, Wayne. (...) I like this - with one reservation. We should only focus on documenting 1.0.0 right now. Additions, which would go in a future version (1.1.0) are being openly discussed. Actual decisions on that version (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) I disagree. Let's stick with the current method of meta-commands until a standards body officially determines the syntax of future generation commands. No hold on anything, innovation can continue (just in the same disorganized fashion it (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) If tags were the way to go, I agree. BUT, ultimately I side with Kevin, just add comment marks, not meta-command ones. I think that option makes the most sense. But as Dan also said, I'm not a programmer who will be implementing this, so I (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) This is all the main idea behind my suggestion for a branch of the namespace to be considered 'open to all' without discussion. I originally suggested 0 APP appname COMMAND but now I wonder if 0 UNOFFICIAL appname COMMAND, or something (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Well this was one of the reasons behind my original suggestion. (This thread sure did take off while I was away skiing this weekend.) I suggested that a new meta command group be made today, albeit before the creation of a standards body, so (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Ah, I see the confusion. In saying //, what I really meant was "0 //", where // is the meta-command that means comment. Rather than place all new meta-commands in <>, or (), or {}, I'd rather have a token that means "the rest of this line is a (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) As I tried to indicate in one of my posts much earlier in this thread, I realized after my original post that the presense of the {} would negate the need for a {META} tag. It would probably work just as well with (). The whole reason I (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | LDraw Versioning (Was Re: Backwards Compatibility)
|
|
(...) All: There are gazillions of file formats out there and most of them have had to undergo some amount format evolution. Format evolution is a healthy and common situation. A common first step towards evolving a file format is to introduce a (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) What I mean is: (URL) for example. Quite corrupted and hard to read - even for us who understand Swedish. ;-) I don't know whether brackets will be cause the same kind of problems, but there is a risk. Then a line from a posted part or model (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) I don't know about American keyboards, but at my Swedish kb, '{' and '}' are at AltGr+7 and AltGr+0, and it collides with Swedish special characters in the ASCII table; it has to be set on codepage 850 or whatever it was. I find them somewhat (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
