Hi,
I have been following this with greate interest too. Today I use the U, V and W axis to store parameters for tool measuring, and I would like to do somthing better. I have not developed in linux but I develop in Windows environment an I like XML. XML is human readable and can be edited with a text editor. I made a quick serach and fond an xml-based database.http://basex.org/ That might be one alternative too. --Per Eklund ________________________________ From: EBo <e...@sandien.com> Sent: Wednesday, October 26, 2016 3:28:35 PM To: emc-developers@lists.sourceforge.net Subject: Re: [Emc-developers] Tool Number limit I am glad you and Andy will develop and maintain this. As I said before, I will not have time to help with this and will accept anything which is provided. On Oct 26 2016 7:08 AM, dragon wrote: > For what it is worth, I am with Andy on this. An actual DB, even > something simple like SQLite, opens up many additional possibilities > while helping to prevent breaking a custom parser. > > As he mentioned... this would allow other custom applications written > in > almost any language to interact with the tool table data. It also > allows > one to expand the schema and store extra tool information that the > mainline LinuxCNC applications might not need but without breaking > them. > > > > On 10/26/2016 07:53 AM, andy pugh wrote: >> On 26 October 2016 at 13:26, TJoseph Powderly <tjt...@gmail.com> >> wrote: >>> >>> so >>> why not just associate an tool with an index into a technology? >> >> This has to be part of any solution,because all that G-code knows >> how >> to do is to pass out a single integer, the T-number. >> From that point it is down to "something else" to deal with that >> number, and currently that is all encoded in iocontrol. [1] >> >>> and the tech stored in simple ascii flat files. >> >> This is where we differ, I think. If we are going to expect system >> integrators to write custom ways to interpret the T-number then I >> think it is actually likely to be easier to have that encoded as a >> database query than to write a custom flat-file parser. >> Also, you can add your own metadata into a database and a query will >> still work with whatever default query LinuxCNC is supplied with. If >> you add members to a flat-file (or set of several flat files) then I >> think you will break the parser. >> >> [1] The proposed tool-table changes will almost certainly kill >> iocontrol, as then that will only be concerned with coolant and lube >> outputs >> > > > > ------------------------------------------------------------------------------ > The Command Line: Reinvented for Modern Developers > Did the resurgence of CLI tooling catch you by surprise? > Reconnect with the command line and become more productive. > Learn the new .NET and ASP.NET CLI. Get your free copy! > http://sdm.link/telerik > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
