To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 7707
7706  |  7708
Subject: 
Re: DAT files: Do No Harm
Newsgroups: 
lugnet.cad.dev
Date: 
Thu, 22 Aug 2002 19:31:11 GMT
Viewed: 
573 times
  
In lugnet.cad.dev, Steve Bliss writes:

8. Try not to fill in an implied part name (where an empty part name implies
previous part) unless necessary (due to edit).

Huh?

I found some model which was (mostly) all 3001.dat, except only the first
line gave the part number! All following lines were meant to be the same
part (with different location.) I guess the author's viewer tolerates this?

So, the rule would be, if the author had left some part names empty, you
should leave them empty, except when that would be wrong.

For example: the editor swaps out one of the middle lines for a new part;
the next line no longer has the same part, so it can't be omitted on that line.



9. Perform smart merges with the file copy to support simultaneous editing

Huh?^2

Suppose you have the model file buffered in a text editor AND the
hypothetical LEDIT type program. The LEDIT type program detects that the
file has been changed. Some kind of "smart merge" is required. If the LEDIT
type program remembers the original file contents, this is not so hard: it
first detects the insertions and deletions, then determines if those overlap
any deletions done on screen. If it's all insertions, the happy solution is
to incorporate the fresh insertions. If a line has been edited in both
places, there could be a choice offered.


10. Try in other ways to format new lines in the way established in the file?
a. when the file has a nice table format, respect that

True.  Tabs vs. spaces?  Space-filled table format?

Here's another one:

10b. Preserve mid-command line breaks.  They're evil, but they can be
useful.  The flip side of this is "fix mid-command line breaks".

Ooh, that is evil. You mean like when there is a line break after the line
type, after the location and after the rotation matrix...



Message has 1 Reply:
  Re: DAT files: Do No Harm
 
(...) Whoa. That's kinda bizarro. (...) I'd say the rule would be, don't fix invalid lines without the authors permission. ;) (...) I see your point, but I would expect most programs to choke (gracefully ;) on the line without part numbers. (...) (...) (22 years ago, 22-Aug-02, to lugnet.cad.dev)

Message is in Reply To:
  Re: DAT files: Do No Harm
 
I don't have any comments, except to say that I agree with pretty much everything you wrote. And that I'd be very hard-pressed to actually implement some of it. And I didn't completely understand all of your points... (...) Yes! (...) Good idea, (...) (22 years ago, 22-Aug-02, to lugnet.cad.dev)

14 Messages in This Thread:





Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR