It'll probably come over as a rant, but to me it feels like imposing a developer to put all his sourcecode inside one file.
Don't get me wrong, I think it's nice to see the effort you're putting in stepconf lately, I'm just worried it gets too configurable which will: a). allow the user to really confuse himself and the config and everything; b). make supporting stepconf users a pain. But before I bring a definite option, I'll try to play with stepconf some more. Regards, Alex ----- Original Message ----- From: Chris Morley To: EMC DEV Sent: Tuesday, January 13, 2009 9:57 AM Subject: [Emc-developers] Opinion on halcmd idea Greetings After doing work with Stepconf I has come to my attention that having multiple hal files can sometimes be messy. I was thinking a hal comand that searches a file for user defined headers with syntax like the INI file, such as: [ FIRST_SECTION ] Then runs all the commands till it reaches the next header. This would allow one to put all Hal commands in one file and call different sections at different times. for instance the POST_GUI.hal file could just have a different header name. And if it makes sense you can still have separate hal files using the regular hal comand. maybe halcmd -f myhalfile.hal [FIRST_SECTION] or halcmd -f myhalfile.hal --FIRST_SECTION Opinions? Chris Morley ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
