Step-by-step instructions: installing RoboFab 1.2 rev 226 in FLS 5.1 on Mac OS X 10.7.2

[Adam Twardoch]

I've just tested those instructions to install RoboFab with FontLab
Studio 5.1 build 4311 and Mac OS X 10.7.2. They work fine.

Since the system Python 2.7 in Mac OS X 10.7.2 comes with pre-
installed NumPy, it's no longer necessary to install NumPy. Therefore,
if you're on Mac OS X 10.7.2 and you have FontLab Studio 5.1 build
4311 or newer installed, do the following:

1. Quit FontLab Studio.

2. Download:
http://robofab.org/download/current/RoboFab226M_plusDependencies.zip

2. In Finder, navigate to the location where you downloaded the .zip
file, double-click to unzip it (if it already hadn't happened). You
should see a folder named "RoboFab226M_plusDependencies".

3. Open the Terminal app

4. In Terminal, type "cd " (with a trailing space) but don't hit
Enter. Drag the RoboFab226M_plusDependencies folder to the Terminal
window. You should see something like this in the Terminal window:

cd /users/[your username]/Downloads/RoboFab226M_plusDependencies

5. In Terminal, hit Enter.

6. In Terminal, do the following:
(Hit Enter after each line. After the first "sudo" you'll need to
enter your administrator password.)

cd FontTools
sudo /usr/bin/python setup.py install
cd ..
cd RoboFab
sudo /usr/bin/python setup.py install
cd ..
cd DialogKit
sudo mv Lib/dialogKit/ /Library/Python/2.7/site-packages/

7. In Finder, do File / New Finder Window

8. If you have enabled "Use custom locations for user data folders" in
FontLab Studio / Preferences / General Options / Folders and paths,
navigate Finder to folder that you've set as the "FontLab Studio user
data files" folder, and skip to step 8.

9. If you have not customized the location, then in Finder's menu,
choose Go / Go to Folder...

10. In the text box that appears, enter:
~/Library/Application Support/FontLab/Studio 5/Macros
and click on Go.

11. Your Finder should now should show a Macro folder with at least
three subfolders in it (Effects, Export and System).

12. Switch to the Finder window that has the
RoboFab226M_plusDependencies folder, and open the subfolder RoboFab/
Scripts folder that is inside.

13. You should see a folder with several subfolders: "Contributed",
"RoboFabIntro", "RoboFabUFO", "RoboFabUFO2", "RoboFabUtils".

14. Select those folders and drag them to the Macro folder in the
other Finder window.

15. Open FontLab Studio and in the Edit Macro panel type in:

import robofab
import dialogKit

If you don't see anything in the Output panel, you have installed
RoboFab and its FontLab macros and DialogKit successfully.

Best,
Adam

[Adam Twardoch]

I have edited the instructions slightly and posted them at:

http://forum.fontlab.com/python-scripting/instructions-installing-robofab-12-rev-226-in-fls-51-on-mac-os-x-1072-t8300.0.html

A.

--

May success attend your efforts,
-- Adam

[Ben Kiel]

Adam,

These look good. I'd just note that any scripts using dialogs from RoboFab likely won't work with the robofab download you linked to. The svn version is a better choice currently.

To edit your instructions, I'd say this:

2.
Create a folder for your RoboFab and other sources. It doesn't really matter where this folder is, or what it is called, but a good practice would be to put in in your user folder, name it with just one word —no spaces or glyphs outside of ascii. For example, my folder for such things is ~/benkiel/code/. The easiest way to make said folder is to open up Terminal.app, and type:

mkdir ~/code
[Replace 'code' with whatever you want to call your source folder.]

Hit enter

3.
Open Terminal.app if you haven't already

4.
In terminal, type:

cd ~/code (of course, if you've called the folder something else, use that)

Hit enter

5.
Next, you'll need to checkout the svn robofab, dialogkit and fonttools. You must be online for the following to work.

This is simply done by typing:

svn checkout http://svn.robofab.com/

Hit enter, watch things scroll by.

Next, you'll need to get dialog kit. This can also be done with a svn checkout. Type:

svn checkout http://svn.typesupply.com/packages/dialogKit

Hit enter, watch things scroll by.

Lastly, you'll need FontTools. Again, a svn checkout will get you that. Type:

svn checkout https://fonttools.svn.sourceforge.net/svnroot/fonttools

Hit enter, watch things scroll by.

If you now type ls in terminal you should see the following three folders:

benBookPro-2:test benkiel$ ls
dialogKit fonttools svn.robofab.com

6. In Terminal, do the following:
(Hit Enter after each line. After the first "sudo" you'll need to enter your administrator password.)

cd fonttools/trunk
sudo /usr/bin/python setup.py install
cd ../..
cd svn.robofab.com/trunk
sudo /usr/bin/python install.py
cd ../..
cd dialogKit/trunk
sudo /usr/bin/python install.py

Best,
Ben

> --
> You received this message because you are subscribed to the Google Groups "RoboFab" group.
> To post to this group, send email to rob...@googlegroups.com
> To unsubscribe from this group, send email to robofab-u...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/robofab?hl=en
>
> Messages from newly joined members are subject to moderation.
> Download RoboFab and documentation at http://robofab.com
>
> !DSPAM:4eaaca0628021248311248!
>

Ben Kiel
http://www.houseind.com
Direct Dial: (302) 766-7593

[Erik van Blokland]

Thanks Adam, Ben!

I've packaged the current trunk version of Robofab. This includes the
new arrayTools and bezierTools, as well as the revised dialogs.

http://robofab.com/download/index.html

The one to get would be RoboFab rev.483 + (up to date) dependencies:
http://robofab.com/download/current/RoboFab483M_plusDependencies.zip

There's also a zip with just RoboFab, without dependencies:
http://robofab.com/download/current/RoboFab483M_Only.zip

The distro-making tools are in the robofab trunk too (rev 484).

Cheers,
Erik

[Dezcom]

Since I have just today managed to get the previous version running by
using Adam's installation procedure, should I just repeat his
procedure to replace the old version with your new version or is there
a better way to install over the existing version now in my Lion
System?

Thanks,

Chris

[Erik van Blokland]

On 29 okt 2011, at 00:37, Dezcom wrote:

Since I have just today managed to get the previous version running by
using Adam's installation procedure, should I just repeat his
procedure to replace the old version with your new version or is there
a better way to install over the existing version now in my Lion
System?

These instructions should work. Except that you start from a new zip.

But, Chris, I'm not sure the changes are big enough to warrant a whole new install. Why don't you work with what you have and see if you run into any problems. You can always do an upgrade later.

Erik

[Dezcom]

I was hoping you would say that!
My wirehead tentacles have grown weary and I long to go back and
design some type :-)

Chris

[Adam Twardoch]

On 11-10-28 23:59, Erik van Blokland wrote:
> The one to get would be RoboFab rev.483 + (up to date) dependencies:
> http://robofab.com/download/current/RoboFab483M_plusDependencies.zip

Erik,

I've downloaded the zip and it seems that in the Vanilla subfolder the
contents of "DialogKit" is included, rather than that of Vanilla.

Am I blind or doing something wrong, or is that an oversight on your side?

Best,
Adam

[Erik van Blokland]

On 29 okt 2011, at 18:31, Adam Twardoch wrote:

I've downloaded the zip and it seems that in the Vanilla subfolder the
contents of "DialogKit" is included, rather than that of Vanilla.

Am I blind or doing something wrong, or is that an oversight on your side?

Fixed. Vanilla is now in the right place.

Changeset 485 - robofabtrac - Trac

The combo is at the same URL:

RoboFab rev.483 + FontTools rev.589 and DialogKit + Vanilla rev.989

Thanks Adam!

Erik

[James Puckett]

I am trying to get Fontlab 5.1 and Robofab working on a new mac running 10.7. I tried Adam’s instructions using the latest package at Robofab.org. I can import robofab and dialog kit. But when I try to run a Robofab script I get the following traceback:

Traceback (most recent call last):

  File "<string>", line 19, in <module>

  File "/Library/Python/2.7/site-packages/robofab/world.py", line 95, in <module>

    from robofab.objects.objectsFL import CurrentFont, CurrentGlyph, RFont, RGlyph, OpenFont, NewFont, AllFonts

  File "/Library/Python/2.7/site-packages/robofab/objects/objectsFL.py", line 6, in <module>

    from robofab.objects.objectsBase import BaseFont, BaseGlyph, BaseContour, BaseSegment,\

  File "/Library/Python/2.7/site-packages/robofab/objects/objectsBase.py", line 27, in <module>

    from robofab.misc.arrayTools import updateBounds, pointInRect, unionRect, sectRect

ImportError: No module named misc.arrayTools

What am I doing wrong?

James Puckett

[Dezcom]

James,
Sounds similar to what I was experiencing before. Which RoboFab
download did you use?

On 11-10-28 23:59, Erik van Blokland wrote:
> The one to get would be RoboFab rev.483 + (up to date) dependencies:
> http://robofab.com/download/current/RoboFab483M_plusDependencies.zip

Also, you may need to redefine the path back as per Adam's "8. If you

have enabled "Use custom locations for user data folders" in
FontLab Studio / Preferences / General Options / Folders and paths,
navigate Finder to folder that you've set as the "FontLab Studio user

data files" folder..."

ChrisL

[Erik van Blokland]

James,

On 9 nov 2011, at 19:04, James Puckett wrote:

  File "/Library/Python/2.7/site-packages/robofab/objects/objectsBase.py", line 27, in <module>

    from robofab.misc.arrayTools import updateBounds, pointInRect, unionRect, sectRect

ImportError: No module named misc.arrayTools

What am I doing wrong?

Hard to guess from a distance. What is odd about the importError is that the  from robofab.misc.arrayTools means it is the new version (this was introduced in the last robofab release). But then it seems your FL can't find it?

So, I only have indirect advice:

- can you see if the folder 

/Library/Python/2.7/site-packages/robofab/misc 

exists and that it contains a bunch of tiles, one of them named arrayTools

- if they exists, can you see if these files and the /misc folder maybe have the wrong permissions? should be readable and possibly executable. 

If that doesn't work - scrape the RoboFab folder from /Library/Python/2.7/site-packages and try the steps that install robofab again. 

Erik

[James Puckett]

Erik,

Thanks. I checked and /Library/Python/2.7/site-packages/robofab/misc did not exist. I had already cleaned out Robofab and reinstalled once, so I am sure that I followed the install procedure. So I copied 

…/RoboFab483M_plusDependencies/RoboFab/Lib/robofab/misc

to

/Library/Python/2.7/site-packages/robofab/misc 

and now I have some Robofab functionality. I can run the “Start Here” script and get:

Robofab is running on darwin, Python version: 2.7, Mac stuff: X, PC stuff: None, FontLab stuff: True, FLversion: 5.1/Mac(Build 4311), Glyphs stuff: False, Glyphs version: None, RoboFont stuff: False, RoboFont version: None

And I can also dump a complete font to a valid UFO with the UFO2 “export…from all open fonts” script.

But more complex stuff is still broken. Trying to create a UFO of selected glyphs with UFO central fails:

Traceback (most recent call last):

  File "/Library/Python/2.7/site-packages/dialogKit/_dkFL.py", line 138, in on_ok

    self._okCallback(self)

  File "<string>", line 440, in okCallback

  File "<string>", line 707, in exportUFO

  File "/Library/Python/2.7/site-packages/robofab/objects/objectsFL.py", line 990, in writeUFO

    bar = ProgressBar("Exporting UFO", nonGlyphCount + len(glyphs))

TypeError: object.__new__() takes no parameters

Best,

James

--

[Ben Kiel]

James:

Progress Bar isn't part of the new dialogs. I think that you'll find if you update your copy of UFO Central (http://code.typesupply.com/browser/applicationScripts/FontLab/UFO/UFOCentral.py?format=raw), that it doesn't use ProgressBar anymore. At least it appears not to from a quick find. It does import ProgressBar still, but that won't cause any problems as it doesn't try to create one.

Best,

Ben

Download RoboFab and documentation at http://robofab.com !DSPAM:4ebafe3d28021196017022!

[James Puckett]

Ben,

That is the version of UFO central that I am using.

Best,

James

[Ben Kiel]

James,

My mistake for looking too quickly at the traceback. A closer read shows that the problem is in the code in RoboFab for writing a UFO. If you want a quick fix, search the UFOCentral macro for "doProgress=True" (without quotes), you'll find it twice, and change it to "doProgress=False" (again, without quotes). 

Ben

James

Ben Kiel

http://www.houseind.com

Direct Dial: (302) 766-7593

--
You received this message because you are subscribed to the Google Groups "RoboFab" group.
To post to this group, send email to rob...@googlegroups.com
To unsubscribe from this group, send email to robofab-u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/robofab?hl=en
 
Messages from newly joined members are subject to moderation.
Download RoboFab and documentation at http://robofab.com

--
You received this message because you are subscribed to the Google Groups "RoboFab" group.
To post to this group, send email to rob...@googlegroups.com
To unsubscribe from this group, send email to robofab-u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/robofab?hl=en
 
Messages from newly joined members are subject to moderation.

Download RoboFab and documentation at http://robofab.com !DSPAM:4ebb061328027983167028!

[Erik van Blokland]

On 9 nov 2011, at 23:26, James Puckett wrote:

Thanks. I checked and /Library/Python/2.7/site-packages/robofab/misc did not exist. I had already cleaned out Robofab and reinstalled once, so I am sure that I followed the install procedure. So I copied 

…/RoboFab483M_plusDependencies/RoboFab/Lib/robofab/misc

to

/Library/Python/2.7/site-packages/robofab/misc 

and now I have some Robofab functionality. I can run the “Start Here” script and get:

Robofab is running on darwin, Python version: 2.7, Mac stuff: X, PC stuff: None, FontLab stuff: True, FLversion: 5.1/Mac(Build 4311), Glyphs stuff: False, Glyphs version: None, RoboFont stuff: False, RoboFont version: None

Hurray!

And I can also dump a complete font to a valid UFO with the UFO2 “export…from all open fonts” script.

Right. I'm curious though about the chain of events that resulted in an incomplete robofab installation in site-packages in the first place. Did you copy parts manually? Or maybe was there an older robofab version installed there and then the new one tried to overwrite it?

But more complex stuff is still broken. Trying to create a UFO of selected glyphs with UFO central fails:

Traceback (most recent call last):

  File "/Library/Python/2.7/site-packages/dialogKit/_dkFL.py", line 138, in on_ok

    self._okCallback(self)

  File "<string>", line 440, in okCallback

  File "<string>", line 707, in exportUFO

  File "/Library/Python/2.7/site-packages/robofab/objects/objectsFL.py", line 990, in writeUFO

    bar = ProgressBar("Exporting UFO", nonGlyphCount + len(glyphs))

TypeError: object.__new__() takes no parameters

I hadn't gotten around to paying some TLC to ProgressBar. Tal checked in a new version for FL. 

http://code.robofab.com/changeset/490

When I have time I will pack up another zip. (if others are so inclined: the zip packer script is conveniently part of the svn distro now :)

Erik

[James Puckett]

This was a clean install of 483M on a new computer. I followed Adam’s instructions step-by-step both times, so I have no idea how it got installed with no misc directory.

--

[James Puckett]

Thanks Ben, that worked. I stripped all references of ProgressBar from UFOCentral and it seems to work fine, albeit so quickly that it seems to do nothing ;). I attached my “working” version if anybody else needs it.

[Adam Twardoch]

On 11-11-11 23:39, James Puckett wrote:
> Thanks Ben, that worked. I stripped all references of ProgressBar from
> UFOCentral and it seems to work fine, albeit so quickly that it seems
> to do nothing ;). I attached my “working” version if anybody else
> needs it.

That's interesting. I recently did a similar thing: I realized that in
some operations, the progress bar, especially a very finely grained one,
is the reason for actually slowing down the operation in a notable way.
I got rid of some of those myself in various macros I've written :)

[David Cabianca]

I am sorry to add to the list. I have read through the threads and I
see a lot of effort on the part of Erik, Tal, Ben, Adam and others to
sort this problem out. I am sorry to add to the pile.
I have tried the recommendations above by Adam and Ben. I have
reinstalled FontLab 5.1 and 5.1.1. I have reinstalled RoboFab quite a
few times. Unfortunately all I can get out for my Fontlab now is a
similar message as below, no matter what script I try, they all end
with "ImportError: No module named misc.arrayTools."

I am using OSX 10.7.2, and with Python 2.7.2 (v2.7.2:8527427914a2, Jun
11 2011, 15:22:34);
My FontLab is using 2.7.1 (r271:86832, Jun 16 2011, 16:59:06). If
anyone has any suggestions, please let me know. Sorry to be such a
newbie.
__

Traceback (most recent call last):

File "<string>", line 29, in <module>

File "/Library/Python/2.7/site-packages/robofab/world.py", line 95,
in <module>
from robofab.objects.objectsFL import CurrentFont, CurrentGlyph,
RFont, RGlyph, OpenFont, NewFont, AllFonts
File "/Library/Python/2.7/site-packages/robofab/objects/
objectsFL.py", line 6, in <module>
from robofab.objects.objectsBase import BaseFont, BaseGlyph,
BaseContour, BaseSegment,\
File "/Library/Python/2.7/site-packages/robofab/objects/

[Erik van Blokland]

Hi David,
the problem is that the 2.7.2 is "occupying" the command line. So when
you type "python", you end up working with 2.7.2, rather than the
2.7.1. So all your install efforts go towards 2.7.2.

It's a nuisance the folks at Python and the folks at Apple decided to
deal with Python sub versions (2.7.1 vs 2.7.2) in such a way.

From our earlier correspondence I know:
python version 2.7.1 (r271:86832, Jun 16 2011, 16:59:06)
site-packages is at /Library/Python/2.7/site-packages

python version 2.7.2 (v2.7.2:8527427914a2, Jun 11 2011, 15:22:34)
site-packages is at /Library/Frameworks/Python.framework/Versions/2.7/
lib/python2.7/site-packages

If you open the 2.7.2 site-pacakges folder you will see the results of
your install work. Robofab, DialogKit, Vanilla, FontTools - either
pointed to by *.pth files or as actual packages in folders.

Now open the 2.7.1 site-packages folder in another window. It is
probably rather empty.

The easiest thing to try would be to proceed to *copy* all files and
folders that relate to RoboFab, DialogKit, FontTools, Vanilla
(including files ending in .pth and folders) from one to the other.
This might require you to type your password.

That will put all the modules on the search path for the 2.7.1 python,
and they will be available to FontLab 5.1.

Erik

[Erik van Blokland]

Another thing you could try is to find out the actual path the 2.7.1
python

What do you get when you do this in Terminal:

cd /usr/bin
ls -la py*

(I'm resisting having to install 2.7.2 myself)

E

[Adam Twardoch]

FontLab Studio 5.1 links to the Python framework present in:
/System/Library/Frameworks/Python.framework/Versions/Current

This is always the Python framework pre-installed by Apple. (Note: It
wasn't completely easy to do for our developers, since "Current" is an
alias and XCode requires a real path. So the application does a bit of
trickery itself to work around that limitation.)

However, we're not at this time able to link to "any" Python available
on the system. In other words, if you've installed a custom Python from
python.org or fink or MacPorts or homebrew or using any other method,
FontLab Studio won't be able to access it -- simply because there are
just too many ways in which Python can be built and installed.

So while FontLab Studio 5.1 is more flexible than the previous versions,
because it links to the most current version of Python *pre-installed by
Apple* on Mac OS X, it won't link to *just any* Python. Especially not
to the Python that the user installed him/herself.

Sorry.

We will investigate the possibility of making the version of Python used
by FontLab Studio selectable by the user from within the application.
But I can't promise that it'll be done, because at this moment I don't
know if it can easily be done.

Best,
Adam

[Erik van Blokland]

On 4 jan. 2012, at 18:39, Adam Twardoch wrote:

So while FontLab Studio 5.1 is more flexible than the previous versions,
because it links to the most current version of Python *pre-installed by
Apple* on Mac OS X, it won't link to *just any* Python. Especially not
to the Python that the user installed him/herself.

Sorry.

Sorry indeed. But I have seen at least one MacBook running 10.7 that had not had any pythons installed by the user, but the command line version was still 2.7.2, FontLab linked to 2.7.1. 

I understand it is tricky - Apple and the Python maintainers certainly did set us up with a messy system. Question is, how are we going to respond. 

A structural and useful approach would be to have a pref in FontLab where I can add paths to addional modules that will be added to FontLab's sys.path. The setup would then become part of FontLab's responsibility, save nicely with its other prefs and so on. It would be a nice non-robofab specific solution to the FontLab python setup. Adding stuff to sys.path is really simple. Adding a window and a pref wouldn't break the bank either (well, if I write them in python they wouldn't— not sure how that goes in C++) But — Can you give us that?

E

[David Cabianca]

On Jan 4, 12:27 pm, Erik van Blokland <letter...@gmail.com> wrote:
> Another thing you could try is to find out the actual path the 2.7.1
> python
>
> What do you get when you do this in Terminal:
>
> cd /usr/bin
> ls -la py*
>

Here is the output. However I can't tell if it is showing v2.7.1 or
v2.7.2:

-rwxr-xr-x 6 root wheel 925 Oct 28 12:36 pydoc
lrwxr-xr-x 1 root wheel 74 Oct 28 12:36 pydoc2.5 -> ../../System/
Library/Frameworks/Python.framework/Versions/2.5/bin/pydoc2.5
lrwxr-xr-x 1 root wheel 74 Oct 28 12:36 pydoc2.6 -> ../../System/
Library/Frameworks/Python.framework/Versions/2.6/bin/pydoc2.6
lrwxr-xr-x 1 root wheel 74 Oct 28 12:36 pydoc2.7 -> ../../System/
Library/Frameworks/Python.framework/Versions/2.7/bin/pydoc2.7
-rwxr-xr-x 2 root wheel 62752 Oct 28 12:36 python
-rwxr-xr-x 6 root wheel 925 Oct 28 12:36 python-config
lrwxr-xr-x 1 root wheel 75 Oct 28 12:36 python2.5 -> ../../
System/Library/Frameworks/Python.framework/Versions/2.5/bin/python2.5
lrwxr-xr-x 1 root wheel 82 Oct 28 12:36 python2.5-config -
> ../../System/Library/Frameworks/Python.framework/Versions/2.5/bin/
python2.5-config
lrwxr-xr-x 1 root wheel 75 Oct 28 12:36 python2.6 -> ../../
System/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6
lrwxr-xr-x 1 root wheel 82 Oct 28 12:36 python2.6-config -
> ../../System/Library/Frameworks/Python.framework/Versions/2.6/bin/
python2.6-config
lrwxr-xr-x 1 root wheel 75 Oct 28 12:36 python2.7 -> ../../
System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
lrwxr-xr-x 1 root wheel 82 Oct 28 12:36 python2.7-config -
> ../../System/Library/Frameworks/Python.framework/Versions/2.7/bin/
python2.7-config
-rwxr-xr-x 2 root wheel 62752 Oct 28 12:36 pythonw
lrwxr-xr-x 1 root wheel 76 Oct 28 12:36 pythonw2.5 -> ../../
System/Library/Frameworks/Python.framework/Versions/2.5/bin/pythonw2.5
lrwxr-xr-x 1 root wheel 76 Oct 28 12:36 pythonw2.6 -> ../../
System/Library/Frameworks/Python.framework/Versions/2.6/bin/pythonw2.6
lrwxr-xr-x 1 root wheel 76 Oct 28 12:36 pythonw2.7 -> ../../
System/Library/Frameworks/Python.framework/Versions/2.7/bin/pythonw2.7

[David Cabianca]

Done. However it did not help. :-/

I still get an error message:

Traceback (most recent call last):
File "<string>", line 29, in <module>
File "/Library/Python/2.7/site-packages/robofab/world.py", line 95,
in <module>
from robofab.objects.objectsFL import CurrentFont, CurrentGlyph,
RFont, RGlyph, OpenFont, NewFont, AllFonts
File "/Library/Python/2.7/site-packages/robofab/objects/
objectsFL.py", line 6, in <module>
from robofab.objects.objectsBase import BaseFont, BaseGlyph,
BaseContour, BaseSegment,\
File "/Library/Python/2.7/site-packages/robofab/objects/
objectsBase.py", line 27, in <module>
from robofab.misc.arrayTools import updateBounds, pointInRect,
unionRect, sectRect
ImportError: No module named misc.arrayTools

Thanks just the same.

[Ben Kiel]

David:

Out of curiosity, what's in your /hard drive/Library/Python/2.7/site-packages folder?

Quick way to dump that out is go to terminal and type:

cd /Library/Python/2.7/site-packages
ls -a

Best,
Ben

> --
> You received this message because you are subscribed to the Google Groups "RoboFab" group.
> To post to this group, send email to rob...@googlegroups.com
> To unsubscribe from this group, send email to robofab-u...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/robofab?hl=en
>
> Messages from newly joined members are subject to moderation.
> Download RoboFab and documentation at http://robofab.com
>

> !DSPAM:4f0ae83027992787694347!

[David Cabianca]

Hello Ben,

Here is the output from Terminal:

David-Cabiancas-Computer:site-packages davidc$ ls -a
. dialogKit
.. dialogKit.pth
FontTools robofab
FontTools.pth robofab-1.1.3_-py2.7.egg-info
README robofab.pth

Cheers,
David

[Erik van Blokland]

On 13 feb. 2012, at 09:09, Roland wrote:

Does anybody have an idea where I went wrong?

No idea. You need to give me more numbers.

Which platform and version, which FontLab version? 

One of the recurring issues is that the Python 2.7 that does all the work in the Terminal (when you're following the steps), is not the version that's doing the work in FontLab. So that's something to check.

In Terminal, open Python, can you import robofab there? Something like this:

[eBookPro:~] erik% python

Python 2.7.1 (r271:86832, Jul 31 2011, 19:30:53) 

[GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on darwin

Type "help", "copyright", "credits" or "license" for more information.

>>> import robofab

>>> 

In FontLab:

import sys

print sys.version

Erik

[Erik van Blokland]

Hi Roland,

I hope you don't mind I CC this to the robofab list, I think it might be useful to have this in the archive.

On 13 feb. 2012, at 09:49, TGG | Roland Stieger wrote:

Thank you very much for your quick answer.

Which platform and version, which FontLab version? 

Mac OSX 10.7.3, iMac Intel Core i5, and FontLab 5.1 Build 4269

Ok.

In Terminal, open Python, can you import robofab there? Something like this:If I type in pathon in the terminal, I got this:
Python 2.7.2 (v2.7.2:8527427914a2, Jun 11 2011, 15:22:34) 
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin

Type "help", "copyright", "credits" or "license" for more information.

import robofab

This worked in the terminal

Ok. That means that you followed the step by step instructions correctly. The problem is that this installed it for Python 2.72, and your FontLab is using 2.5.6.

Just out of curiosity, did you install a python version yourself? I'm still assuming 10.7 comes with 2.7.1, but I'm spotting 2.7.2 in the wild. I'm still on 10.7.2.

In FontLab:

import sys

print sys.version

2.5.6 (r256:88840, Jul 31 2011, 19:30:45) 

You have 2 ways to solve this:

1 Reinstall: you follow the step by step instructions again, but now rather than call "python" (which defaults to python 2.7.2 on your system), type "python2.5", which should get you to the python 2.5.6. (This is assuming you only have 1 python 2.5 version). Note: if you upgrade to the current FontLab 5.1 version you have to do this again.

2 Copy: the files directly from one site-packages to the other. This particular method might not be recommended by my associates because you need to be precise about which files you transplant and you might break other things. But here it is:

In the Finder you open a window on

/Library/Python/2.5/site-packages/

and

/Library/Python/2.7/site-packages/

(NOTE: this might not be the 2.7.2 site-packages, but rather the 2.7.1, If you want to find out where the site-packages folder is where all your installations ended up, go to Terminal and run

import sys

for s in sys.path:

if s.find("site-packages")!=-1:

print s

That should print a couple of paths. Find the one that ends in site-packages/

Trick: if you want to open a folder in the Finder, from Terminal, do "open <path>" and a window will pop. Example:

[eBookPro:~] erik% open /Library/Python/2.7/site-packages

Now, with those 2 windows open (you still have the 2.5.6 site-packages window open, right?), you can *copy* the files and folder (FROM 2.5 folder TO 2.7 folder) that look like they're related to robofab. If the 2.7 folder already has robofab and fonttools stuff, you're probably looking at the wrong one.

I can't give you the exact list of names because I don't have 2.7.2 installed and my installation is different. But if you give me the list of files and folders you find in the 2.7 site-packages I can tell  you which ones you need to copy.

Erik