OK. So we went from "change nothing" to doing something which is not only necessary for a few, but also darn right practical. No, this all sounds good. I was not aware of the 59 item limit. 256 (8-bit int) or 64K (16-bit int) seems more reasonable. For James example I would lean towards a 16-bit tool number. It is also possible that some of the bits could be used for status indication and we actually end up with something like 12-bits of tool numbers and 4 bits for status.
If we need a full on relational database, then fine, but I simply not seeing it. I understand Sarah's desire to have something easily portable to what she is currently using. But if we are simply linking tables and not doing sophisticated queries and joins and ..., then requiring maintenance of a full SQL database is adding to the complexity of the toolchain overmuch. I would offer that we should accommodate export tools to save in MSQL, Postgress, etc. So I will ask my question again "what is the most maintainable long term solution?" All that said, I doubt that I will have time to help on this one and will simply use whatever the developers come up with. That said, I see this as a maintenance nightmare. On Oct 26 2016 2:31 AM, James Waples wrote: > Machines with more than 56 tools are becoming a lot more common so > removing > this arbitrary limit would be quite important to a lot of people. > From a > personal standpoint, I would like to be able to group my tools by > number > (0-99 for endmills, 100-199 for drills, etc). I tried this once > before but > was surprised by an error when I tried adding tool T100. Sounds like > there's some technical debt that would be good to clean up. > > On Tue, 25 Oct 2016 at 21:35 EBo <e...@sandien.com> wrote: > >> On Oct 25 2016 9:03 AM, andy pugh wrote: >> > On 25 October 2016 at 15:25, EBo <e...@sandien.com> wrote: >> >> That said, what is the most maintainable long term >> >> solution? >> > >> > Change nothing.... >> >> Then why did the subject come up in the first place? Isn't there >> bugs >> that is causing issues and problems are arising? >> >> EBo -- >> >> >> >> >> ------------------------------------------------------------------------------ >> 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
