>
> Hi. sorry, couldn't resist my five cents as not-developer but long time
> industrial player.
>
Either could I :)
> I hate parameters distributed in lots of " you just have to know them files".
>
> One "collecting" place like the ini of lcnc is what i love and use extensive.
>
I like it too other then I don't like referencing the INI from the HAL file.
When I read the HAL I find it much easier, though it's not the end of the world.
Our calibration GUI requires the INI substitution in the HAL file, and that is a
handy program, so I do see the advantages.
More importantly is making sure our docs and config examples jive and that the
user understand that reworld HAL and INI files can differ especially wizard
derived.
it's probably time to re-evaluate standard names used in the INI file.
use of INPUT and ENCODER_INPUT for the same thing depending who made it, is
confusing.
Another one is the hundred different VELOCITY entries. some for the GUI some for
linuxcnc and HAL ..
some guide line for GUI entries would be a good idea. The docs in general assume
AXIS but that is changing and each GUI adds different INI entries. Some are
moving
from INI entries to GUI selection. Some standards with an eye to the future
would
help here I think.
I hack on PNCconf so the subtle and not so subtle differences to do the same
thing
is a PITA for me, so must be a huge mountain to climb for a newcomer.
>
> I think it's transparenter to have one single ini per config. My expierence
> is
> that after some month you forget which other configs might be in danger if
> you
> change a "guarantied stable in cases all" configfile.
>
> I know, I'm old fashioned, but lost to many manhours in tree structured
> configurations.
>
> Mike
It's sure nice to be user readable too.
> I LIKE the machinekit aproach... Following all of you guys very exited.
>
It's exciting times - there is tons going on all over linuxcnc!
I hope it comes together soon, it's a little scattered.
And I really would like to grab some more users / developers from the rest of
the world.
This is a great project.
Chris M
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
