From: Ray H. <re...@up...> - 2003-12-24 15:14:18
|
Good thoughts. Thanks for bringing my understanding of the underlying config stuff for EMC2 up to date. By using plain text for the base config storage, we can build any kind of configuration systems that we want. We could also make it i18 compliant for those who would prefer a language other than English. I can fit this into my graphical configurator fairly easily so that those who need gui interface for a simple setup can start it and tick new INI, three axis, steppers, old parport, 4 microsteps, 200 steps per rev, direct drive, 20 tpi, standard motion directions, no switches, mini interface, and be done with the task of setting up a Sherline. Ray On Tuesday 23 December 2003 9:15 pm, jmk...@at... wrote: > Robin wrote: > > consider: > > > > 1) I would hope users never have to even see this part of the > > workings unless they wish to delve int the inner workings .. > > it should be able to get up and running with a few clicks on > > a simple config tool .. this is deeper inside than Joe Public > > should ever have to mess with ... > > Since the HAL config is in the form of commands, there is no need > to have everything in one ini file. One file could set up most of > the machine - the stuff that Joe Public neither wants or needs to > touch. Then a much smaller file could set up the final pinouts > and other things that Joe cares about. > > > 2) helping someone out with a text ini is just 'what does it say > > on line xxx with a GUI it becomes, now click on the thing .. just > > .. top right, no down a bit .. looks like a box with some gears > > and a cat, now drag that and ...no, left a little .. > > Agreed. And I would _never_ propose replacing text ini file(s) with > GUI stuff. HAL is configured by a text file, period. BUT, we can > use the schematic capture tool to generate that file, if we wish. > We can also generate it from scratch. No matter how the file is > initially created, we can edit it by hand all we want. > > Using a schematic tool can make things a lot clearer though. Think > about an electronic circuit. If you are trying to understand how > a circuit works, would you rather look at a schematic or a netlist? > The hal config is like a netlist - an exact textual description of > what is connected to what. The schematic shows the same thing, but > in a way that is often easier to understand. HAL "schematics" will > really be more like block diagrams. > > John Kasunich > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for > IBM's Free Linux Tutorials. Learn everything from the bash shell to > sys admin. Click now! > http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Emc-developers mailing list > Emc...@li... > https://lists.sourceforge.net/lists/listinfo/emc-developers |