"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 designer, I was looking for a different option than existing 2018 gui's that didn't exist and ran across the BrendaEM thread. I began contributing to it but it seemed stifled and uncertain if that designer would continue moving forward so I looked for the next way to achieve the goal of a new UI. When I saw a functioning control panel video in one of the posts I said ok there is a way forward to make an updated gui a reality. So for me it was the first one that I found with something actually functioning which was QtPyVCP. I spent the next 4 and half years working on that platform. 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 paced and innovative team mentality group I have had the pleasure of working with to date. It is driven by some extremely talented developers genuinely excited about the creative process. I think a designer would be able to choose which they would want to work in and at this point they are different enough that it is relevant. The fact that their exists several very well received usable gui's in both is also a strong reason. By excluding one it is essentially short changing user choices. So the bigger question is why would anyone want to do that? On Thu, Dec 1, 2022 at 3:12 PM andy pugh <bodge...@gmail.com> wrote: > On Wed, 30 Nov 2022 at 23:31, Steffen Moeller <steffen_moel...@gmx.de> > 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 and vice versa. Both GUIs > > should be as easy to install and use as possible. > > > We already see users getting confused about whether they are using PyVCP > (hand-coded XML input files) > https://linuxcnc.org/docs/stable/html/gui/pyvcp.html > Or GladeVCP (more capable, more widgets, has Python handlers. designed > using a GUI (which is horrible, unintiutive and crashes a lot) > https://linuxcnc.org/docs/stable/html/gui/gladevcp.html > > How are integrators (ie, GUI / Panel designers) meant to pick between QtVCP > and the very similarly named QtPyVCP? They do the same thing, > fundamentally. > > -- > atp > "A motorcycle is a bicycle with a pandemonium attachment and is designed > for the especial use of mechanical geniuses, daredevils and lunatics." > — George Fitch, Atlanta Constitution Newspaper, 1912 > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
