> From: [email protected]
> To: [email protected]
> Date: Tue, 13 Jan 2009 10:26:03 +0200
> Subject: Re: [Emc-developers] Opinion on halcmd idea
>
> 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.
>
I'll explain more about what I was trying to do with the hal command idea.
I wanted to separate the main hal file from the added options (the pyvcp
panels and ladder hal connections) to make it more obvious what was changed.
I could do that now but would have to call multiple hal files :
1 for the main Stepconf hal connections
2 to add the loadrt modules (abs scale etc)
3 to add the addf calls
4 to add the hal connection that are made after the GUI loads
If I had the other option I could have the main Stepconf hal file,
put all the extra commands in one file and just call the
head section I wanted.
[LOAD_MODULES]
...
[ADD_FUNCTIONS]
...
[CONNECT_HAL]
...
I tell you when I first started looking at sample configuration way back when
It was hard to follow. core_stepper.hal classicladder.hal postgui.hal etc
plus half a dozen other files !
_________________________________________________________________
Drag n’ drop—Get easy photo sharing with Windows Live™ Photos.
http://www.microsoft.com/windows/windowslive/photos.aspx
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
