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
Whatever you want to achieve can be done in C / C++, dicts, hash tables,
dawgs etc.
There are C/C++ apis for all the databases too
Given that
I like python and find it easier to understand and write programs in and
hope more of LinuxCNC can use it. But I don't have a clue if that makes
any difference in the overall scope of things.
JT
On 7/2/2013 5:51 AM, Schooner wrote:
the way I envisage it to be is to be rather pythonic than
Do you have a git branch set up for this? I'd like to follow along with
the SQL and Python part, I've tried to learn C and C++ but don't get
very far.
JT
On 7/2/2013 6:42 AM, andy pugh wrote:
On 2 July 2013 12:36, John Thornton bjt...@gmail.com wrote:
I like python and find it easier to
On Tuesday 02 July 2013 08:03:14 John Thornton did opine:
Do you have a git branch set up for this? I'd like to follow along with
the SQL and Python part, I've tried to learn C and C++ but don't get
very far.
JT
C++ I never got the overall picture of John, but C itself I tend to look at
Am 02.07.2013 um 13:53 schrieb John Thornton bjt...@gmail.com:
Do you have a git branch set up for this? I'd like to follow along with
the SQL and Python part, I've tried to learn C and C++ but don't get
very far.
I'll spin out a branch containing the protobuf support machinery plus zmq
Thanks
On 7/2/2013 11:05 AM, Michael Haberler wrote:
Am 02.07.2013 um 13:53 schrieb John Thornton bjt...@gmail.com:
Do you have a git branch set up for this? I'd like to follow along with
the SQL and Python part, I've tried to learn C and C++ but don't get
very far.
I'll spin out a branch
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
On 6/30/2013 10:36 PM, Chris Morley wrote:
Date: Sun, 30 Jun 2013 22:25:20 -0700
From: d...@calypsoventures.com
To: emc-developers@lists.sourceforge.net
Subject: Re: [Emc-developers] toolstore discussion notes: Andy/mhaberler
Andy, Michael,
The network accessibility of the data store
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
On 07/01/2013 09:13 AM, TJoseph Powderly wrote:
--- snip ---
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 )
--- snip ---
thx andy thx michael
tomp
haha the
On Jul 1 2013 10:06 AM, TJoseph Powderly wrote:
On 07/01/2013 09:13 AM, TJoseph Powderly wrote:
--- snip ---
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 )
---
2013/7/1 TJoseph Powderly tjt...@gmail.com
will the toolstore be only for linuxcnc or also for machines running
just HAL?
Could you, please, explain, why would it make sense to have it also in
HAL-only setup?
The way I see it is that all the tool offsets etc and tool change
operations are
On 07/01/2013 12:56 PM, Viesturs Lācis wrote:
2013/7/1 TJoseph Powderly tjt...@gmail.com
will the toolstore be only for linuxcnc or also for machines running
just HAL?
Could you, please, explain, why would it make sense to have it also in
HAL-only setup?
The way I see it is that all the
Am 01.07.2013 um 16:13 schrieb TJoseph Powderly tjt...@gmail.com:
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
Am 01.07.2013 um 16:20 schrieb EBo e...@sandien.com:
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
Am 01.07.2013 um 21:33 schrieb TJoseph Powderly tjt...@gmail.com:
On 07/01/2013 12:56 PM, Viesturs Lācis wrote:
2013/7/1 TJoseph Powderly tjt...@gmail.com
will the toolstore be only for linuxcnc or also for machines running
just HAL?
Could you, please, explain, why would it make
Michael,
hello and thanks for the input
On 07/01/2013 03:06 PM, Michael Haberler wrote:
---snip---
will the toolstore be only for linuxcnc or also for machines running
just HAL?
I would see using entities to be: interpreter, UI's, RT comps which access or
change tool information
so
On Mon, 1 Jul 2013 22:09:21 +0200
Michael Haberler mai...@mah.priv.at wrote:
Am 01.07.2013 um 16:20 schrieb EBo e...@sandien.com:
hat raises a question though how deeply you want
Python to get into LinuxCNC.
No, it does not; a key/value pair-based API does not imply any
language.
You
This is a short summary of Andy's and my discussion of the issue at Wichita,
and several longer offline discussions before that. It sketches how in the
future the handling of tool information (and likely all persistent data) will
be handled in LinuxCNC.
1. the storage and retrieval of all
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?
Dave
Date: Sun, 30 Jun 2013 22:25:20 -0700
From: d...@calypsoventures.com
To: emc-developers@lists.sourceforge.net
Subject: Re: [Emc-developers] toolstore discussion notes: Andy/mhaberler
Andy, Michael,
The network accessibility of the data store and the associated API is
key to both
21 matches
Mail list logo
