Along the same lines: What sort of suggestions does everybody have for organizing/commenting HAL and INI files.
Mine are starting to get a little hard to read. I'm big on coding standards in general, as a big part of them is about code readability. Is there a method any of you use to do the same? N. Christopher Perry On Apr 16, 2013, at 19:23, Gene Heskett <ghesk...@wdtv.com> wrote: > On Tuesday 16 April 2013 19:05:57 andy pugh did opine: > >> On 16 April 2013 10:49, propcoder <marius.alks...@gmail.com> wrote: >>> electronics (power, drivers, custom electronics with documentation and >>> all datasheets, cabling, signals, computer,..) >> >> I don't do anything for anyone other than myself, but I would be lost >> without the wiring details. (and it really needs to be down to the >> level of pin numbers in every connector, and the wire colours between >> them) >> >> It would be nice to be able to generate a nice HAL diagram, and there >> have been various ways to do that suggested, but I am not sure any >> have been shown to work properly. > > There was a thingy that I assume worked, I installed it last fall, but it > had one fatal flaw. It tried to make the whole diagram fit on a single > sheet of paper, when, in order to have been able to read it with a > magnifying glass, it would have had to be done in multi-page poster style > that would have likely used 54 to 100+ sheets of paper to be taped together > before the text in one of the teeny little logic boxes would have been big > enough to read. > > It could have been quite valuable as a troubleshooting tool had it rendered > to a pdf that we could then have grabbed the sliders to move the screen > view to anyplace in it. I tried to blow it up myself, but it rendered in > postscripts default 72 dpi, so it wasn't readable at any scale for the > diagram generated for my lathes, .hal files. > > I looked at the code to see if I could figure out how to fix it, but I > wasn't familiar enough with the language to understand it, let alone > troubleshoot it. > > Today, I don't even recall the name of it. Sorry. The mailing list > archive for last fall might contain a reference, as it is this list that > made me aware of it in the first place. > > Looking on the lathes box, I find a ~/gene/src/RockHopper directory that > looks like one of those usual suspects, was that it? > > Cheers, Gene > -- > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > My web page: <http://coyoteden.dyndns-free.com:85/gene> is up! > My views > <http://www.armchairpatriot.com/What%20Has%20America%20Become.shtml> > BOFH excuse #319: > > Your computer hasn't been returning all the bits it gets from the Internet. > A pen in the hand of this president is far more > dangerous than a gun in the hands of 200 million > law-abiding citizens. > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
