Re: [Kicad-developers] Code execution context

2021-03-02 Thread Seth Hillbrand
ease contact us at > priv...@3dconnexion.com. > -Original Message- > From: Kicad-developers 3dconnexion@lists.launchpad.net> On Behalf Of Wayne Stambaugh > Sent: Thursday, February 25, 2021 6:06 PM > To: kicad-developers@lists.launchpad.net > Subject: Re: [Kicad-deve

Re: [Kicad-developers] Code execution context

2021-03-01 Thread Markus Bonk
regards to personal data, please contact us at priv...@3dconnexion.com. -Original Message- From: Kicad-developers On Behalf Of Wayne Stambaugh Sent: Thursday, February 25, 2021 6:06 PM To: kicad-developers@lists.launchpad.net Subject: Re: [Kicad-developers] Code execution context

Re: [Kicad-developers] Code execution context

2021-02-26 Thread Markus Bonk
Mark Roszko Sent: Thursday, February 25, 2021 3:38 PM To: Jon Evans Cc: Markus Bonk ; kicad-developers@lists.launchpad.net Subject: Re: [Kicad-developers] Code execution context On another note, I personally am not a fan of websockets usage locally on Windows. In corporate environments there'

Re: [Kicad-developers] Code execution context

2021-02-25 Thread Mark Roszko
>We just cannot ship those libraries. Why not? It's hardly a problem if the library allows redistribution in their licensing and it's extremely commonplace in Windows land to redistribute dependencies in the installer. On Thu, Feb 25, 2021 at 12:06 PM Wayne Stambaugh wrote: > Any code contribut

Re: [Kicad-developers] Code execution context

2021-02-25 Thread Clemens Koller
Hello, Markus! I can offer to do some testing / debugging on Arch Linux. (I'm currently on boost 1.75.0, but I hope it is not needed as dependency.) I cannot help with proprietary / closed source drivers. My SpaceNav was sleeping in my drawer for ages, so the rubber parts became sticky as chewi

Re: [Kicad-developers] Code execution context

2021-02-25 Thread Wayne Stambaugh
Any code contributed to KiCad would have to be release under the GPL3+ or compatible license to be accepted. Linking to proprietary drivers is not an issue since we already link to Windows and MacOS proprietrary libraries in order to provide KiCad on those platforms. We just cannot ship those lib

Re: [Kicad-developers] Code execution context

2021-02-25 Thread Kevin Cozens
On 2021-02-25 1:47 a.m., Markus Bonk wrote: I am currently investigating adding support for 3D input devices to pcbnew. One other piece of information I forgot to include is that for development under Linux you can use the libspnav0(-dev) libraries. The description for the library is: The s

Re: [Kicad-developers] Code execution context

2021-02-25 Thread Kevin Cozens
On 2021-02-25 1:47 a.m., Markus Bonk wrote: I am currently investigating adding support for 3D input devices to pcbnew. The plan is to use a websocket interface I've long wanted to be able to use my 3DConnexion device when I'm in the 3D view of pcbnew. I thought about trying to implement it bu

Re: [Kicad-developers] Code execution context

2021-02-25 Thread Jon Evans
As long as the experience is the same on all platforms (Win, Mac, Linux) and KiCad does not require any proprietary libraries to compile, I think it is up to Wayne whether or not an optional dependency on a proprietary library on Windows is acceptable. But, I would like to hear from Markus on the

Re: [Kicad-developers] Code execution context

2021-02-25 Thread Mark Roszko
On another note, I personally am not a fan of websockets usage locally on Windows. In corporate environments there's going to be hell with security software interfering and in general it's fragile. I personally would rather just link against the 3dconnexion library directly. We have the MSVC build

Re: [Kicad-developers] Code execution context

2021-02-25 Thread Jon Evans
That is a good point Mark, we could either have this behind a flag so that it only gets enabled/compiled with new-enough Boost versions, or investigate a different websockets library. I'm not sure the overlap of 3dconnexion users and 18.04 users is large enough to rule that approach out, at least

Re: [Kicad-developers] Code execution context

2021-02-25 Thread Mark Roszko
* Boost 1.65 being the version Ubuntu 18.04 LTS currently has and are committed to support until EOL. On Thu, Feb 25, 2021 at 9:19 AM Mark Roszko wrote: > Markus, > > We currently require support for a minimum of boost 1.59 due to Linux > distros lagging behind. boost/beast is not a viable optio

Re: [Kicad-developers] Code execution context

2021-02-25 Thread Mark Roszko
Markus, We currently require support for a minimum of boost 1.59 due to Linux distros lagging behind. boost/beast is not a viable option as beast did not appear in boost until 1.66. >From some offhand sounding out we may be able to bump the minimum to 1.65 but that doesn't help :/ Regards, Mark

Re: [Kicad-developers] Code execution context

2021-02-25 Thread Jon Evans
Hello Markus, This is exciting news, as some of our users are also big fans of 3dconnexion products[1] Others have looked in to what it would take in the past, but there were some questions about the need for proprietary drivers on some platforms[2] It sounds like this websocket interface is a n

[Kicad-developers] Code execution context

2021-02-24 Thread Markus Bonk
Hi, I am currently investigating adding support for 3D input devices to pcbnew. The plan is to use a websocket interface (boost/beast) to communicate with the 3D device. Effectively the communication runs on an extra thread. Somewhere the event code will need to switch to executing on the main