On Jul 1 2013 8:13 AM, TJoseph Powderly wrote: > On 07/01/2013 01:11 AM, Michael Haberler wrote: >> >> Am 01.07.2013 um 07:25 schrieb David Bagby >> <d...@calypsoventures.com>: >> >>> Andy, Michael, >>> The network accessibility of the data store and the associated API >>> is >>> key to both providing and understanding the functionality that this >>> approach could provide. >>> Is there a proposed design document that lays out the API? >> >> not yet, this is the time to contribute your thoughts on the issue >> >> the way I envisage it to be is to be rather pythonic than c-ish, >> namely using name/value pairs as arguments rather than say positional >> arguments, which seems to me more suitable to the case and more >> extensible that a C binding >> >> on the operative level what I'll as soon as I'm back do is spin out >> a branch which has protobuf support and zmq examples in place so work >> can start 'in tree' on the issue >> >> - Michael >> >> > will the toolstore be only for linuxcnc or also for machines running > just HAL? > > the python binding key:value sounds to me like a dict for each tool, > > a dict allows different key sets for different tools( the broach has > keys that the grinding wheel does not ) > > will tool related data like spindle rpm and coolant be in the > toolstore?
that is an interesting take on the tool properties issue (ie a dict for each tool). That raises a question though how deeply you want Python to get into LinuxCNC. You might be able to write it all in python (minus the hard real-time bits, and maybe even those). EBo -- ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
