What is the background to this? The reason I wanted a new file format (and this still applies) is to enable the kind of forking/merging workflow that we enjoy when writing software - this being a prerequisite for a proper sharing economy for physical things built around open designs. In all other circumstances it is probably simpler to reuse an existing format.
But this way of working would require some basic changes to the way CAD software works, it isn't enough to just add another parser/serialiser to an existing tool.
--
Bruno
Hello.
What about resurrecting your project?
EdaCore was another failed try...
FOSDEM is there. There's discussions about it in geda-users...
Are you still alive?
CAD-software is very extensive, collaboration is necessary.
Collaboration needs standards and basic tools.
Standards not only for the exchange-format, also for the basic functions of the binary-cad-base, the viewer, the geometry-module, the format-exchange-modules, and the user-interface should be defined.
With basic rules for non-standard object-types or object-attributes.
Where can i find a description of the "BRL-CAD's .g geometry file format" (sorry - did not find it with google) ?
Franz
This sounds great, the threshold for me would be: if I was able to put
a CAD project on github, let other people fork and edit it using
different tools, then pull and merge their changes without corrupting
the data, then I have a CAD file format that the whole world will have
to adopt eventually. There is no point designing new file formats
unless this is the aim.
This doesn't _have_ to use text files, it would still work ok with
custom diff/patch tools that know about the file format internals
(since every object would need to have a persistent GUID, this GUID
has to make it into every patch file).
ISO 10303-21 starts with:
.. neither this ISO standard nor any extract from it may be reproduced, stored in a retrieval system or ..
- is this an OPEN cad format ?
ad:
" IFC format (https://en.wikipedia.org/wiki/Industry_Foundation_Classes)"
for me this format (it is STEP) is -
- is not really free (CHF 178 for the spec! See eg:
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=33713
- is extremely complicated
- but - really great: it is ascii-text.
ad:
GCV and http://brlcad.org/w/images/2/2d/BRL_CAD_g_format_V5.pdf:
when would it be possible to eg import some objects in DXF,
modify some coordinates, export also as DXF ?
ad "Initial filtering does not yet include individual coordinate editing ..":
With "modify some coordinates" i did mean:
- start a plugin (a user-function) doing:
- get object(s) out of (with cad-function)
- modify object(s) (user function)
- store back to Cad-DB (with cad-function)
This would mean that the Cad-system provides functions:
- import file into Cad-DB
- export Cad-DB into file
- get object(s) out of Cad-DB (into memSpace, binary)
- store object(s) in Cad-DB
Is this correct ?
Franz
HiI am from India. I am both a practising architect and also a researcher in the field of architetural representation systems. Initially I was only practising and had the proverbial frog-in-the-well effect, sitting in one corner oblivious about what is happening elsewhere. India got the www only in 1996 and it was extremely slow and costly too.Being isolated had its advantages too, I guess. I developed a BIM system based around spaces; instead of built-matter. Architecture has a "figure-ground" epistemology issue. We need to represent both the built matter as well the space. But one forms the background of the other. Traditional CAD and even conventional BIM discards representing spaces. After all, when the building is built, we do not have to "build" the space. By the virtue of building what is to be built, the spaces emerge.
--
You received this message because you are subscribed to the Google Groups "open_cad_format" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open_cad_form...@googlegroups.com.
To post to this group, send email to open_ca...@googlegroups.com.
--
Hi Sabu
I have looked at your project once before and think it sounded interesting.
In this forum we are discussing free and open formats, opensource and/or GNU software. What do you have to add to that sphere of work.
Last time I looked I couldn't find the code for TAD. I also can't find anywhere documentation of the file format(s) your software uses.
Please share your knowledge in this context of freedom in formats and software. Not just free as in no-cost but free as in freedom.
Best regards
Duncan
--
Sendt fra min vanilla Android mobil