With all this talk about new versions and GUI, it would be nice to introduce some patterns to address separation of concerns and ease GUI creation in a common way.
-Brad Murry ________________________________ From: Michael Haberler Sent: 8/25/2012 9:32 PM To: EMC developers Subject: Re: [Emc-developers] RFC: cleaning up linuxcnc.in to support HAL+GladeVCP only configs (and then some) Am 26.08.2012 um 01:11 schrieb Chris Morley: > > >> 3. ALL guis, not just Axis, need to eventually learn how to start a >> POSTGUI_HALFILE if there is any chance itself or a subprocess creates >> additional HAL objects. To do so, they need to understand that they are the >> primary UI component. This suggests a per-ui command line flag like >> '--primary-ui'. > > > AXIS, TOUCHY and The future Gscreen all understand POST_GUI. > TOUCHY requires a touchy.hal file though. > It would be nice if linuxcncTK could be retrofitted with POSTGUI and at least > PYVCP panels. > but TCL is not my bag.... I think by now the whole POSTGUI_HALFILE thing was a kludge. The linuxcnc.in assumption is: shutdown happens when the UI program exits, so just block on the UI program, and run cleanup thereafter. It would be much easier and uniform if: 1. linuxcnc.in just starts the UI in the background and records its pid 2. linuxcnc.in waits for the UI to be fully set up (all HAL comps/pins created and ready) 3. linuxcnc.in runs any POSTGUI type jobs. 4. when done, it explicitly waits for the UI pid. 1,3,4: easy 2: I'm taking suggestions - one cant tell in advance which halcomps are set up behind the UI, so you cant test for them being ready easily; also halcmd is less than helpful wrt exit status: say 'halcmd show comp axis' always reports exit status 0 even if comp axis doesnt exist. Maybe somebody has a simple idea in his bag of shell tricks how a process can notify the parent shell that some step is complete. - Michael > > One thing that happens is if you try to load two guis in the same config (not > often to happen, > but sometimes when testing) is that both guis try to load the POSTGUI file > and of course the > last one fails due to the pins/signals already being present. Not sure if > that is a real deal breaker... > > It would be a good idea is we added a section in the developers manual about > the common > requirements of a 'full featured' gui screen eg reparenting, POSTGUI etc. > easier to follow the standard then fix the code after the fact... > > my 2 cents :) > Chris M > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
