How do I get ReplicatorG to install on a Mac?

[Oliver de Peyer]

Hi,
I'm thinking of buying a Think-O-Matic but first I thought I'd check
out the ReplicatorG software. The main computer I had hoped to use
this on was a G5 iMac, OS X 4.11.
When I double-click on the ReplicatorG icon, all I can see is the
"About" and "Preferences" Finder menu options for ReplicatorG The
ReplicatorG GUI completely fails to load.
I updated to Python 3.2 but this made no difference.
I reckoned that one of you might have had the same experience or know
a workaround.

[Andrew Plumb]

See http://replicat.org/installation-mac

The key is to drag'n'drop-copy all the whole "replicatorg-0023-mac" folder from the .dmg file into Applications, not just the "ReplicatorG" app contained in that folder.

Andrew.

--
You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.
To post to this group, send email to make...@googlegroups.com.
To unsubscribe from this group, send email to makerbot+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/makerbot?hl=en.

--

Makerbot Number Nine... #9... 0x09... 0o11... 0b1001... 
http://clothbot.com/wiki/MakerBotNumberNine

[Oliver de Peyer]

Dear Andrew,
Many thanks - but that is what I had done - the entire folder is in
Applications. Just to make sure, I deleted it and recopied it from
the .dmg again - everything is there in the folder but the problem is
just the same.
Any thoughts?

Oliver

On Feb 9, 9:34 pm, Andrew Plumb <and...@plumb.org> wrote:
> Seehttp://replicat.org/installation-mac

>
> The key is to drag'n'drop-copy all the whole "replicatorg-0023-mac" folder from the .dmg file into Applications, not just the "ReplicatorG" app contained in that folder.
>
> Andrew.
>
> On 2011-02-09, at 4:24 PM, Oliver de Peyer wrote:
>
>
>
> > Hi,
> > I'm thinking of buying a Think-O-Matic but first I thought I'd check
> > out the ReplicatorG software. The main computer I had hoped to use
> > this on was a G5 iMac, OS X 4.11.
> > When I double-click on the ReplicatorG icon, all I can see is the
> > "About" and "Preferences" Finder menu options for ReplicatorG The
> > ReplicatorG GUI completely fails to load.
> > I updated to Python 3.2 but this made no difference.
> > I reckoned that one of you might have had the same experience or know
> > a workaround.
>
> > --
> > You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.
> > To post to this group, send email to make...@googlegroups.com.
> > To unsubscribe from this group, send email to makerbot+u...@googlegroups.com.

> > For more options, visit this group athttp://groups.google.com/group/makerbot?hl=en.

[Jordan Miller]

repg does not and will not work on PPC Mac. skeinforge will not process any files for you unfortunately.

jordan

[Aaron Double]

You can process your files with Skeinfox.

https://github.com/jmil/SkeinFox/wiki/

[Oliver de Peyer]

Many thanks Jordan & Aaron for your advice. Unfortunately Skeinfox
seems to be OS X 5 or 6 only.

I am trying to get ReplicatorG to run on my Linux laptop instead but
that is turning into another great odyssey! (Stay tuned).
I could use another machine under Windows if I had to.

Ol

On Feb 9, 11:51 pm, Aaron Double <aad...@gmail.com> wrote:
> You can process your files with Skeinfox.
>
> https://github.com/jmil/SkeinFox/wiki/
>
> On Feb 9, 2011, at 6:12 PM, Jordan Miller wrote:
>
> > repg does not and will not work on PPC Mac. skeinforge will not process any files for you unfortunately.
>
> > jordan
>

> >> For more options, visit this group athttp://groups.google.com/group/makerbot?hl=en.

[Marius Kintel]

On Feb 10, 2011, at 00:12 AM, Jordan Miller wrote:

> repg does not and will not work on PPC Mac. skeinforge will not process any files for you unfortunately.
>

I don't see any reason why this shouldn't work. Admittedly, it's not a target platform, so it would require someone to put in some work ironing out any issues, if there are any Mac developers out there still on G5's running 10.4.

-Marius

[Oliver de Peyer]

Hi Marius,
Yeh, it seemed odd to me too, because the latest version of Python ran
without any problems at all on my G5, and indeed even supports Mac OS
10.3
I think there will still be quite a lot of PPC Macs out there, which
means Mac OS 4.11 or earlier. One guy I knew had an Oct-Core G5 tower
- that would still be pretty fast today I guess and unlikely to
binned, for example.

I ran into problems with the Linux install too. I can see various
problems piling up when I run ReplicatorG from a terminal in root. I
have, again, installed the latest version of Python. I'm running in
Fedora 7 (for compatibility with some PC104 single board computers I
sometimes use)

(Ironically, ReplicatorG installed absolutely flawlessly on my Windows
Vista machine. SInce I have Rhino3D on the same system, I might stick
with that for now)

Thanks

Oliver

[Andrew Plumb]

If you aren't already, make sure you're using Python 2.6, not the Python 3.x series.

Andrew.

--
You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.
To post to this group, send email to make...@googlegroups.com.
To unsubscribe from this group, send email to makerbot+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/makerbot?hl=en.

[Oliver de Peyer]

Oh dear, I've out 3.2 on all three... will that cause big problems?
(But the Mac problem was present even before I changed to 3.2)

Annoying because the ReplicatorG site specifically says to go for the
most up to date version...

> > For more options, visit this group athttp://groups.google.com/group/makerbot?hl=en.

[Andrew Plumb]

Out of habit, I stick to the 2.x series because 3.x is still quite new (only about a year old IIRC) and breaks lots of legacy code. See http://wiki.python.org/moin/Python2orPython3  Unless you have a developer-specific reason to be running the 3.2 release candidate, you might want to roll that back to 3.1.3.  I'd still recommend sticking to Python 2.7.1 until you get things running; there aren't likely as many PPC machines out there anymore to give 3.x the same degree of attention that 2.x has received over the years.

That said, the python dependency only comes into play for the skeinforge slicing though.  If you can't even launch the ReplicatorG UI then you likely have a Java VM dependency to resolve.  Not sure what the story is for that in Mac OS 10.3; might have to manually download and install updates from Apple.

If the ReplicatorG UI does come up, make sure you go into the preferences and "Select Python interpreter" to try your new(er) version.

Andrew.

For more options, visit this group at http://groups.google.com/group/makerbot?hl=en.

[Oliver de Peyer]

Hi Andrew,

ReplicatorG does partially run on the Mac... you get a basic menu come
up in the Finder but nothing else.
There's a screenshot at:
http://replicatorg.lighthouseapp.com/projects/66325/tickets/95-replicatorg23-wont-start-on-mac#ticket-95-1
- but nothing in Replicator's own GUI. This does though give me a
chance to select the Python interpreter - this doesn't make any
difference.
I will check out the Java VM.... I'm on Mac OS X 4.11 so not quite as
bad as 3!

But can it really be Java? For both Mac & Linux, the ReplicatorG site
says you need at least Java 1.5. 1.5 is pre-installed in Mac OS X 4,
and indeed on my Fedora 7 machine as well. Would updating help?

My apologies, I was going on about Python 3.2 but upon checking it is
3.1.3 that I have indeed installed.

I would still like to get it running on these two machines, but I had
the most success on my Windows machine, so maybe I should cut my
losses. I am using Python 3.1.3 there too though.
I've kind-of lost my confidence so is there a cradle-to-grave test I
could make in simulation?
Can I run it all the way through and generate gcode, even without an
actual piece of hardware attached?
And if I do, how can I check that the gcode is valid?

I am very new at this, apologies for all the questions!!

Thanks

Oliver

On Feb 13, 4:31 am, Andrew Plumb <and...@plumb.org> wrote:
> Out of habit, I stick to the 2.x series because 3.x is still quite new (only about a year old IIRC) and breaks lots of legacy code. Seehttp://wiki.python.org/moin/Python2orPython3 Unless you have a developer-specific reason to be running the 3.2 release candidate, you might want to roll that back to 3.1.3.  I'd still recommend sticking to Python 2.7.1 until you get things running; there aren't likely as many PPC machines out there anymore to give 3.x the same degree of attention that 2.x has received over the years.