#emc-devel | Logs for 2009-03-31

[04:59:45] <CIA-2> EMC: 03cmorley 07TRUNK * 10emc2/src/emc/usr_intf/pncconf/ (pncconf.py pncconf.glade): change glade and mesa5i20_prepare function to handle hostmot2 driver- more work needed
[17:46:19] <jcoby> does anyone have any interest in a git mirror of the cvs repo? i'm also thinking of doing nightly builds if anyone thinks that's useful.
[17:48:09] <SWPLinux> thanks for the offer
[17:48:20] <SWPLinux> there's a git repo already, though it's not really used
[17:48:36] <SWPLinux> and we have two systems that automatically build from CVS whenever there's a check-in
[17:49:05] <SWPLinux> if you're thinking of rebuilding packages nightly, that's another thing - it could be a good thing
[17:49:24] <SWPLinux> (but it could also be a support headache ...)
[17:49:47] <jcoby> where is the git repo?
[17:50:06] <jcoby> i haven't used cvs in years and generally have a hard time with it
[17:50:08] <SWPLinux> darned good question. I think jepler and maybe alex_joni have git repos
[17:50:10] <SWPLinux> heh
[17:50:28] <jcoby> yeah i was talking about building the .deb files nightly
[17:50:54] <jcoby> svn and git i use all the time. cvs.. not so much :)
[17:51:12] <SWPLinux> alias svn=cvs
[17:51:13] <SWPLinux> ;)
[17:51:16] <jcoby> ha
[17:51:31] <SWPLinux> we
[17:51:54] <SWPLinux> we've talked about moving from CVS to something else, like svn or git, but I think there are issues with that
[17:52:34] <SWPLinux> not least of which is that we must be absolutely sure (a) that all history is preserved and (b) that tools are available to all developers
[17:52:43] <SWPLinux> and usable, ideally :)
[17:53:11] <jcoby> svn and git both have history import tools
[17:53:56] <SWPLinux> yeah, I think jepler used the git import to create his repo
[17:54:29] <SWPLinux> of course, it might be better to have the repo on something faster than a DSL line if we switch to git/svn, since you get the full history on initial checkout
[17:55:11] <SWPLinux> I think svn is available on the host where linuxcnc.org is, but I'm not sure we have enough control over security and access settings there
[18:10:07] <jepler> there's no way we'd change to svn
[18:10:27] <jepler> I have an import of emc2's history into git, but it's on the slow end of a dsl connection so I don't recommend you clone from it
[18:10:45] <SWPLinux> yeah, not much point in going to svn - if we make a jump I'd like it to be meaningful
[18:11:40] <cradek> and to something better
[18:11:53] <SWPLinux> yeah, that would qualify as meaningful
[18:28:32] <jcoby> jepler: i was thinking of putting it up on github
[18:28:49] <jcoby> (my git clone of the cvs repo)
[18:29:03] <jcoby> fwiw, git is significantly better than svn
[18:29:14] <jcoby> and svn is significantly better than cvs :)
[18:29:27] <jepler> not sure I agree with the second :-P
[18:29:33] <jcoby> hg gets good reviews as well
[18:29:40] <cradek> jcoby: are you hacking on emc2 for a project?
[18:30:06] <jcoby> cradek: just interested. i was thinking about diving into axis and seeing if i could make it look a little better
[18:30:22] <cradek> cvs is a turd so old that it's no longer steaming - can't say the same about svn IMO
[18:30:40] <jcoby> cvs is better than rcs heh
[18:30:51] <cradek> :-)
[18:30:59] <SWPLinux> I just make backup copies before making significant changes :)
[18:31:11] <SWPLinux> who needs all this SCM anyway
[18:31:48] <jcoby> yeah, real programmers use labeled 5.25" floppies to revision code!
[18:32:03] <SWPLinux> floppies?
[18:32:06] <cradek> who needs labels? I just remember.
[18:32:19] <SWPLinux> I use green and white paper printouts, you insensitive clod!
[18:32:23] <jcoby> the blue one is last tuesday. black is wednesday
[18:32:26] <jcoby> greenbar, nice
[18:33:14] <jcoby> i'm mostly a web developer these days but i know python and thought i'd play with axis some. not really interested in hacking on the driver code
[18:33:52] <jcoby> hence the desire to use git to make a branch
[18:38:26] <jepler> I don't see why you wouldn't be allowed to put it up on github. and it sounds like you think it'll help you do what you want to do with emc2.
[18:38:45] <jepler> fwiw, another developer, seb_kuzminsky, has put a bzr import of the history up on launchpad
[18:39:45] <cradek> the AXIS screen stuff is pretty much in two files - to me, doing a VC import sounds like a long way around the block to edit them - but that's just me.
[18:42:32] <jcoby> cradek: yeah i know but the code itself looks like it needs to be broken up
[18:42:45] <jepler> fwiw I just finished putting my import of the cvs on a faster machine, but it's only got dumb http as a transport. It should be automatically updated from now on, though. The clone URL is http://media.unpythonic.net/git-repos/emc2.git
[18:42:46] <jcoby> there is a ton of code in axix.py
[18:43:03] <cradek> that's definitely true
[18:46:50] <jcoby> and it's all undocumented heh
[18:46:58] <SWPLinux> pydoc axis
[18:47:00] <SWPLinux> :)
[18:47:11] <jcoby> one of the guys on the diy-cnc yahoo list thinks it's a conspiracy
[18:47:28] <SWPLinux> to do what, I wonder
[18:47:30] <cradek> what is?
[18:47:39] <jcoby> cradek: the lack of documentation
[18:47:42] <cradek> hahaha
[18:47:51] <jcoby> yeah
[18:48:01] <jepler> oh look, a reminder why I don't read diy-cnc
[18:48:04] <SWPLinux> huh. if I thought a lot of diy-cnc guys could contribute to the code, I'd document it myself
[18:48:08] <jcoby> i didn't feel like arguing with him
[18:48:19] <SWPLinux> (user documentation is among the best for any open source project, I think)
[18:48:24] <cradek> he's probably not familiar with ... software
[18:48:52] <jcoby> check out the mach3 vs emc2 - but not what you think thread
[18:49:01] <cradek> nope, I won't do that
[18:49:05] <jcoby> heh
[18:49:12] <jcoby> he claims to be a java programmer
[18:49:16] <SWPLinux> ynneb?
[18:49:22] <jepler> let's change the subject
[18:49:29] <cradek> cheesebiscuit!
[18:49:40] <SWPLinux> icanhascheezburger
[18:49:48] <SWPLinux> oh, I can hve a cheeseburger. bbl
[18:49:49] <cradek> jepler: apt-file search bin/cb => nothing relevant
[18:50:18] <cradek> so, if you want to write a new SCM system called cheesebiscuit, you're in the clear
[18:50:20] <jcoby> is there anything people are looking to add or change axis?
[18:50:24] <BJT-Work> bacon
[18:51:03] <cradek> jcoby: did you check the feature request tracker on sourceforge? there may be some ideas there - not sure
[18:51:10] <jepler> jcoby: my recent top two wishes are to separate out the 3d plot so that it can run as a separate "preview plot" without emc running; and to rework the jogging logic from scratch
[18:51:38] <cradek> yeah, there has been a lot of talk about more jogging features recently
[18:52:15] <jepler> every once in a while somebody finds a new way to combine keyboard and mouse commands to leave an axis joggine when it shouldn't be .. and the current system is brittle enough to have me scared about adding new features, like shift+jog to temporarily jog at top speed
[18:52:15] <cradek> halscope could use some hacking too - it would be so extremely useful if you could save and load plot data
[18:54:01] <jcoby> jepler: that's why i wanted to clean up the code a bit
[18:54:19] <jcoby> having a 6000 line file makes things somewhat hard to isolate and clean up
[18:54:22] <jepler> cradek: ah, the program I was thinking of is called "cbb", not "cb"
[18:54:30] <cradek> jepler: good
[18:55:33] <jcoby> cradek: i've been trying to find where features requests are kept. things are really disorganized on the website
[18:56:09] <jepler> the issue tracker is on sourceforge .. sf.net/projects/emc and click around wishing you could find it
[18:56:14] <cradek> http://sourceforge.net/projects/emc, click tracker, click feature requests
[18:56:33] <jcoby> thanks
[18:56:39] <jcoby> i also saw stuff on the wiki
[18:56:44] <cradek> god help you if you want to find the mailing lists
[18:57:25] <jcoby> i actually found them pretty easily
[18:57:34] <cradek> ah, good
[18:57:35] <jepler> (and note that we don't necessarily promise that everything in the feature request tracker is a good idea .. I doubt they are)
[18:57:36] <jcoby> finding the CVSROOT was damned near impossible
[18:57:50] <jcoby> jepler: typical of every project
[18:58:01] <cradek> there's lots of info about the cvs on the wiki
[18:58:07] <cradek> including step-by-steps
[18:58:35] <jcoby> cradek: i usually start with developer or contributing documentation. hitting a wiki generally doesn't yield much
[18:58:53] <jcoby> i found it in the "how to get emc2" docs
[18:59:15] <cradek> (we may have docs in too many places.)
[18:59:18] <jepler> bbl
[18:59:46] <jcoby> cradek: it took me a week to find screenshots
[19:00:09] <jcoby> the only entry point to the wiki is on the home page.. and that's the only place that has screenshots
[19:00:26] <cradek> http://www.google.com/search?q=emc2+screenshots
[19:00:44] <cradek> now I think you must be exaggerating?
[19:00:47] <micges> I have strange issue:
[19:01:19] <jcoby> cradek: i wasn't searching 8 hrs a day. more like trying to figure out what all emc2 does from the website
[19:01:38] <micges> I'm using home ignore limits on both x and y axes
[19:02:08] <jcoby> cradek: i'm a web developer. i don't have much patience for bad websites :-)
[19:03:03] <micges> when I've stopped homing when machine was on both limits, then both joint limit on switches errors shows up, is this correct ?
[19:04:05] <micges> on each axis is one limit for homing and limit
[19:04:53] <jcoby> cradek: and yeah, i was exaggerating
[19:05:39] <cradek> micges: yes it is correct that you get two errors if two axes are on limit
[19:06:52] <micges> so if homing state turns off then normal limits error checking turns on immeadiately?
[19:07:28] <cradek> yes
[19:08:10] <micges> just checking thanks
[19:08:45] <cradek> welcome
[19:11:02] <micges> I've just upgraded 2.1.7 to 2.3.0 large 2x2m laser
[19:11:27] <micges> everyone is exited what can be done with it :)
[19:12:20] <micges> of course 2xmesa on board :)
[19:26:01] <jepler> micges must not have read where it says "not for production systems"
[19:26:39] <jepler> EMC2 development -- http://linuxcnc.org/ | 2.3 schedule: beta3 or 2.3.0 according to feedback on beta2 | channel logged by logger_dev
[19:26:49] <jepler> which brings up the question: do we want the next release to be 2.3.0 or 2.3.0beta3?
[19:27:04] <jepler> I still haven't gotten around to installing it on my own system
[19:27:29] <jepler> every time I run 2.2.8, I think "I wish I had that one feature", but then I go ahead and mill my part and forget about it.
[19:27:41] <BJT-Work> I've got it on three computers and the plasma
[19:27:48] <cradek> I've been using it (and trunk leading up to it) for a while. what I'm less sure about is stuff like stepconf that I don't use
[19:28:23] <BJT-Work> I generate stepconf configs all the time for testing things for the manual...
[19:28:36] <cradek> you're a saint
[19:28:48] <BJT-Work> my desktop is covered with configs :)
[19:29:05] <jepler> so it doesn't crash -- but is every single config right?
[19:29:50] <BJT-Work> dunno if they are "right" or not but no crashes
[19:31:59] <BJT-Work> * BJT-Work wanders off to make 6061 chips
[19:34:57] <BJT-Work> I start off each example with a fresh stepconf config
[19:40:50] <jepler> you know you can get rid of the old shortcuts, right?
[19:43:27] <BJT-Work> I clean house from time to time :)
[20:01:06] <alex_joni> hmm.. now I have a config for seb, but he's not here :)
[20:01:07] <alex_joni> http://pastebin.com/m2573b842
[20:13:32] <alex_joni> BJT-Work: is there some doc about joystick/joypad jogging ?
[20:13:44] <alex_joni> something with halui and hal_input ?
[20:14:36] <alex_joni> (found this in the wiki: http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Simple_Remote_Pendant )
[20:16:17] <BJT-Work> think so
[20:16:37] <BJT-Work> not in the manual
[20:16:57] <BJT-Work> yea, that one is a good one