Re: [K3d-development] This could have been done completely with K-3D,

[Daniel S. M. <dsm...@gm...>]

On Wed, Dec 16, 2009 at 4:39 PM, Daniel Scott Matthews
<dsm...@gm...> wrote:
> On Wed, Dec 16, 2009 at 4:17 PM, Timothy M. Shead <ts...@k-...> wrote:
>> Let's all try to be a little more constructive:
>>
>> * The website is a huge improvement over what we had, which was just a wiki.
>>  It lacks a decent gallery and examples, but that's on the todo list.
>>  Hopefully, much of the material going in (like downloads, getting started)
>> is more focused, more professional than the wiki, and easier to understand.
>>
>> * Dan, weren't you going to look into CNC/CAD type formats that we might
>> support?
>>
>
> If we have fully functioning STL I/O we are set to go, unless you want
> to get into g-code output. i.e. tool path planning. If you look at an
> opensource project such as http://www.reprap.org/bin/view/Main/WebHome
> you will find that STL is all you need as the code driving the
> machines will know best how to parse it into the required g-code or
> commands for whatever hardware drivers they are using.
>
> Fully functional DXF/DWG and COLLADA I/O are always handy as they fill
> in 95% of the gaps for a CNC/CAD use cases. By that I mean part level
> I/O with attributes not just a single combined mesh.
>

Having said that, I have just found this:

http://code.google.com/p/heekscnc/

Which looks like a good reference of how to implement g-code output
via 3D tool path planning.