Re[8]: emc really needs a copyleft cad/cam package

["Terry L. Ridder" <terrylr-at-blauedonau.com>]

hello;

i received a few messages concerning the proposed
project i would really like to take a moment and
provide some further insight.

some decision have already been made.

a. all source code and design documents on sourceforge.net
b. project mailing list hosted by one of my servers.
   1. there is absolutely no need to be distracted by
      ads, spam, etc.
   2. there is absolutely no need to provide any personal
      information other than a valid e-mail address to
      join project mailing list.
c. the project will always be gnu gpled.
   1. gnu general public license is the best known
      and the most "lawyer-proof" of the opensource
      licenses.

1. to answer the questions concerning the design
   phase.

certain parts of the design phase will take time
there is no doubt about that. however, several
parts of the proposed project already have design
documents written.

   i. file formats and output formats.
    a. dxf file format
    b. hpgl standard as published by hp.
    c. rs274ngc written by nist employees.
    d. fig format 3.2 (facility for interactive generation of figures)
    e. iges file format standard.
    f. stl file format standard.
    g. povray syntax
    h. rayshade syntax
    i. radiance syntax
    j. dwg file format

   ii. human machine interface
    a. written again by nist employee.

there is already usable code which is usable.
   iii.
    a. new version of rs274ngc from emc/rcslib written by nist.
    b. older version of rs274ngc from emc/rcslib written by nist.

there are several gpled graphics/math libraries available.

there are already several filter/translator utilities released
under gpl.
    a. transfig
    b. ghostscript (yes ghostscript is a filter/translator)
    c. hp2ps, ps2hp, fig2dvi, etc.

physical properties of materials and cutting tools characteristics
are obtainable from machinist's handbook, several reprints from
lindsay books.

in some sense yes we are starting from scratch in another
sense we are not starting from scratch. there is a need for
this project that being we need a package designed from the ground
up to output g-code.

before people start jumping to conclusions allow us time
to compile all the documents and get the discussion going.

we have had good input already just in the few days
we have been discussing the proposed project.

here is what we have as of today.

1. multi-os:
   a. linux (this also covers netbsd/freebsd/openbsd/solaris/etc)
   b. windows
   c. macos

2. scriptable
   a. python
   b. perl
   c. e-lisp
   d. povray
   e. read g-code and draw module based on it.
   
3. greater than 3-axis:
   a. hexapod capabilities.
   b. vertical rotary table (y-z plane or x-z plane)
   c. horizontal rotary table (x-y plane)
   d. pitch, roll, yaw of z-axis.

4. familiar user interface
   a. autocad like

5. programming language
   a. will not be using.
      1. java
   b. will be using.
      2. yet to be determined

6. inter-module communication
   a. first choice - corba (common object request broker architecture)
   b. others yet to be determined.
   c.  last choice - com   (component object module)

7. machine interface
   a. tool path generation and editing.

8. library of physical properties of material to be machined.
   a. estimated time of machining.
   b. suggested depth per cutting pass.
   c. suggested feed rates.
      1. rough cut feed rate.
      2. finish cut feed rate.

9. cutting tool library.
   a. physical characteristics of cutting tools.
   b. suggested feed rates.
      1. rough cut feed rate.
      2. finish cut feed rate.

-- 
Terry L. Ridder
Blue Danube Software (Blaue Donau Software)
"We do not write software, we compose it."

digging deep, i feel my conscience burn
i need to know who and what i am
this hunger jolts me from complacency
rocks me, makes me meet myself
----kendall payne---closer to myself---