On Wednesday 28 November 2018 12:15:25 Jon Elson wrote:
> On 11/28/2018 07:23 AM, Jeff Epler wrote:
> > .. which is likely, in turn, to affect LinuxCNC. Those
> > interested
> > should look at modernizing the parts of LinuxCNC that
> > still use gtk2.
> >
> > I know this still includes halscope
On 11/28/2018 07:23 AM, Jeff Epler wrote:
.. which is likely, in turn, to affect LinuxCNC. Those
interested
should look at modernizing the parts of LinuxCNC that
still use gtk2.
I know this still includes halscope and halmeter. it
would be a real
pity to lose halscope to CADTs^Wthe
On Wednesday 28 November 2018 08:23:52 Jeff Epler wrote:
> .. which is likely, in turn, to affect LinuxCNC. Those interested
> should look at modernizing the parts of LinuxCNC that still use gtk2.
>
> I know this still includes halscope and halmeter. it would be a real
> pity to lose halscope
On Wed, 28 Nov 2018 at 13:25, Jeff Epler wrote:
> .. which is likely, in turn, to affect LinuxCNC. Those interested
> should look at modernizing the parts of LinuxCNC that still use gtk2.
>
The absolute lack of support on the pygtk mailing lists and IRC make me not
so upset with the idea of
.. which is likely, in turn, to affect LinuxCNC. Those interested
should look at modernizing the parts of LinuxCNC that still use gtk2.
I know this still includes halscope and halmeter. it would be a real
pity to lose halscope to CADTs^Wthe progress of the Linux desktop.
- Forwarded
