On Saturday 02 May 2020 04:46:52 Phill Carter wrote: > > On 2 May 2020, at 5:32 pm, Reinhard <reinha...@schwarzrot-design.de> > > wrote: > > > > On Samstag, 2. Mai 2020, 08:22:05 CEST Jared McLaughlin wrote: > >> In my opinion, linuxcnc should be more like a distro that > >> you install packages on. The UI's should be packages that are not > >> maintained by the main development team. > > > > That makes sense > > I really don't see a problem with having the UI's as part of LinuxCNC > > >> I also agree with the idea that a cleaned up "new version" should > >> be considered for the next major release. > > > > Would be nice! > > > >> I have used PathPilot and it seems a lot better than the other > >> LinuxCNC UI's I poked at before. That said, I feel like even > >> PathPilot has a long way to go ... > > > > Well, I'm the creator of JCNCScreen. > > > > The reason, why I started with such a big time-consuming work was, > > that none of the existing UIs was really usable for me (including > > PathPilot and others). > > > > I'm bit outdated, so I can't read axis and the like, that don't > > respect proposals of window manager (i.e. like fontsize). Even on my > > desktop pc I need glasses and put my nose onto the screen to be able > > to read axis … > > It is relatively easy to change the font size in Axis. > > > For me, it is important, that I'm able to recognize the most > > important states of the machine at a glance. Even from a distance of > > about 4-5 meters. None of the UI offers this. Most if not all are > > too noisy - and you need several seconds to find out, what is > > relevant and what is just high-polishing for non-machinists - and > > even then: not every important state is visible. Of cause, that does > > not mean, that I want to read gcode from that distance, but > > important machine states should be recognizable. > > Kind of a catch 22, the more states displayed the noisier it becomes. > > > Another problem is, that neither pyqt, nor gscreen runs on my > > desktop box. I don't know enuf of python to solve that problems on > > my own and it does not help, if others state, that they don't have > > problems. > > So I started with java, where I know to solve my own problems. > > Startup may be too slow, but response time of the running app is > > fast enuf for anything. > > I imagine I would have the same issues with a Java UI if it didn't > run. > > > I don't really need my own UI - if another UI would offer, what I'm > > looking for, it would be just fine. > > I don't think there will ever be a GUI that suits more than a few. > This is true. I still use axis although I have looked at some of the others, its seems like I always come back to axis, primarily because with pyvcp, I can bend it to do what I want. No two of my axis setups look alike. But I also get the impression that some of whats currently available no longer have a support person to answer setup questions, and those s/b reduced to honerable mentions.
My biggest squawk about our gui's in general is the microscopic halmeter. It needs about a 4x magnification so it can be read from 3 meters away on a 22" screen when troubleshooting a home switch or whatever its set to watch. > Cheers, Phill > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene> _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
