Hi Anders I am probably not typical of the "almight board" but I tend to encourage experimentation in most any direction seen to be of value by users/developers. The board tends to fall out on the evolutionary side when it comes to development in this project. As we progress we still need to keep our eyes on the CNC "industry" so that our CNC development is consistent with best practice there. We also need to keep our eyes on the existing architecture that is used by the current system.
This notion of somehow moving feed override down into the HAL raises quite a few concerns for me. As I remember the early HAL discussions it was not intended to do any thing but make hardware connections. Several have imagined a HAL that needs none of the old EMC code in order to make a machine work. NML has the messages needed to scale things like axis and spindle speeds. HAL and halui provide a interface to these systems right now. As halui was being developed, I imagined hardware being connected to these various pins including feedrate and spindle speed. The halvcp code does add to that by offering the ability to develop displays that show and interact with HAL but IMO we must keep in mind the difference between HAL as a hardware connector/operator and EMC's motion control functions and build interfaces appropriate to each. Rayh On Mon, 2007-01-01 at 15:20 +0200, Anders Wallin wrote: > John Prentice wrote: > > (a) There are occasions when the UI benefits from being bi-directional. > > Yes. But I don't know how to program a bidirectional slider or other > widget yet. Maybe someone else can help ? > > > (b) It would a useful generality to be able to display (and as above set) > > parameters (including the proposed global named parameters?) via a vidget. > > indicating and controlling (Labview parlance) HAL parameters should be easy. > > extended functionality could/should be implemented through the Python > 'emc' module, which allows control of almost everything in emc (NML > commands etc.). I guess the 'emc' module is how AXIS interfaces to emc ? > > In the meantime, I have programmed my first ever XML parser which looks > at an XML file and produces a widget layout from it: > http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?PyVCP > > As I am not a professional programmer, and only a Python beginner, the > code is still very rough, but it seems to work somehow. All of the > design decisions probably warrant more thought and re-writing to make > pyvcp really useful. > > would the almighty board of directors please indicate if this > development has a future, or if I should keep it as my private toy ?? > > > > Anders > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers