On 3 Feb 2009 at 6:37, Chris Morley wrote:
> > Greetings. > > I see that the pyvcp example that uses halui in stepconf (of > trunk) > was deleted. I knew that would get your hair to stand on end! I'm not sure if jepler is always like that or something else in his life is bothering him. He bit my head off the other day for a simple mistake... I commited something and cradek reversed it, I thought I forgot to commit when I could not find it a day or two later and committed it again... not catching that cradek had reversed it. It was over nothing really just changing the splash code so it would not break when you used a stock config or if you left the X0 and Y0 as the start of the machine limits... Funny how when I mentioned that he had changed the axis.ngc himself 2 1/2 years ago to move the X over .5 he change his tune just a little. Alex finally moved the Y over .5 yesterday then I added a few words to give a newbee a hint how to run it. My point is it should work "out of the box" if you accecpt all the defaults it should at least run on your screen... > While I could understand wanting some things possibly changed > for technical / usability reasons I don't understand why one would > completely > remove an example. > For instance if having buttons that set clear G92 would cause > confusion with > the display in Axis of course that should be changed. > But the separate jog buttons did no harm that I could see and I have > heard of > people asking for separate jog buttons for each axis. > A working example of 'something' is a good reference point for doing > 'something else'. > They are completely optional and by default not included. > They are meant as examples of using pyvcp/halui not for specifically > to add features to a GUI. > Believe it or not people use stepconf to do more then just setup a > simple machine. > I changed the XYZ example twice trying to make people happy and > asked for acceptable > examples. If it was just going to be erased with no chance for > improvement > then I wish I knew that in beginning as I would not have put as much > time into it. > > I might add that the choice of wording "are forbidden" of the commit > message seemed designed > to > start a pissing match. The only problem when you start pissing is it never leads to any good. I really don't think he thought any at all when he added the commit message... The best thing is to ignore it. For a chuckle look in the pyVCP Examples section of the Integrators manual in the Jog Button example. I'm not going to change the image! > > Beyond all that I am thankful for the help/direction received when > building the page. > I am happy the advanced page is being included and think it will be > well received > by users. (or else we will have to change/ remove it in 2.4 :) ) > > Chris M I think the Advanced page adds significant capability to the step conf wizard and will be the hit with the newbees. In a couple of mouse clicks you can have a pyVCP to work with or a ClassicLadder started that might have taken a newbee weeks to figure out. The main developers are so in tune to the code they forget what it is like to not know anything and everything is brand new to you. When I first got EMC up and running I tried to RTFM and it was so confusing to me that I almost lost interest in EMC. The HAL tutorial is/was a nightmare and had errors in it. I gained nothing from it. Thanks for taking that task on. And have a fun day :) John ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
