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 / 2878
2877  |  2879
Subject: 
Re: DAT format question
Newsgroups: 
lugnet.cad.dev
Date: 
Wed, 22 Sep 1999 02:26:07 GMT
Viewed: 
559 times
  
"Gary Williams" <graywolf@pcpros.net> writes:
For example, it shouldn't allow the user to add primitives directly
to a model,

Why not?  I've done this when a part didn't exist (I used a box.dat for
the center of the 1x2x2 shock absorber)

Also, the color selector would only display codes 16 and 24 when
editing a part or primitive,

Part developers often use different colors to make sure shapes are
matching up correctly.  Also, atterned parts and some other parts
(electric parts) require specific colors other than 16 and 24.

but allow any color for a part reference in a model or subassembly (or,
at >least, something along those lines).

Make sure you allow parts of models to be color 16.  That helps in
playing with color schemes.

In other words, the user's ability to manipulate an object should be
restricted to only those actions that are in context for that object.

I would try to limit the amount of restrictions as much as possible.

However, it seems that any type of file can be stored in any of the
usual suite of directories, and the program is supposed to allow this
to be compatible with the other CAD packages.  This means that the • parser
will have to be able to somehow analyze the contents of a file to • determine
what kind of object it contains.

Is this really necessary?  After all, the format of all the types of
files is the same. (parts reference primitives as if they were parts,
models use submodels as if they were parts)

The only other alternative I can think of would to have sub-menus on
the File/Open and File/New menus, one for each file type.  Then it would

be up to the user to tell the program what type of file he was about to
work with.

I think this would be best.  Let the user choose which interface
(primitive, part, model) (s)he wants to use.
--Bram


Bram Lambrecht           / o   o \           BramL@juno.com
-------------------oooo-----(_)-----oooo-------------------
    WWW:   http://www.chuh.org/Students/Bram-Lambrecht/
-----------------------------------------------------------



Message has 1 Reply:
  Re: DAT format question
 
Bram Lambrecht wrote in message <19990921.200045.509...no.com>... (...) My experience has been that as flexibility increases, complexity increases. I'm usually quite anal about coding objects to always behave in a very structured, predictable (...) (25 years ago, 22-Sep-99, to lugnet.cad.dev)

Message is in Reply To:
  Re: DAT format question
 
My original plans called for my CAD package to distinguish among the various kinds of DAT file. This would allow the program to know when it was appropriate to enable certain editing features. For example, it shouldn't allow the user to add (...) (25 years ago, 21-Sep-99, to lugnet.cad.dev)

27 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