there are several ways to handle this. (1) When an internal object needs a config file entry it defines the entry along with a validation method. Later the configuration form is created dynamically from all the parameter definitions. ou can embed the parameter definitions right inside the files where they are used.
(2) ROS uses an XML file to define parameters then you could have both the HAL and configuration form generator read the XML. If you don't like XML pick JSON or whatever. Basically a place where parameters are defined. (If a parameter can be used in two places then you need a common place to define them. #1 about won't work.) (3) Parameter servers are another good idea. You include a process who's job it is to manage parameters. It can accept and store both parameter's metadata (type, validation rules and access controls ) as well as the value. Then you might add a GIU so the values could be manly changed. These are much nicer then config files. These can be as simple as just using Berkeley DB. More ways I'm sure but, point is you don't have to give up flexibility for better design. One important goal of getting user input is always to detect errors as soon as it is logically possible to detect them and then of course have some way for the user to correct them right away. The way this happens is the software that is accepting input has to "know" a little bit about what is being input. On Thu, Oct 12, 2017 at 4:40 PM, andy pugh <bodge...@gmail.com> wrote: > > On 13 October 2017 at 00:31, Chris Albertson <albertson.ch...@gmail.com> > wrote: > > > At the very least this could have been implemented with an HTML form > > where clicking on the parameter name brings up a pop-up wit the parameter's > > definition > > > The HAL file can do pretty much the same thing as Simulink does. > Simulink and LabVIEW are the two "graphical" interfaces that most > closely relate to the function of the HAL file, and if you have ever > used them (I have) you would realise that that is just as much > "programming" as editing a text file. > > Chris Morley did try to make PnCConf do exactly what you are > describing, but the complexity inherent in all the different ways that > Mesa cards can be connected together, along with the constant trickle > of new hardware from Mesa made that a Sisyphean task. > > For a simple parallel-port based system Stepconf comes close to what > you describe. Except that you still do need to know what you want to > do. > > -- > 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, 1916 > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Chris Albertson Redondo Beach, California ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
