Which version of python is distributed with a new plucker release?
The reason I'm asking is that there have been some improvements in the web
libraries - and more are planned for 2.4. I'm trying to figure out what
baseline I can work with, and what I have to override, just in case. I do
not
I think I'm going to add VFS font support. A full anti-aliased font package
can be enormous. It should be pretty easy to add the support. Any
thoughts?
--
Dr. Alexander R. Pruss
Department of Philosophy
Georgetown University
Washington, DC 20057-1133 U.S.A.
e-mail: [EMAIL PROTECTED]
online
Alexander R. Pruss wrote:
I think I'm going to add VFS font support. A full anti-aliased font package
can be enormous. It should be pretty easy to add the support. Any
thoughts?
--
Sounds like a good idea, if compactness can be done. I put some aa fonts
on my T|T device this past week.
Hi Jim,
I can help provide some info about Python versions.
There is no python distributed with either the Mac OSX nor Linux
distributions.
As of Mac OS X version 10.2 (Jaguar), OS X ships with python as part of
the OS. It is python version 2.2, and IIRC is customized to work fast on
that
What happened to the web site?
Are the servers down, or moved?
Thanks
___
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
As of Mac OS X version 10.2 (Jaguar), OS X ships with python as part of
the OS. It is python version 2.2, and IIRC is customized to work fast on
that OS.
As of Mac OS X 10.3 (Panther) it's Python 2.3.
Bill
___
plucker-dev mailing list
[EMAIL
Seems to be back up.
At 09:11 AM 4/12/2003, John Pywtorak wrote:
What happened to the web site?
___
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Here are some thoughts. Scanning for fonts on VFS is time consuming. One
could do it with no real extra time penalty, however, if one did it at the
same time as scanning VFS for Plucker documents. But such scanning doesn't
always happen--it only happens when one is in the library, and not
On Wed, Dec 03, 2003, Alexander R. Pruss wrote:
thing I could do is additionally store in the prefs a small cache
of the pathnames and volumeRefs of the last three,
I don't think it's a good idea to store the volumeRefs; it's safer
to store the volume label and then get the volumeRef using
