<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Wolfgang Spraul wrote:
<blockquote cite="mid:0B07D581-520B-46BE-9705-16850076554C@openmoko.com"
type="cite">Jeremiah -
<div>thanks for the information, that is indeed very helpful.</div>
<div>Your list includes DXF, that was the preference before.</div>
<div>I am concerned that the export process will corrupt the file and
we release a file that will be painful to actually use.</div>
<div><br class="webkit-block-placeholder">
</div>
<div>From the formats you listed (Wavefront, DXF, STL), which is your
preference?</div>
<div>Which one do you believe is a format where Pro/E can export all
information into, without loosing much?</div>
</blockquote>
I'm not very familiar with internal structure/format of DXF files, but
have written software that uses STL and Wavefront files. I'll answer
to the best of my knowledge.<br>
<br>
The most information would be lost with STL files. DXF files would
likely loose the least information and Wavefront would be somewhere
between. This is dependent on how good the converters in ProE are.
Often only the most basic features of the Wavefront format are
implemented in applications and a surface description equal to or only
slightly better than a STL file is achieved. This could also apply to
DXF files, depending on the quality of the converter and the app that
reads them in, but I bet the converter in ProE is pretty good.<br>
<br>
One issue is there are many versions of the DXF file format. A quick
search shows Blender supports a subset of objects up to DXF version
2007. Art of Illusion only loads from ASCII DXF files and is limited
to vertex information. Of course as long as the conversion is good
& loads well for a couple apps, we could do additional conversions
on our own.<br>
<br>
I believe an ASCII DXF format would be more accurate for most people
and lose the least amount of information in the conversion. There may
be fewer version compatibility issues with Wavefront files, but DXF
readers can also often read newer files than they were designed for at
a lower level of detail.<br>
<br>
Jeremiah<br>
<br>
<blockquote cite="mid:0B07D581-520B-46BE-9705-16850076554C@openmoko.com"
type="cite">
<div>Thanks,</div>
<div>Wolfgang</div>
<div><br>
<div>
<div>On Jan 17, 2008, at 10:37 AM, Jeremiah Flerchinger wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div bgcolor="#ffffff" text="#000000"> <font
face="Helvetica, Arial, sans-serif">I don't think ProE by itself is
suitable, especially since you need a copy of ProE even to import it to
BRLCAD. I myself would suggest Wavefront (.obj), ASCII DXF (.dxf), or
STL (.stl) file. All are standard formats & should be in ProE and
any other 3D editor.<br>
<br>
Instructions for converting from ProE to STL are as follows:<br>
<br>
ProE<br>
<br>
* File > Export > Model<br>
* STL<br>
* Set chord height to 0. The field will be replaced by minimum
acceptable value.<br>
* Set Angle Control to 1<br>
* OK<br>
<br>
ProE Wildfire<br>
<br>
* File > Save a Copy > Model<br>
* Change type to STL (*.stl)<br>
* Set Chord Height to 0. The field will be replaced by minimum
acceptable value.<br>
* Set Angle Control to 1<br>
* OK<b><br>
</b><br>
I'm sure the process would be similar to convert to either of the other
2 formats.<br>
<br>
Jeremiah Flerchinger</font><b><br>
<br>
</b><br>
<br>
Wolfgang Spraul wrote:
<blockquote
cite="mid:7E693315-C660-45AA-B78A-0D711F330C01@openmoko.com"
type="cite">Esben - <br>
Interesting. I checked on BRLCAD's website <br>
<br>
Converting Geometry Between BRL-CAD and other Formats, Page 17 <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://ftp.brlcad.org/VolumeIV-Converting_Geometry.pdf">http://ftp.brlcad.org/VolumeIV-Converting_Geometry.pdf</a>
<br>
<br>
and it seems Pro/E import is actually quite solid. However you need a
seat of Pro/E to do the conversion. <br>
Is releasing in Pro/E format (.prt and .asm files) an acceptable way? <br>
Wolfgang <br>
<br>
On Jan 17, 2008, at 2:36 AM, Esben Stien wrote: <br>
<br>
<blockquote type="cite">Wolfgang Spraul <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E" href="mailto:wolfgang@openmoko.com"><wolfgang@openmoko.com></a>
writes: <br>
<br>
<blockquote type="cite">Regarding the format, the original is
in Pro/Engineer Assembly <br>
(.asm) and Part (.prt) files. That's probably hard to digest for any <br>
FOSS CAD software. <br>
</blockquote>
<br>
BRLCAD[0] has preliminary support for this format. <br>
<br>
[0]<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://brlcad.org/">http://brlcad.org/</a> <br>
<br>
-- <br>
Esben Stien is b0ef@e s a <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www">http://www</a>. s t n m <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="irc://irc">irc://irc</a>. b - i . e/%23contact <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="sip:b0ef@">sip:b0ef@</a> e e <br>
jid:b0ef@ n n <br>
<br>
_______________________________________________ <br>
OpenMoko community mailing list <br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://lists.openmoko.org/mailman/listinfo/community">http://lists.openmoko.org/mailman/listinfo/community</a>
<br>
</blockquote>
<br>
<br>
_______________________________________________ <br>
OpenMoko community mailing list <br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://lists.openmoko.org/mailman/listinfo/community">http://lists.openmoko.org/mailman/listinfo/community</a>
<br>
<br>
</blockquote>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</body>
</html>