I'm merging 2.8 into 2.9, and I came across a spot where it looks like a
feature was added independently to both 2.8 and 2.9 (7i96s support in
pncconf), and a bunch of bugfixes were applied in 2.9 but not 2.8.
Please remember folks: apply patches to the oldest branch where it
belongs, then
Agreed!
Not everyone likes QtPyVCP, Qt, Tk, Gtk.. and users should have the freedom
to install the interface they want and not have to have the ones they don't
need.
But this would be an immense undertaking to make possible.
Cheers!
Kurt
On Thu, Dec 1, 2022 at 12:44 AM Johannes P Fassotte <
Good evening!
I have been busy starting a family so have been completely out of the
LinuxCNC loop lately,
glad to see most of the old familiar names still active, as well as the new
ones!
I have not thoroughly read this thread, but I have read enough to be
discouraged
by some of the things said.
Le jeu. 1 déc. 2022 à 20:26, Sebastian Kuzminsky a écrit :
> On 11/30/22 22:24, Johannes P Fassotte wrote:
> > It was not to may years ago that LinuxCnc was just over 120Mb in
> > extracted size. Now V 2.9 master is takes up 252Mb so its getting
> > bloaded with a lot of none essential things.
Le jeu. 1 déc. 2022 à 22:47, Small Shop Concepts a
écrit :
>
> The collaboration there is fantastic and the general positive can-do
> attitude helped to push things along. If something is dreamt up it is
> tried and tested and if it works it is implemented. It has been by far the
> most fast
Le jeu. 1 déc. 2022 à 20:36, Small Shop Concepts a
écrit :
>
> I was under the impression we were collaborators not competitors?
>
I really hope we are mate, I really hope...
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
Le jeu. 1 déc. 2022 à 19:42, Chris Morley a
écrit :
> Because qtpyvcp and qtvcp do the same job using mostly the same tools
> (python and qt)
>
> If qtpyvcp wanted to be under the linuxcnc unberella they could have
> continued working in qtvcp instead of making a new independent, project.
"How are integrators (ie, GUI / Panel designers) meant to pick between QtVCP
and the very similarly named QtPyVCP? They do the same thing,
fundamentally."
Does that even matter at the user level for gui selection?
I am not privy to why the two were divided and frankly could care less as a
Le jeu. 1 déc. 2022 à 17:19, andy pugh a écrit :
> On Thu, 1 Dec 2022 at 16:06, Jérémie Tarot wrote:
>
> Absolutely ! I already told JT and said here that MesaCT repository surely
> > deserves to join the LinuxCNC organization
> >
>
> Then new users are _really_ going to need a flowchart to
Have implemented a manual tool change component.
To release tool hydraulic pump is started and stopped. To clamp tool
hydraulic pressure have to be released. There is also two digital
inputs from sensors that will tell if open or closed.
There is buttons to unlock tool, clamp tool and tell then
> Gesendet: Donnerstag, 01. Dezember 2022 um 21:07 Uhr
> Von: "andy pugh"
> An: "EMC developers"
> Betreff: Re: [Emc-developers] Eye candy is important - Titan got a new German
> friend - want that reaction for a LinuxCNC controller
>
> On Wed, 30 Nov 2022 at 23:31, Steffen Moeller
> wrote:
On Wed, 30 Nov 2022 at 23:31, Steffen Moeller
wrote:
I consider all our users to be somehow part of our project and am
> agnostic about the interface they are using. From how I see it, if
> PyQtVCP does something better than QtVCP then QtVCP gets some
> encouragement and ideas on how to improve
" I consider all our users to be somehow part of our project and am
agnostic about the interface they are using. From how I see it, if
PyQtVCP does something better than QtVCP then QtVCP gets some
encouragement and ideas on how to improve and vice versa. Both
GUIsshould be as easy to install and
I am not sure how that would be perceived as trampling on Qtvcp and
that sounds like a very personal reason for exclusion of QtPyVCP UI's.
I think that mentality is crippling to Linuxcnc's future and growth.
I was under the impression we were collaborators not competitors?
On Thu, Dec 1, 2022 at
On 11/30/22 22:24, Johannes P Fassotte wrote:
It was not to may years ago that LinuxCnc was just over 120Mb in
extracted size. Now V 2.9 master is takes up 252Mb so its getting
bloaded with a lot of none essential things. I think it needs a good
cleaning to get it back on track. I feel that
I would agree that development tools in Linuxcnc is not ideal, I think
also in many cases it can bring a level of confusion to new users. I
also think that it should be weighed and a solution found to bring
those UI's that users would want to use into an easy to install
situation that did not
Because qtpyvcp and qtvcp do the same job using mostly the same tools (python
and qt)
If qtpyvcp wanted to be under the linuxcnc unberella they could have continued
working in qtvcp instead of making a new independent, project. Nothing wrong
with being independent, seems to work for both
On Thu, 1 Dec 2022 at 16:42, Jon Elson wrote:
> Thanks for any insight, I don't use this feature at the moment.
>
It seems to work fine in a simulator (sim/axis_mm) without anything
connected to hal_manualtoolchange.change_button.
Perhaps he has an odd graphics setup or skin that is making the
On 11/21/22 19:35, Jon Elson wrote:
I have a user who tried to implement the manual tool change
button in LinuxCNC 2.8, he says there is no continue button
displayed.
His original code was :
loadusr-W hal_manualtoolchange
net tool-change iocontrol.0.tool-change =>
On Thu, 1 Dec 2022 at 16:16, Chad Woitas
wrote:
>
> Sounds to me like a package manager is what ya'll are looking for.
> Download Base Linuxcnc, and add in the UI's and interfaces afterwards.
Splitting the LinuxCNC package into sub-packages is probably more work than
anyone has the appetite
On Thu, 1 Dec 2022 at 16:06, Jérémie Tarot wrote:
Absolutely ! I already told JT and said here that MesaCT repository surely
> deserves to join the LinuxCNC organization
>
Then new users are _really_ going to need a flowchart to get them going.
Are you using a Mesa card?
Which one?
In that
Sounds to me like a package manager is what ya'll are looking for. Download
Base Linuxcnc, and add in the UI's and interfaces afterwards.
-Chad
From: Small Shop Concepts
Sent: December 1, 2022 9:43 AM
To: EMC developers
Subject: Re: [Emc-developers] Eye candy
Le jeu. 1 déc. 2022 à 16:47, Small Shop Concepts a
écrit :
> I think it would be great if QtPyVCP were included in Linuxcnc. I'm not
> sure how you mean it would undermine qtvcp? Isn't Linuxcnc stronger with
> more options for users?
Further, IIRC @cmorley, you're our UI API uniformization
Le jeu. 1 déc. 2022 à 11:06, Phill a écrit :
>
> Actually on second thought some users would use QtVCP, for example
> embedding CamView into an Axis or Gmoccapy tab.
Then, they're not just users anymore !
A CNC _user_ starts the machine, makes chips, stops the machine...
sometimes have a cold
I think it would be great if QtPyVCP were included in Linuxcnc. I'm not
sure how you mean it would undermine qtvcp? Isn't Linuxcnc stronger with
more options for users? As the developer of Probe Basic and speaking on
behalf of the thousands of Probe Basic users out there I am sure they would
also
On 12/1/22 04:25, Jérémie Tarot wrote:
Le jeu. 1 déc. 2022 à 01:32, Phill Carter a
écrit :
Neither QtVCP nor QtPyVCP are GUIs, they are infrastructure for creating
GUIS.
I would think that most users will use neither, they will just use the
GUIs that have been developed.
Absolutely !
This
On 12/1/22 04:04, Nicklas SB Karlsson wrote:
...
As far as tools for building user interfaces It would also not
surprise
me if the next fad for building those is just around the corner and
that
QT will hopefully be just part of the old LinuxCnc history. I there
will always be newer and better
Original message From: Jérémie Tarot
Date: 1/12/22 8:28 pm (GMT+10:00) To: EMC developers
Subject: Re: [Emc-developers] Eye candy
is important - Titan got a new German friend - want that reaction for a
LinuxCNC controller Le jeu. 1 déc. 2022 à 01:32, Phill Carter
aécrit
Le mar. 29 nov. 2022 à 23:27, Feral Engineer a
écrit :
> There's that one interface that's a blatant rip off of a siemens control
> that would be a great addition
>
... and, according to his last messages, he's at least planning to bring
much more than just the UI !
I really hope this guy
Le jeu. 1 déc. 2022 à 01:32, Phill Carter a
écrit :
> Neither QtVCP nor QtPyVCP are GUIs, they are infrastructure for creating
> GUIS.
> I would think that most users will use neither, they will just use the
> GUIs that have been developed.
Absolutely !
This is why I think that all *VCP and UI
> ...
> As far as tools for building user interfaces It would also not
> surprise
> me if the next fad for building those is just around the corner and
> that
> QT will hopefully be just part of the old LinuxCnc history. I there
> will always be newer and better ways to get things done without
Le jeu. 1 déc. 2022 à 00:31, Steffen Moeller a
écrit :
>
> Am 30.11.2022 um 19:12 schrieb Chris Morley:
> > The difference is free cad doesn't compete with anything in linuxcnc.
> Qtpycp does. If they wanted to be included in linuxcnc, then they would
> have been part of the project. They made a
hahaha was that rhetorical or suppository? :-/
tomp
On 11/30/22 04:27, Alec Ari via Emc-developers wrote:
Subject
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
33 matches
Mail list logo
