Good day gurus, Just FWIW, I'd like to share my view as a newbie hobby machinist using EMC regarding the tool table.
> I'm proposing a much more moderate goal: to encode the current EMC > tool table such that it can be reused by other programs, and with some > self-description features (field names, types, version number, machine I think this is a noble goal. Also, dxf2gcode was mentioned as likely sharing this information. For a hobbyist like me, being able to easily link the bits in the chain from CAD to the part with the lesser possible amount of fiddling is immensely useful. I envision drawing a part, feeding dxf2gcode with the drawing and the tool table, and from there to AXIS with no steps in between. That'd be great for guys like me, who need to get things going but are not professionals and therefore can't be expected to posess a level of knowledge and skill even remotely comparable to people who machine for a living. As for formats, I'm somewhat used to editing XML because of certain professional tasks (configuring Cisco phones by hand being the most tiresome). While at first daunting, XML is very readable and editable if decently indented. Also, you can't break well-formed XML adding data, which is great in general but specially for rapidly evolving software like EMC2. Whenever I have the choice, I usually choose XML above any alternative. -- Alfredo Sola ASP5-RIPE http://alfredo.sola.es/ ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users