Re: [PyCAM-devel] Hard for a user to know where to get the latest version

[Valerio B. <va...@se...>]

On Fri, 2014-07-18 at 00:58 +0100, Damian Moore wrote:
> First of all, I'm just beginning my journey with CAM and am very pleased 
> a tool like PyCAM exists. I started out using the stable release but any 
> non-trivial jobs were taking a long time and then running out of RAM and 
> Swap. Somewhere I read that it was recommended to use the development 
> version and sure enough it was drastically less resource heavy.
> 
> It was not easy to get to where I am though. There seems to be an SVN 
> and Git repo hosted with Sourceforge - As far as I can tell they are 
> actually separate repos and not linked in any way. When searching the 
> mailing list I found Paul Bonser has a Git repo on Github (which would 
> be preferable for me). This seems to be older than the SF Git repo but 
> there are 4 people forking it on Github and some of those are quite 
> recent but I don't know if they're pulling in changes for the other 
> repos. Then there's also the confusion of pycam++ - Is this the 
> replacement version? I couldn't compile that and gave up after 30 mins.
> 
> The main reason I am going through checking out each of these repos is 
> that I have a problem with the waterline process strategy which I would 
> like to report as a bug as it seems a regression from the stable 
> version. However, without testing different repos, I can't be sure that 
> I don't just have out-dated code.
> 
> Would it be possible to add a sentence to the main project page stating 
> where official development happens and a simple command for developers 
> to clone/checkout the latest code?
> 
> It seems that (unless I'm misunderstood) there are no active developers 
> working on this so making it easy for developers to get involved in the 
> project is really important. Github seems to be where everybody is right 
> now and I wouldn't mind taking over some of the management. It seems 
> like the main solution would be to get a new stable release ready. I'm 
> happy to get involved with that.
> 
> Regards,
> Damian

I recommend start using version 0.5.1, the latest git master branch
produces bad gcode (for me).

We started by using this version (0.5.1) and made some good jobs. When
switched to latest git revision , it produces a considerable amount of
unwanted moves.

After testing both versions we are now writing our gcode by hand.


Cheers.