On Thu, 2012-02-09 at 11:36 -0600, Jon Elson wrote: ... snip > Yes, if the docs don't adequately describe how this system of putting > settings in the > .ini file and then having HAL code in a HAL file that reads them and > makes the > settings to the HAL component, then it does need to be put into the docs. > It should at least be documented one place, and any HAL component doc > that says the settings come from the .ini file should be corrected. > > Jon
Before wizards, everyone had to write their own custom .ini and .hal files. In writing mine, I noticed that I could put my own sections and keywords in the .ini file and reference them in my .hal file. At the time I was a new user and it didn't occur to me, and it didn't seem to be my place, to see this got documented. Experienced users rely less on the general documentation, so the people who know better, don't tend to notice or fill in the gaps. I have no idea how this could be improved. -- Kirk Wallace http://www.wallacecompany.com/machine_shop/ http://www.wallacecompany.com/E45/index.html California, USA ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
