On 21 April 2014 03:30, Kirk Wallace kwall...@wallacecompany.com wrote:
I did start on making the tool table a lot cleverer. It would be a
database (which means that you can actually add any data fields you
like for your own purposes, LinuxCNC will just ignore things it
doesn't know how to
On Mon, Apr 21, 2014 at 4:32 AM, andy pugh bodge...@gmail.com wrote:
On 21 April 2014 03:30, Kirk Wallace kwall...@wallacecompany.com wrote:
I did start on making the tool table a lot cleverer. It would be a
database (which means that you can actually add any data fields you
like for your
On 21 April 2014 10:10, Mark Wendt wendt.m...@gmail.com wrote:
Ugh. Stay away from SQLite. That's a one-user, build it in your home
directory, terribly slow, resource hog. MySQL or PostgreSQL are much
better databases. You can optimize them much easier and better,
It's a tool table. Just
Chris Radek chris@... writes:
Upgraded, started, works perfect!
THX guys
Mike
Many thanks to the people who have reported bugs, and
especially to
the folks who worked to improve LinuxCNC for this release:
Alex Joni
Andy Pugh
Ben Jackson
Chris Morley
Chris Radek
Chris S Morley
On Mon, Apr 21, 2014 at 5:37 AM, andy pugh bodge...@gmail.com wrote:
On 21 April 2014 10:10, Mark Wendt wendt.m...@gmail.com wrote:
Ugh. Stay away from SQLite. That's a one-user, build it in your home
directory, terribly slow, resource hog. MySQL or PostgreSQL are much
better
On 21 April 2014 10:43, Mark Wendt wendt.m...@gmail.com wrote:
It's a tool table. Just how big and busy do you anticipate it getting?
It depends. For somebody like me, not very big, but for somebody like
Stuart, I imagine it might grow a bit.
I imagine even MPM only have hundreds of tools
On Mon, Apr 21, 2014 at 5:52 AM, andy pugh bodge...@gmail.com wrote:
On 21 April 2014 10:43, Mark Wendt wendt.m...@gmail.com wrote:
It's a tool table. Just how big and busy do you anticipate it getting?
It depends. For somebody like me, not very big, but for somebody like
Stuart, I
Whats wrong with a file based tool table. It is easier for the layman to
maintain offline as well.
On 2014-04-21 11:37, andy pugh wrote:
On 21 April 2014 10:10, Mark Wendt wendt.m...@gmail.com wrote:
Ugh. Stay away from SQLite. That's a one-user, build it in your home
directory, terribly
On 21 April 2014 11:33, Marius Liebenberg mar...@mastercut.co.za wrote:
Whats wrong with a file based tool table. It is easier for the layman to
maintain offline as well.
A simple flat file has to make assumptions about what data can be
stored. Specifically it would have to make assumptions
I understand now. I have to agree with you that the SQlite option will
be the least resource intensive thing to use.
I used to use a file based RDBS a long time ago that was very easy to
implement with a very small footprint, but I cannot seem to find any
reference to it anywhere.
On
Andy
Have a look at this work. Maybe a good solution.
https://github.com/bitsnbytes7c8/MegatronDB
On 2014-04-21 17:37, andy pugh wrote:
On 21 April 2014 11:33, Marius Liebenberg mar...@mastercut.co.za wrote:
Whats wrong with a file based tool table. It is easier for the layman to
maintain
On 21 April 2014 18:47, Marius Liebenberg mar...@mastercut.co.za wrote:
Andy
Have a look at this work. Maybe a good solution.
https://github.com/bitsnbytes7c8/MegatronDB
Possibly.
The real work is in working out everywhere that tool data is used, and
when changes get committed back to the DB.
Well, a google search on open source cam software turns
up a few items:
openscam: appears to be a g-code simulator and not a CAM package at all
blendercam: plug-in for Blender.
HeeksCNC: looks promising, imports dxf and step files.
makercam: online app
pycam: python scripts, uses dxf, svg,
13 matches
Mail list logo
