comment on

Bruno Postle has proposed an interesting CAD file format, complete with proof of concept application written in perl.

Concept

If it can be a separate file, then that's what it should be.
- Fast efficient saving
- Fast efficient reading
- Infinite undo
- Changes are easily encapsulated and portable
- Full version tagging and release management
- Embedded resources are kept external
- Fine-grained permissions system
- Platform-independent data
- Object-oriented data

The beauty of this concept is the leverage of existing tools (modern filesystems, versioning, perl/tk, etc.) to provide an elegant example of what is now possible but rarely implemented.

With CVS, multiple authors can work on a single CAD project complete with real time display of all changes as they happen.

Each element of the drawing (an object perhaps; line, circle, etc.) can be described in a simple and human readable text file:

Content-Type: application/drawing; class=line/plain
Version: 1.0
Units: millimetres
0: 10
0: 20
0: 0
1: 10
1: 40
1: 0
License: http://creativecommons.org/licenses/sa/1.0/
Copyright: Jane Doe <jane@example.com>
[download]

Groups of these files make an application which can later be used as a reference, providing object oriented approach to CAD design.

Making the hard things possible...

The author makes these points clear in about "400 lines of perl code." I downloaded the proof of concept application, installed the few modules necessary and it worked perfectly on my Fedora FC2 box. The concepts demonstrated in perl may not provide for the needs of a commercial CAD application and the author states (in various POD comments) that perl is not the solution for long term CAD implementations.

What is profoundly important are the concepts demonstrated. Faced with thousands of text files, perl was the natural solution for parsing and display of this information. With a bit more work, I am certain this proof of concept could surprise more than I with the possibilities of perl/tk and GUI applications to visual data display.

SciDude
The first dog barks... all other dogs bark at the first dog.

In reply to Open Human Readable Computer Aided Design file format by SciDude

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks