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:
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.
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.
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
On Oct 28, 2011, at 11:27 AM, Adam Twardoch wrote:
> 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:
> 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
> -- > You received this message because you are subscribed to the Google Groups "RoboFab" group. > To post to this group, send email to robofab@googlegroups.com > To unsubscribe from this group, send email to robofab-unsubscribe@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
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
On Oct 28, 5:59 pm, Erik van Blokland <letter...@gmail.com> 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.
> > 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.
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
On Fri, Oct 28, 2011 at 11:27 AM, Adam Twardoch <a...@twardoch.com> wrote: > 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:
> 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
> -- > You received this message because you are subscribed to the Google Groups > "RoboFab" group. > To post to this group, send email to robofab@googlegroups.com > To unsubscribe from this group, send email to > robofab-unsubscribe@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
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
On Nov 9, 1:04 pm, James Puckett <james.puck...@gmail.com> wrote:
> 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
> On Fri, Oct 28, 2011 at 11:27 AM, Adam Twardoch <a...@twardoch.com> wrote:
> > 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:
> > 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
> > --
> > You received this message because you are subscribed to the Google Groups
> > "RoboFab" group.
> > To post to this group, send email to robofab@googlegroups.com
> > To unsubscribe from this group, send email to
> > robofab-unsubscribe@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 athttp://robofab.com
> 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.
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
On Wed, Nov 9, 2011 at 4:58 PM, Erik van Blokland <letter...@gmail.com>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
> -- > You received this message because you are subscribed to the Google Groups > "RoboFab" group. > To post to this group, send email to robofab@googlegroups.com > To unsubscribe from this group, send email to > robofab-unsubscribe@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
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/UFO...), 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.
> 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
> On Wed, Nov 9, 2011 at 4:58 PM, Erik van Blokland <letter...@gmail.com> wrote: > 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
> -- > You received this message because you are subscribed to the Google Groups "RoboFab" group. > To post to this group, send email to robofab@googlegroups.com > To unsubscribe from this group, send email to robofab-unsubscribe@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 robofab@googlegroups.com > To unsubscribe from this group, send email to robofab-unsubscribe@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:4ebafe3d28021196017022!
On Wed, Nov 9, 2011 at 5:51 PM, Ben Kiel <b...@houseind.com> wrote: > 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/UFO...), > 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
> On Nov 9, 2011, at 5:26 PM, James Puckett wrote:
> 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
> On Wed, Nov 9, 2011 at 4:58 PM, Erik van Blokland <letter...@gmail.com>wrote:
>> 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
>> -- >> You received this message because you are subscribed to the Google Groups >> "RoboFab" group. >> To post to this group, send email to robofab@googlegroups.com >> To unsubscribe from this group, send email to >> robofab-unsubscribe@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 robofab@googlegroups.com > To unsubscribe from this group, send email to > robofab-unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/robofab?hl=en
> -- > You received this message because you are subscribed to the Google Groups > "RoboFab" group. > To post to this group, send email to robofab@googlegroups.com > To unsubscribe from this group, send email to > robofab-unsubscribe@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
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).
> That is the version of UFO central that I am using.
> Best,
> James
> On Wed, Nov 9, 2011 at 5:51 PM, Ben Kiel <b...@houseind.com> wrote: > 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/UFO...), 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
> On Nov 9, 2011, at 5:26 PM, James Puckett wrote:
>> 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
>> On Wed, Nov 9, 2011 at 4:58 PM, Erik van Blokland <letter...@gmail.com> wrote: >> 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
>> -- >> You received this message because you are subscribed to the Google Groups "RoboFab" group. >> To post to this group, send email to robofab@googlegroups.com >> To unsubscribe from this group, send email to robofab-unsubscribe@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 robofab@googlegroups.com >> To unsubscribe from this group, send email to robofab-unsubscribe@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 robofab@googlegroups.com > To unsubscribe from this group, send email to robofab-unsubscribe@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 robofab@googlegroups.com > To unsubscribe from this group, send email to robofab-unsubscribe@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!
> 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 :)
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.
On Thu, Nov 10, 2011 at 2:07 AM, Erik van Blokland <letter...@gmail.com>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
> -- > You received this message because you are subscribed to the Google Groups > "RoboFab" group. > To post to this group, send email to robofab@googlegroups.com > To unsubscribe from this group, send email to > robofab-unsubscribe@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
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.
On Wed, Nov 9, 2011 at 6:05 PM, Ben Kiel <b...@houseind.com> wrote: > 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
> On Nov 9, 2011, at 6:00 PM, James Puckett wrote:
> Ben,
> That is the version of UFO central that I am using.
> Best,
> James
> On Wed, Nov 9, 2011 at 5:51 PM, Ben Kiel <b...@houseind.com> wrote:
>> 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/UFO...), >> 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
>> On Nov 9, 2011, at 5:26 PM, James Puckett wrote:
>> 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
>> On Wed, Nov 9, 2011 at 4:58 PM, Erik van Blokland <letter...@gmail.com>wrote:
>>> 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
>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "RoboFab" group. >>> To post to this group, send email to robofab@googlegroups.com >>> To unsubscribe from this group, send email to >>> robofab-unsubscribe@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 robofab@googlegroups.com >> To unsubscribe from this group, send email to >> robofab-unsubscribe@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 robofab@googlegroups.com >> To unsubscribe from this group, send email to >> robofab-unsubscribe@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 robofab@googlegroups.com > To unsubscribe from this group, send email to > robofab-unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/robofab?hl=en
> -- > You received this message because you are subscribed to the Google Groups > "RoboFab" group. > To post to this group, send email to robofab@googlegroups.com > To unsubscribe from this group, send email to > robofab-unsubscribe@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
> 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 :)
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/
objectsBase.py", line 27, in <module>
from robofab.misc.arrayTools import updateBounds, pointInRect,
unionRect, sectRect
ImportError: No module named misc.arrayTools
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.
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.
> 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.
> 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?
