pyx-devel — PyX development

Re: [PyX-devel] Re: [PyX-checkins] pyx/test/experimental brace.py,NONE,1.1

[Andre W. <wo...@us...>]

Hi,

On 31.08.05, Michael Schindler wrote:
> This is worth to be considered. But the geometry elements like line,
> circle, rect,... are far more basic than a brace. A brace makes no
> sense to me without aligning things to it. We have a similar problem
> as with the boxes and the connectors:
> 
> Two points + orientation sign are sufficient to orient a brace.
> Next, the brace yields one point + orientation vector for aligning
> something to the brace (some text, some connectors, another brace?)
> It should also be possible to align a brace the other way round:
> one point + orientation vector --> Two points + orientation sign

Well, isn't this whole discussion about *using* braces for example as
decorators to lines or connectors between boxes.

> The boxes, when I have understood André right, should orient
> themselves relative to other boxes, too. Their orientation relative to
> one point + orientation vector is already there.
> 
> The connectors, on the other hand, need more information than just
> points. They only work if they also have some distance information
> (for cuts at their ends), so I have chosen boxes (point + outline
> path) to be the alignment base for the connectors.
> 
> So, when introducing braces in a geometry package we certainly should
> derive them from a class that can align (boxes?)
> 
> When seen from their path capability the braces are rather like
> decorators. One decorates something (a path, a box, ...) with a brace,
> similar to the arrow heads.

Basically braces are decorators for me. But they can decorate straight
lines only. They could also be used to decorate connection lines
between boxes. Something like this ... but I'm not sure. However, a
brace decorator would basically place some text (or different canvas,
say a box) as a description text (or whatever). There might be cases,
where you want to use braces directly without constructing a
connection line to be decorated. I'm not that sure either, but I think
so.

> > Btw, André, if we are about to split path anyway (in order to separate
> > normpath out), we could also think about doing things like this at the
> > same time.
> 
> What is then to remain in path? Only the pathels?

The pathel's, the path itself and the helper functions to deal with
arcs (conversion to beziers etc.). Overall its more than 1000 lines
and thats enough to make this part its own module. The normpath is
again more than 1000 lines. From the numbers alone splitting seems
natural.

Splitting of the paths (circle, rect, etc. seems natural), when we
deside to allow for complicated path creators like the braces. As I
said, its kind of 


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/

Re: [PyX-devel] Re: [PyX-checkins] pyx/test/experimental brace.py,NONE,1.1

[Michael S. <m-s...@us...>]

Hello Jörg,

On 31.08.05, Joerg Lehmann wrote:
> On 31.08.05, Michael Schindler wrote:

> Looks amazing! But obviously, we do not yet have a place where one could
> put such stuff. Maybe it would maybe be more clear if brace were a path
> instead of having a path() method.

Oh, this can easily be changed -- it is of no importance.

> We could then create a new package
> (for instance "paths", but I'm sure there is a better name, "elements"
> also came to my mind) which contains only modules generating paths. In
> principle, already a simple circle or a line would belong there, but I'm
> not sure whether we want something like:
> 
>         paths.circle.circle(1, 2, 3)
>         paths.line.line(1, 2, 3, 4)
> 

>         paths.circle(1, 2, 3)
>         paths.line(1, 2, 3, 4)
> 
> Actually, I think this is not too bad, is it?

This is worth to be considered. But the geometry elements like line,
circle, rect,... are far more basic than a brace. A brace makes no
sense to me without aligning things to it. We have a similar problem
as with the boxes and the connectors:

Two points + orientation sign are sufficient to orient a brace.
Next, the brace yields one point + orientation vector for aligning
something to the brace (some text, some connectors, another brace?)
It should also be possible to align a brace the other way round:
one point + orientation vector --> Two points + orientation sign

The boxes, when I have understood André right, should orient
themselves relative to other boxes, too. Their orientation relative to
one point + orientation vector is already there.

The connectors, on the other hand, need more information than just
points. They only work if they also have some distance information
(for cuts at their ends), so I have chosen boxes (point + outline
path) to be the alignment base for the connectors.

So, when introducing braces in a geometry package we certainly should
derive them from a class that can align (boxes?)

When seen from their path capability the braces are rather like
decorators. One decorates something (a path, a box, ...) with a brace,
similar to the arrow heads.

> Btw, André, if we are about to split path anyway (in order to separate
> normpath out), we could also think about doing things like this at the
> same time.

What is then to remain in path? Only the pathels?

Michael.

-- 
"A mathematician is a device for turning coffee into theorems"
  Paul Erdös.

Re: [PyX-devel] Re: [PyX-checkins] pyx/test/experimental brace.py,NONE,1.1

[Andre W. <wo...@us...>]

Hi,

On 31.08.05, Joerg Lehmann wrote:
> On 31.08.05, Michael Schindler wrote:
> > Update of /cvsroot/pyx/pyx/test/experimental
> > In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28316
> > 
> > Added Files:
> > 	brace.py 
> > Log Message:
> > braces that look good even when drawn huge -- but where to put them?
> 
> Looks amazing! But obviously, we do not yet have a place where one could
> put such stuff. Maybe it would maybe be more clear if brace were a path
> instead of having a path() method.

That's an interesting idea. Get's a +1 from me.

I was always thinking about braces to be somehow related to connectors
and/or decorators. But neigher connectors nor decorators fit very
well. Instead, in the first, they are path "constructors". A
brace-function seems absolutely natural. I have to repeat myself: +1

> We could then create a new package
> (for instance "paths", but I'm sure there is a better name, "elements"
> also came to my mind) which contains only modules generating paths. In
> principle, already a simple circle or a line would belong there, but I'm
> not sure whether we want something like:
> 
>         paths.circle.circle(1, 2, 3)
>         paths.line.line(1, 2, 3, 4)
> 
> One could also think about grouping stuff together
> 
>         paths.basic.circle(1, 2, 3)
>         paths.basic.line(1, 2, 3, 4)
> 
> Then we could also say that all stuff from the basic package is so
> important that we inject it in the paths namespace:
> 
>         paths.circle(1, 2, 3)
>         paths.line(1, 2, 3, 4)
> 
> Actually, I think this is not too bad, is it?

Interesting. But it looks a bit overdesigned. Should paths become a
subdirectory? How is this subdirectory related to the path (normpath)
module(s)? Do we except such a huge number of path creating functions
having that much code? Get's something like a -0.5 from me ...

I would suggest to split the path module into path, paths and
normpath (the later is quite unimportant to the user, it should not
even be imported by "from pyx import *").

> Btw, André, if we are about to split path anyway (in order to separate
> normpath out), we could also think about doing things like this at the
> same time.

BTW I've already started to rework the pathitem signature. It seems to
work very well and leads to very clean and readable code (overall it
becomes less code and faster code as well). However, I'm not yet
finished (pdf is not working ... I want to allow for epsilon=None to
be used in that case), but I guess I can easily finish it tonight.
It's not really related to this discussion, but I could easily split
of the normpath (a regular user should not even notice this) ... and
create a paths module at the very same time. Do we already have a
consensus (otherwise this splitting can wait ... as I said, its not
really related).

> Adding some backwards compatibility code which issues a
> warning would be rather simple.

Right, we definitely should do that.


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/

[PyX-devel] Re: [PyX-checkins] pyx/test/experimental brace.py,NONE,1.1

[Joerg L. <jo...@us...>]

Hi Michael!

On 31.08.05, Michael Schindler wrote:
> Update of /cvsroot/pyx/pyx/test/experimental
> In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28316
> 
> Added Files:
> 	brace.py 
> Log Message:
> braces that look good even when drawn huge -- but where to put them?

Looks amazing! But obviously, we do not yet have a place where one could
put such stuff. Maybe it would maybe be more clear if brace were a path
instead of having a path() method. We could then create a new package
(for instance "paths", but I'm sure there is a better name, "elements"
also came to my mind) which contains only modules generating paths. In
principle, already a simple circle or a line would belong there, but I'm
not sure whether we want something like:

        paths.circle.circle(1, 2, 3)
        paths.line.line(1, 2, 3, 4)

One could also think about grouping stuff together

        paths.basic.circle(1, 2, 3)
        paths.basic.line(1, 2, 3, 4)

Then we could also say that all stuff from the basic package is so
important that we inject it in the paths namespace:

        paths.circle(1, 2, 3)
        paths.line(1, 2, 3, 4)

Actually, I think this is not too bad, is it?

Btw, André, if we are about to split path anyway (in order to separate
normpath out), we could also think about doing things like this at the
same time. Adding some backwards compatibility code which issues a
warning would be rather simple.

        Jörg

[PyX-devel] Re: [PyX-checkins] pyx/pyx pdfwriter.py,1.46,1.47

[Andre W. <wo...@us...>]

Hi Jörg,

On 25.08.05, Jörg Lehmann wrote:
>   
>       def __init__(self, type, _id=None, pageresource=None, pageprocset=None):
> +         """create a PDFobject
> +           - type has to be a string describing the type of the object
> +           - _id is a unique identification used for the object if it is not None.
> +             Otherwise id(self) is used
> +           - If pageresource is not None, it has to be a string describing the name
> +             of the resource to be included in the resource dictionary of the pages
> +             including the PDFobject.
> +           - If pageprocset is not None, it has to be a string describing the name 
> +             to be used in the ProcSet list of the pages including the PDFObject.
> +         """
>           self.type = type
>           if _id is None:

Genau. Wobei procset's eigentlich sowieso schon deprecated sind und
nur noch aus Kompatibilitätsgründen mitgeführt werden ...


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/

[PyX-devel] transparency

[Mladen B. <wt...@ma...>]

Thanks Andre, that's exactly what I was looking for! Perhaps the code
can be included in the next version of pyx?

Mladen

Re: [PyX-devel] transparency

[Andre W. <wo...@us...>]

Hi,

On 17.08.05, Mladen Bestvina wrote:
> Would it be possible to add a transparency option to the fill method? I
> understand that postscript does not allow transparency but pdf does.
> What I mean is that after a transparent fill the region below is
> partially visible.

Well, as far as I can see all we need to do is to modify the graphic
state, which contain several transparency features in PDF.
Unfortunately there are no PDF operators to modify those features
directly. Hence you need to create a ExtGState resource and use the gs
operator to set the feature. (The gs operator works on resources only,
you can't embed the graphic state dictionary directly into the content
stream.)

Since the page need to know about the new resources to be written, we
have to overwrite it's output method. For the future we should change
that ... just make it a feature of the resource, that it knows whether
and how it needs to be inserted into a PDFpage output. (I do have
other things in mind -- about forms -- where we'll need that too.)

Still, it's not that worse as it sounds. You can do transparency as
demonstrated in the enclosed code ... ;-)


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/

[PyX-devel] transparency

[Mladen B. <wt...@ma...>]

Hi,

Would it be possible to add a transparency option to the fill method? I
understand that postscript does not allow transparency but pdf does.
What I mean is that after a transparent fill the region below is
partially visible.

Thanks,
Mladen

[PyX-devel] ANN: PyX 0.8.1 released

[Andre W. <wo...@us...>]

Hi,

I've just uploaded PyX 0.8.1, which focus on bug fixing. Thanks to our
users for helping us improving our releases. The release notes are:

This release fixes some bugs in the path module and the output of
decorated paths. The fallback for kpathsea was considerably improved
in speed (it was unintensionally slowed down in 0.8). The inclusion of
the bounding box information in PS and PDF files is now optional. It
is suppressed by default when a paperformat is specified. A new path
example completes the release.

Enjoy,


Jörg, André, Michael, and Gert


------

CHANGES:

0.8.1 (2005/08/13):
  - deco module:
    - fix bug in postscript deco code for stroking only attributes
  - path module:
    - fix multicurveto._normalized
    - fix path.paramtoarclen and path.paramtoarclen_pt 
    - remove unused method-local function
    - fix linestyle rellength in PostScript
    - correction to the rounding problems in circles (reported by Uwe Fabricius)
  - epsfile module:
    - fix a typo
  - pattern module:
    - issue a warning when not using a stroke color for patterns
  - text module:
    - postpone PDFfontdescriptor information, since it raises an error on certain
      fonts even when PostScript output was requested (reported by Gert Ingold)
    - remove spurious spaces when checking for empty texmessages
  - kpathsea module:
    - caching in fallback to lower system call bottleneck
  - canvas module:
    - add missing writePSfile wrapper
    - add *args to writeEPSfile and writePDFfile wrappers
  - writer modules:
    - writebbox option to write bbox information (disabled by default)
      even when a paper format is specified (PS and PDF writers only)
  - use arclen in spring example
  - add knot example
  - use pdf graphic files for pdf version of the manual
  - use PyX to create tipa fallbacks for FAQ
  - correct description regarding the manual in the README file


-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/

Re: [PyX-devel] Re: [PyX-checkins] pyx CHANGES,1.388,1.389

[Andre W. <wo...@us...>]

Hi,

On 27.07.05, Joerg Lehmann wrote:
> > Unfortunately there is a bad behaviour in this new version, that a PDF
> > file created with PyX, centered on a page (i.e. no paperformat given)
> > is clipped in ghostview to positive coordinates.
> 
> You probably mean gv - I would be surprise if you still had installed
> ghostview...

Sure.

> > It seems a bug in the
> > ghostview/ghostscript communication, since ghostscript does it
> > properly (it takes into account the negative MediaBox information,
> > which is not declared invalid in the PDF spec.). To get the old
> > behaviour, which works with ghostscript you have to specify a
> > paperformat and enable the writebbox option. Is this a reasonable
> > approach or should we discuss this again before 0.8.1 release?
> 
> It works with acroread, xpdf, kpdf, ghostscript, so I wouldn't be too
> concerned about that. Maybe one should report that bug though.

Ok. Lets keep it while we know that there is a problem in gv
displaying those files. I've written a bug report to the gv
maintainer.


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript figures with Python & TeX
 (_/ \_)_/\_/           visit http://pyx.sourceforge.net/

Re: [PyX-devel] Re: [PyX-checkins] pyx CHANGES,1.388,1.389

[Joerg L. <jo...@us...>]

Hi André!

On 27.07.05, Andre Wobst wrote:
> On 27.07.05, André Wobst wrote:
> >   - writer modules:
> >     - writebbox option to write bbox information (disabled by default)
> >       even when a paper format is specified (PS and PDF writers only)
> 
> I've just checked a change to not write bbox information in PS and PDF
> documents anymore when a paperformat is given (as it was requested by
> some folks). At the same time we do not have a default paperformat
> setting default as we introduced it in PyX 0.8 by accident.
> 
> Unfortunately there is a bad behaviour in this new version, that a PDF
> file created with PyX, centered on a page (i.e. no paperformat given)
> is clipped in ghostview to positive coordinates.

You probably mean gv - I would be surprise if you still had installed
ghostview...

> It seems a bug in the
> ghostview/ghostscript communication, since ghostscript does it
> properly (it takes into account the negative MediaBox information,
> which is not declared invalid in the PDF spec.). To get the old
> behaviour, which works with ghostscript you have to specify a
> paperformat and enable the writebbox option. Is this a reasonable
> approach or should we discuss this again before 0.8.1 release?

It works with acroread, xpdf, kpdf, ghostscript, so I wouldn't be too
concerned about that. Maybe one should report that bug though.

        Jörg

[PyX-devel] Re: [PyX-checkins] pyx CHANGES,1.388,1.389

[Andre W. <wo...@us...>]

Hi,

On 27.07.05, André Wobst wrote:
>   - writer modules:
>     - writebbox option to write bbox information (disabled by default)
>       even when a paper format is specified (PS and PDF writers only)

I've just checked a change to not write bbox information in PS and PDF
documents anymore when a paperformat is given (as it was requested by
some folks). At the same time we do not have a default paperformat
setting default as we introduced it in PyX 0.8 by accident.

Unfortunately there is a bad behaviour in this new version, that a PDF
file created with PyX, centered on a page (i.e. no paperformat given)
is clipped in ghostview to positive coordinates. It seems a bug in the
ghostview/ghostscript communication, since ghostscript does it
properly (it takes into account the negative MediaBox information,
which is not declared invalid in the PDF spec.). To get the old
behaviour, which works with ghostscript you have to specify a
paperformat and enable the writebbox option. Is this a reasonable
approach or should we discuss this again before 0.8.1 release?


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript figures with Python & TeX
 (_/ \_)_/\_/           visit http://pyx.sourceforge.net/

[PyX-devel] Your STERLING card has been reserved for you !

[<s-s...@ya...>]

<HTML>
<HEAD>
<TITLE>slider</TITLE>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html;
charset=3Diso-8859-1">
<style type=3D"text/css">
<!--
.style2 {font-family: Arial, Helvetica, sans-serif;	font-size: 10px;
}
.style4 {font-family: Arial, Helvetica, sans-serif; font-size: 10px;
}
-->
</style>
</HEAD>
<BODY BGCOLOR=3D#FFFFFF LEFTMARGIN=3D0 TOPMARGIN=3D0 MARGINWIDTH=3D0
MARGINHEIGHT=3D0>
<map name=3D"map0"><area
href=3D"https://instantvuecard.com/index.asp?masteraff=3D0739&aff=3D1"
target=3D"_blank" alt=3D"SterlingCard Application" shape=3D"rect"
coords=3D"0,0,615,345"></map>
<!-- ImageReady Slices (slider.psd) -->
<table width=3D"40%" border=3D"0" cellspacing=3D"0" cellpadding=3D"0">
<tr>
<td>
<table width=3D615 border=3D0 cellpadding=3D0 cellspacing=3D0>
<tr>
<td> <img
src=3D"https://esuperoffers.com/new/VUE/615x345/1/images/slider_01.gif"
width=3D615 height=3D49 alt=3D"" usemap=3D"#map0" border=3D"0"></td>
</tr>
<tr>
<td> <img
src=3D"https://esuperoffers.com/new/VUE/615x345/middle.gif" width=3D"615"
height=3D"162" usemap=3D"#map0" border=3D"0"></td>
</tr>
<tr>
<td> <img
src=3D"https://esuperoffers.com/new/VUE/615x345/1/images/slider_03.gif"
width=3D615 height=3D134 alt=3D"" usemap=3D"#map0" border=3D"0"></td>
</tr>
</table>
</td>
</tr>
<tr>
<td><span class=3D"style2">This Prepaid Visa&reg; Debit Card is
issued by Four Oaks Bank &amp; Trust Company, NC pursuant to a license by
Visa&reg; U.S.A., Inc.</span></td>
</tr>
<tr>
<td>
<p class=3D"bodycopy"><font face=3D"Arial, Helvetica, sans-serif"
size=3D"2">To
indicate that you would rather not be contacted, please print
out a copy
of the ad that you received and include it with your letter
to:</font></p>
<p class=3D"bodycopy"><FONT face=3D"Courier New, Courier, mono"
size=3D1>*The USA Patriot Act is a Federal Law that requires all financial
institutions to obtain, verify and record information that identifies each
person who opens an account. You will be asked to provide your name,
address, date of birth, and other information that will allow us to
identify you. You may also be asked to provide documentation as proof of
identification. "Everyone is Approved" and "No One is Turned Down" is
contingent upon successfully passing this mandatory identification
confirmation.<B><SPAN
style=3D"FONT-WEIGHT: bold"><o:p></o:p></SPAN></B></FONT></p>
<p><font size=3D"2" face=3D"Arial, Helvetica,
sans-serif"><b>VUE</b><br>
5301 Laurel Canyon, Suite 126<br>
North Hollywood, CA 91607</font></p>
<p><font size=3D"4" face=3D"Arial, Helvetica,
sans-serif">OR</font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><br>
Follow this <a
href=3D"https://debitcardtracking.com/unsubscribe/index.asp">link</a>
and it will direct you to your Email Preference page where you
will be
able to manage and control future correspondence and
ads.</font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif">&copy;
2004, All rights
reserved.</font></p>
</td>
</tr>
<tr><td class=3D"style4"><br>This message was sent on behalf of
Got-Money.net, 1484 Pollard Road #306, Los Gatos, CA 95032<br>
Got-Money.net is not responsible for third party offers and makes no
representations or warranties regarding them.<br>	  <a
href=3D"https://debitcardtracking.com/unsubscribe/index.asp">Click here
to
unsubscribe</a><br></td>  </tr>
</table>
<!-- End ImageReady Slices -->
</BODY>
</HTML>
  

[PyX-devel] ANN: PyX 0.8 released

[Joerg L. <jo...@us...>]

Hi,

after quite some time, we finally managed to prepare a new major release,
PyX 0.8. Many improvements and fixes are included (see the attached list of
changes), but there are a couple of highlights which should be mentioned
separately: PyX now supports PDF output and the generation of multi-page
PS/PDF documents. The internals of the path system have been cleaned up and its
external interface has been streamlined. The axis data handling of the graph
component has undergone a major revision.

Note that there are several changes in PyX's API which are are potentially
relevant for "average" PyX users:

- The paperformat argument of the writeEPSfile, writetofile, etc. methods of
  the canvas, accepts no longer a string (e.g. "A4"), but a paperformat
  instance (e.g. document.paperformat.A4). A backward compatibility layer has
  been added, which issues a deprecation warning. Note that the support for the
  old API will be removed in the next major revision of PyX.

- The graph.data.function class expects the function specification to be of the
  form "y(x)=x**2" (instead of "y=x**2"). Again, a backward compatibility layer
  has been added, which will be removed in the next major revision.

- There is a change in the argument handling of the path methods that expect a
  parameter specifying a position along the path: When a number/length is
  passed, it is now interpreted as an arc length. If you want to specify the
  position by a tuple (subpath index, internal parameter t), you have to
  construct a corresponding normpathparam instance (please consult the
  documentation for more details).

- The most notable change in the graph subsystem is that the axes dictionary of
  a graph instance now contains a composite datatype, which stores all
  axis-related information including positioning methods. Instead of code like
  "g.axispos['x2'].gridpath(0)" you now have to use "g.axis['x2'].gridpath(0)".
  You also need to use the composite axis information to create linked axis
  between graphs. 

- Bar and split axes have been unified, which necessitate some changes in their
  data handling. Nested bar axes now need to be constructed explicitly by
  nestedbar instances.

Finally, we remark that starting from this release PyX requires Python 2.1
or newer.

Enjoy,

    André, Jörg, and Michael

----

0.8 (2005/07/13):
  - changed requirements to python 2.1 or newer:
    - nested scopes are needed without fallback solution by the path module
      (at other places fallback solutions for missing nested scopes are missing as well)
    - use warning module for warnings
  - path module:
    - path parameters and argument handling
    - the arct to arc/arcn conversion (needed for bbox calculation and for conversion into
      normpath) has been fixed
  - document module: new
    - container classes for document and pages
    - document.paperformat class (strings are deprecated)
  - canvas module:
    - writeEPSfile wraps a canvas in a single page document and performs the output
  - bbox module:
    - add _pt methods
  - pdfwriter module:
    - completely rewritten: support for fonts and patterns has been added
  - pswriter module: new
    - separate PS output from canvas
    - new signature of outputPS methods: writer and context are passed as additional
      arguments
  - color module:
    - allow selection on zero range palette (reported by Francisco Borges, cf. bug #1116257)
  - prolog module: removed due to code reorganisation
  - graph modules:
    - modifications on __init__.py in graph and axis subdirectories to
      make "from pyx.graph import *" working as expected
    - graph styles:
      - addontop added to stackedbarpos
      - column -> columnname renaming where appropriate
      - histogram style added
    - graph data:
      - function needs explicit variable definition (implicit variable definition is deprecated)
      - column names are inherited by data.data() except when copy=0;
        unused columns are silently ignored now
      - dynamic function data on a logarithmic axis uses isinstance check now
        (although it removes the only (mis)use of axis.inverse, it is a
        temporary solution only)
    - graph key:
      - extend graph keys to allow for several columns
    - axis data handling refactoring:
      - introcuded an axis positioner (module graph.axis.positioner)
      - introduced anchoredaxis to make axis data and positioning local to a graph
      - linkedaxis is a special version of anchoredaxis and is generic
        (it uses the new linkpainter provided by an axis)
      - unification of split and bar axes;
        removed some black magic in baraxis in favor of a nestedbar axis
      - x linked to x2 etc. is now possible
      - axis.inverse was removed (the only place it was (mis)used was by a function)
    - graphxy:
      - allow to transform axis after layout
      - [xy]axisat arguments in the constructor to easily move [xy]-axes
        to a position defined the orthogonal axis
      - remove axispos (use the axis dictionary now, since it now contains
        anchored axis instances and those have shortcuts for the axis positioner
        methods)
  - dvifile:
    - tfm->dvi conversion rounding bugfix
    - fix parsing of empty strings ("") in fontmap files (reported by John Owens, bug #1218983)
  - text module:
    - support for halign of boxes and content of boxes (see halign example)
    - take units xscale into account in parbox
    - messageparser for replaced fontsizes: Warning -> implemented by texmessage.fontwarning
    - messageparser for size differences at the end: Warning not Exception -> implemented by texmessage.fontwarning
    - messageparser for overfull/underfull vbox/hbox: Warning not Exception -> implemented by texmessage.boxwarning
    - dvicopy flag removed
    - allow argument of set to be None
    - rename nomathmode and nophantom to clearmathmode and clearphantom
    - texmessagepattern for easy creation of simple TeX message parsers
    - allow long file names in file checking TeX message parsers
    - no newline removal to not disturbe TeX messages when reporting errors
    - reworked documentation to use the python documentation standards
  - style module:
    - linewidth is no longer a unit.length subclass but expects a such as first argument
  - epsfile module:
    - correct EOL handling while reading DSC's (reported by Markus Meyer)
  - pattern module: new
    - moved canvas.pattern to its own module together with the new PDFpattern class
    - add some default patterns: hatched and crosshatched
  - deformer module:
    - improve the smoothing deformer
    - add a parallel deformer
  - tex module:
    - the very old tex module finally got removed completely
  - contrib directory:
    - a simple converter from dvi to EPS/PS/PDF files (dviconvert.py) has been added
    - a simple imagine to EPS/PS/PDF converter (imgconvert.py) has been added
    - a simple dvitype.py has been added
  - update address of FSF all over the place

Re: [PyX-devel] Re: [PyX-checkins] pyx/pyx pdfwriter.py,1.28,1.29

[Andre W. <wo...@us...>]

On 27.06.05, Andre Wobst wrote:
> On 27.06.05, Jörg Lehmann wrote:
> > Modified Files:
> > 	pdfwriter.py 
> > Log Message:
> > give PDFcontentlength the id of their parents, such that they get merged whenever theire parents are merged
> 
> Ok, but I think this does not work that way, since the id's of the
> parents are different as well, aren't they? Do we have a real design
> problem here? Hmmm ....

FFI: solved in private communication.


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript figures with Python & TeX
 (_/ \_)_/\_/           visit http://pyx.sourceforge.net/

[PyX-devel] Re: [PyX-checkins] pyx/pyx pdfwriter.py,1.28,1.29

[Andre W. <wo...@us...>]

Hi Jörg,

On 27.06.05, Jörg Lehmann wrote:
> Modified Files:
> 	pdfwriter.py 
> Log Message:
> give PDFcontentlength the id of their parents, such that they get merged whenever theire parents are merged

Ok, but I think this does not work that way, since the id's of the
parents are different as well, aren't they? Do we have a real design
problem here? Hmmm ....


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript figures with Python & TeX
 (_/ \_)_/\_/           visit http://pyx.sourceforge.net/

Re: [PyX-devel] Smoothing patterns

[Joerg L. <jo...@us...>]

Hallo Michael,

On 22.06.05, Michael Schindler wrote:
> I remember that we had a discussion about smoothing patterns in PyX.
> I will need this for visualizing some Finite Elements -- what is the
> state of this development. What was the reason not to implement this
> feature?

I remember having had a look into this, but it seemed quite complicated
and there was no real need at that time. In particular, the sheer number
of different shading types would make an interface rather hard to
implement.

> I played around with it but with little success. What works
> is the "shfill" operator that fills a patch (triangle, deformed
> square...) with a shading but using this as a shading pattern (in
> terms of a ressource) and using the pattern later did not work.

You mean using it in a fill operation. If I understand the PLRM
correctly, this should work as any other colour/pattern. Maybe it's
a problem of the renderer?

> The documentation says something about LanguageLevel 3 but I cannot
> figure out if this applies to the whole shading/patterns.

I think this applies to the shading patterns but not to patterns per se.

> If I understand this right, we do write Level 3 Postscript?

Yes, we declare it so at the beginning of the file.

> And is shading implemented in PDF?

I don't know precisely but I would be surprised if this should not be
the case.

        Jörg

[PyX-devel] Smoothing patterns

[Michael S. <m-s...@us...>]

Hello André and Jörg,

I remember that we had a discussion about smoothing patterns in PyX.
I will need this for visualizing some Finite Elements -- what is the
state of this development. What was the reason not to implement this
feature?

I played around with it but with little success. What works
is the "shfill" operator that fills a patch (triangle, deformed
square...) with a shading but using this as a shading pattern (in
terms of a ressource) and using the pattern later did not work.

The documentation says something about LanguageLevel 3 but I cannot
figure out if this applies to the whole shading/patterns.
If I understand this right, we do write Level 3 Postscript?
And is shading implemented in PDF?


Michael.

-- 
"A mathematician is a device for turning coffee into theorems"
  Paul Erdös.

[PyX-devel] [ pyx-Bugs-1218983 ] compile error with graphs/minimal example?

[SourceForge.net <no...@so...>]

Bugs item #1218983, was opened at 2005-06-12 04:17
Message generated for change (Comment added) made by joergl
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=1218983&group_id=45430

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
Resolution: None
Priority: 5
Submitted By: John Owens (john_owens)
Assigned to: André Wobst (wobsta)
Summary: compile error with graphs/minimal example?

Initial Comment:
I'm trying to compile a PyX program (first time). I have one based on 
graphs/minimal:

#!/usr/bin/env python
from pyx import *

g = graph.graphxy(width=8)
g.plot(graph.data.file("historical-fp-performance.dat", x=1, y=2))
g.writeEPSfile("historical-fp-performance")

after running "python setup.py install" (I did enable the kpathsea 
build as well). This is on python 2.3.5 on OS X 10.4.1. I have tried 
this with both PyX 0.7.1 as well as the CVS version (trace below is 
for the CVS version). 

Error trace follows, then an error trace from "make" in the manual 
directory. Help?

Traceback (most recent call last):
  File "./historical-fp-performance.py", line 6, in ?
    g.writeEPSfile("historical-fp-performance")
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/canvas.py", line 364, in 
writeEPSfile
    document.document([document.page(self, 
**kwargs)]).writeEPSfile(filename)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/document.py", line 131, in 
writeEPSfile
    pswriter.epswriter(self, filename, *args, **kwargs)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/pswriter.py", line 237, in __init__
    bbox = canvas.bbox()
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/graph.py", line 445, in 
bbox
    self.finish()
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/graph.py", line 342, in 
finish
    self.domethods[0]()
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/graph.py", line 275, in 
dolayout
    self.axes[key].create(self.texrunner)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/axis/axis.py", line 518, in 
create
    self.canvas = self.axis.create(self.data, self.positioner, 
graphtexrunner, self.errorname)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/axis/axis.py", line 205, in 
create
    self.painter.paint(canvas, variants[0], self, positioner)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/axis/painter.py", line 189, 
in paint
    t.temp_labelbox = canvas.texrunner.text_pt(t.temp_x_pt, 
t.temp_y_pt, t.label, labelattrs)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/text.py", line 1171, in text_pt
    return self.text(x * unit.t_pt, y * unit.t_pt, expr, *args, **kwargs)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/text.py", line 1153, in text
    self.execute(expr, self.defaulttexmessagesdefaultrun + 
self.texmessagesdefaultrun + texmessages)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/text.py", line 851, in execute
    self.fontmap = dvifile.readfontmap(self.fontmaps.split())
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/dvifile.py", line 534, in 
readfontmap
    fm = fontmapping(line)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/dvifile.py", line 474, in __init__
    if token.startswith("<"):
AttributeError: 'NoneType' object has no attribute 'startswith'





john-owens-powerbook-g4-15:~/Documents/src/pyx/manual jowens
$ make
python -c "import sys;sys.path[:0]=[\..\];import pyx.version;print 
pyx.version.version+'%'" > pyxversion.tex
python -c "import sys;sys.path[:0]=[\..\];import pyx.version;print 
pyx.version.date+'%'" > pyxdate.tex
export PYTHONPATH=/Users/jowens/Documents/src/pyx/
manual/.. ; python arrows.py
Traceback (most recent call last):
  File "arrows.py", line 7, in ?
    text.preamble(r"\renewcommand{\familydefault}{\ttdefault}")
  File "/Users/jowens/Documents/src/pyx/pyx/text.py", line 1118, in 
preamble
    self.execute(expr, texmessages)
  File "/Users/jowens/Documents/src/pyx/pyx/text.py", line 851, in 
execute
    self.fontmap = dvifile.readfontmap(self.fontmaps.split())
  File "/Users/jowens/Documents/src/pyx/pyx/dvifile.py", line 534, in 
readfontmap
    fm = fontmapping(line)
  File "/Users/jowens/Documents/src/pyx/pyx/dvifile.py", line 474, in 
__init__
    if token.startswith("<"):
AttributeError: 'NoneType' object has no attribute 'startswith'
make: *** [arrows.eps] Error 1

----------------------------------------------------------------------

>Comment By: Jörg Lehmann (joergl)
Date: 2005-06-18 12:13

Message:
Logged In: YES 
user_id=390410

Thanks for the debugging output. The fontmapping files are
ok, the
problem was in PyX's parsing code. I've just checked in the
trivial fix.

----------------------------------------------------------------------

Comment By: John Owens (john_owens)
Date: 2005-06-17 21:43

Message:
Logged In: YES 
user_id=798340

Sure thing. Attached.
The entries in the map file are ones that are generated from the otftotfm 
tool in the LCDF TypeTools. If there are problems with how that tool 
generates map files, we should track that down (the author is good with 
updates when necessary).

john-owens-powerbook-g4-15:~/Documents/src/PyX-0.7.1/examples 
jowens$ python hello.py 
LY1-ACaslonPro-Bold-kern-liga--base ACaslonPro-Bold 
"AutoEnc_4v2jjxamia3nw3b2mzbmticwud ReEncodeFont" <[a_4v2jjx.enc 
<ACaslonPro-Bold.pfb
['LY1-ACaslonPro-Bold-kern-liga--base']
['LY1-ACaslonPro-Bold-kern-liga--base', 'ACaslonPro-Bold']
['LY1-ACaslonPro-Bold-kern-liga--base', 'ACaslonPro-Bold', 
'"AutoEnc_4v2jjxamia3nw3b2mzbmticwud ReEncodeFont"']
['LY1-ACaslonPro-Bold-kern-liga--base', 'ACaslonPro-Bold', 
'"AutoEnc_4v2jjxamia3nw3b2mzbmticwud ReEncodeFont"', '<
[a_4v2jjx.enc']
['LY1-ACaslonPro-Bold-kern-liga--base', 'ACaslonPro-Bold', 
'"AutoEnc_4v2jjxamia3nw3b2mzbmticwud ReEncodeFont"', '<
[a_4v2jjx.enc', '<ACaslonPro-Bold.pfb']
LY1-ACaslonPro-Bold-kern-liga--lcdfj ACaslonPro-BoldLCDFJ "" 
<ACaslonPro-BoldLCDFJ.pfb
['LY1-ACaslonPro-Bold-kern-liga--lcdfj']
['LY1-ACaslonPro-Bold-kern-liga--lcdfj', 'ACaslonPro-BoldLCDFJ']
['LY1-ACaslonPro-Bold-kern-liga--lcdfj', 'ACaslonPro-BoldLCDFJ', None]
['LY1-ACaslonPro-Bold-kern-liga--lcdfj', 'ACaslonPro-BoldLCDFJ', None, 
'<ACaslonPro-BoldLCDFJ.pfb']
Traceback (most recent call last):
  File "hello.py", line 4, in ?
    c.text(0, 0, "Hello, world!")
  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/site-packages/pyx/canvas.py", line 268, in text
    return self.insert(self.texrunner.text(x, y, atext, *args, **kwargs))
  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/site-packages/pyx/text.py", line 1153, in text
    self.execute(expr, self.defaulttexmessagesdefaultrun + 
self.texmessagesdefaultrun + texmessages)
  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/site-packages/pyx/text.py", line 851, in execute
    self.fontmap = dvifile.readfontmap(self.fontmaps.split())
  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/site-packages/pyx/dvifile.py", line 583, in readfontmap
    fm = fontmapping(line)
  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/site-packages/pyx/dvifile.py", line 523, in __init__
    if token.startswith("<"):
AttributeError: 'NoneType' object has no attribute 'startswith'


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2005-06-17 09:35

Message:
Logged In: YES 
user_id=405853

(I'm sorry for the late response. I'm right back from vacation. Could you 
please stick on the 0.7.1 release for our further discussion. The CVS is 
known to be partially broken (although I don't expect your problem to be 
related to that) and its easier to watch for tracebacks on released versions, 
where we can easily reproduce all line numbers in files and tracebacks 
etc.)

The problem you encounter seems to be related to our parsing routine of 
your "psfonts.map". I'm wondering for what case our parser emits a 
NoneType in the token list. Could you please insert a debugging print 
statement at the top of the constructor of the fontmapping class. At 
release 0.7.1 insert a line "print s" at line 499 in the file. Also add a "print 
tokens" right after the 517 and run your test again. You should be able to 
reproduce the problem already at the most simple TeX-using example, 
which is hello.py in the example directory.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=1218983&group_id=45430

[PyX-devel] [ pyx-Support Requests-1218983 ] compile error with graphs/minimal example?

[SourceForge.net <no...@so...>]

Support Requests item #1218983, was opened at 2005-06-11 19:17
Message generated for change (Comment added) made by john_owens
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442887&aid=1218983&group_id=45430

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: John Owens (john_owens)
Assigned to: André Wobst (wobsta)
Summary: compile error with graphs/minimal example?

Initial Comment:
I'm trying to compile a PyX program (first time). I have one based on 
graphs/minimal:

#!/usr/bin/env python
from pyx import *

g = graph.graphxy(width=8)
g.plot(graph.data.file("historical-fp-performance.dat", x=1, y=2))
g.writeEPSfile("historical-fp-performance")

after running "python setup.py install" (I did enable the kpathsea 
build as well). This is on python 2.3.5 on OS X 10.4.1. I have tried 
this with both PyX 0.7.1 as well as the CVS version (trace below is 
for the CVS version). 

Error trace follows, then an error trace from "make" in the manual 
directory. Help?

Traceback (most recent call last):
  File "./historical-fp-performance.py", line 6, in ?
    g.writeEPSfile("historical-fp-performance")
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/canvas.py", line 364, in 
writeEPSfile
    document.document([document.page(self, 
**kwargs)]).writeEPSfile(filename)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/document.py", line 131, in 
writeEPSfile
    pswriter.epswriter(self, filename, *args, **kwargs)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/pswriter.py", line 237, in __init__
    bbox = canvas.bbox()
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/graph.py", line 445, in 
bbox
    self.finish()
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/graph.py", line 342, in 
finish
    self.domethods[0]()
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/graph.py", line 275, in 
dolayout
    self.axes[key].create(self.texrunner)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/axis/axis.py", line 518, in 
create
    self.canvas = self.axis.create(self.data, self.positioner, 
graphtexrunner, self.errorname)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/axis/axis.py", line 205, in 
create
    self.painter.paint(canvas, variants[0], self, positioner)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/axis/painter.py", line 189, 
in paint
    t.temp_labelbox = canvas.texrunner.text_pt(t.temp_x_pt, 
t.temp_y_pt, t.label, labelattrs)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/text.py", line 1171, in text_pt
    return self.text(x * unit.t_pt, y * unit.t_pt, expr, *args, **kwargs)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/text.py", line 1153, in text
    self.execute(expr, self.defaulttexmessagesdefaultrun + 
self.texmessagesdefaultrun + texmessages)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/text.py", line 851, in execute
    self.fontmap = dvifile.readfontmap(self.fontmaps.split())
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/dvifile.py", line 534, in 
readfontmap
    fm = fontmapping(line)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/dvifile.py", line 474, in __init__
    if token.startswith("<"):
AttributeError: 'NoneType' object has no attribute 'startswith'





john-owens-powerbook-g4-15:~/Documents/src/pyx/manual jowens
$ make
python -c "import sys;sys.path[:0]=[\..\];import pyx.version;print 
pyx.version.version+'%'" > pyxversion.tex
python -c "import sys;sys.path[:0]=[\..\];import pyx.version;print 
pyx.version.date+'%'" > pyxdate.tex
export PYTHONPATH=/Users/jowens/Documents/src/pyx/
manual/.. ; python arrows.py
Traceback (most recent call last):
  File "arrows.py", line 7, in ?
    text.preamble(r"\renewcommand{\familydefault}{\ttdefault}")
  File "/Users/jowens/Documents/src/pyx/pyx/text.py", line 1118, in 
preamble
    self.execute(expr, texmessages)
  File "/Users/jowens/Documents/src/pyx/pyx/text.py", line 851, in 
execute
    self.fontmap = dvifile.readfontmap(self.fontmaps.split())
  File "/Users/jowens/Documents/src/pyx/pyx/dvifile.py", line 534, in 
readfontmap
    fm = fontmapping(line)
  File "/Users/jowens/Documents/src/pyx/pyx/dvifile.py", line 474, in 
__init__
    if token.startswith("<"):
AttributeError: 'NoneType' object has no attribute 'startswith'
make: *** [arrows.eps] Error 1

----------------------------------------------------------------------

>Comment By: John Owens (john_owens)
Date: 2005-06-17 12:43

Message:
Logged In: YES 
user_id=798340

Sure thing. Attached.
The entries in the map file are ones that are generated from the otftotfm 
tool in the LCDF TypeTools. If there are problems with how that tool 
generates map files, we should track that down (the author is good with 
updates when necessary).

john-owens-powerbook-g4-15:~/Documents/src/PyX-0.7.1/examples 
jowens$ python hello.py 
LY1-ACaslonPro-Bold-kern-liga--base ACaslonPro-Bold 
"AutoEnc_4v2jjxamia3nw3b2mzbmticwud ReEncodeFont" <[a_4v2jjx.enc 
<ACaslonPro-Bold.pfb
['LY1-ACaslonPro-Bold-kern-liga--base']
['LY1-ACaslonPro-Bold-kern-liga--base', 'ACaslonPro-Bold']
['LY1-ACaslonPro-Bold-kern-liga--base', 'ACaslonPro-Bold', 
'"AutoEnc_4v2jjxamia3nw3b2mzbmticwud ReEncodeFont"']
['LY1-ACaslonPro-Bold-kern-liga--base', 'ACaslonPro-Bold', 
'"AutoEnc_4v2jjxamia3nw3b2mzbmticwud ReEncodeFont"', '<
[a_4v2jjx.enc']
['LY1-ACaslonPro-Bold-kern-liga--base', 'ACaslonPro-Bold', 
'"AutoEnc_4v2jjxamia3nw3b2mzbmticwud ReEncodeFont"', '<
[a_4v2jjx.enc', '<ACaslonPro-Bold.pfb']
LY1-ACaslonPro-Bold-kern-liga--lcdfj ACaslonPro-BoldLCDFJ "" 
<ACaslonPro-BoldLCDFJ.pfb
['LY1-ACaslonPro-Bold-kern-liga--lcdfj']
['LY1-ACaslonPro-Bold-kern-liga--lcdfj', 'ACaslonPro-BoldLCDFJ']
['LY1-ACaslonPro-Bold-kern-liga--lcdfj', 'ACaslonPro-BoldLCDFJ', None]
['LY1-ACaslonPro-Bold-kern-liga--lcdfj', 'ACaslonPro-BoldLCDFJ', None, 
'<ACaslonPro-BoldLCDFJ.pfb']
Traceback (most recent call last):
  File "hello.py", line 4, in ?
    c.text(0, 0, "Hello, world!")
  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/site-packages/pyx/canvas.py", line 268, in text
    return self.insert(self.texrunner.text(x, y, atext, *args, **kwargs))
  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/site-packages/pyx/text.py", line 1153, in text
    self.execute(expr, self.defaulttexmessagesdefaultrun + 
self.texmessagesdefaultrun + texmessages)
  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/site-packages/pyx/text.py", line 851, in execute
    self.fontmap = dvifile.readfontmap(self.fontmaps.split())
  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/site-packages/pyx/dvifile.py", line 583, in readfontmap
    fm = fontmapping(line)
  File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/site-packages/pyx/dvifile.py", line 523, in __init__
    if token.startswith("<"):
AttributeError: 'NoneType' object has no attribute 'startswith'


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2005-06-17 00:35

Message:
Logged In: YES 
user_id=405853

(I'm sorry for the late response. I'm right back from vacation. Could you 
please stick on the 0.7.1 release for our further discussion. The CVS is 
known to be partially broken (although I don't expect your problem to be 
related to that) and its easier to watch for tracebacks on released versions, 
where we can easily reproduce all line numbers in files and tracebacks 
etc.)

The problem you encounter seems to be related to our parsing routine of 
your "psfonts.map". I'm wondering for what case our parser emits a 
NoneType in the token list. Could you please insert a debugging print 
statement at the top of the constructor of the fontmapping class. At 
release 0.7.1 insert a line "print s" at line 499 in the file. Also add a "print 
tokens" right after the 517 and run your test again. You should be able to 
reproduce the problem already at the most simple TeX-using example, 
which is hello.py in the example directory.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442887&aid=1218983&group_id=45430

[PyX-devel] [ pyx-Support Requests-1218983 ] compile error with graphs/minimal example?

[SourceForge.net <no...@so...>]

Support Requests item #1218983, was opened at 2005-06-12 04:17
Message generated for change (Comment added) made by wobsta
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442887&aid=1218983&group_id=45430

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: John Owens (john_owens)
>Assigned to: André Wobst (wobsta)
Summary: compile error with graphs/minimal example?

Initial Comment:
I'm trying to compile a PyX program (first time). I have one based on 
graphs/minimal:

#!/usr/bin/env python
from pyx import *

g = graph.graphxy(width=8)
g.plot(graph.data.file("historical-fp-performance.dat", x=1, y=2))
g.writeEPSfile("historical-fp-performance")

after running "python setup.py install" (I did enable the kpathsea 
build as well). This is on python 2.3.5 on OS X 10.4.1. I have tried 
this with both PyX 0.7.1 as well as the CVS version (trace below is 
for the CVS version). 

Error trace follows, then an error trace from "make" in the manual 
directory. Help?

Traceback (most recent call last):
  File "./historical-fp-performance.py", line 6, in ?
    g.writeEPSfile("historical-fp-performance")
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/canvas.py", line 364, in 
writeEPSfile
    document.document([document.page(self, 
**kwargs)]).writeEPSfile(filename)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/document.py", line 131, in 
writeEPSfile
    pswriter.epswriter(self, filename, *args, **kwargs)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/pswriter.py", line 237, in __init__
    bbox = canvas.bbox()
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/graph.py", line 445, in 
bbox
    self.finish()
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/graph.py", line 342, in 
finish
    self.domethods[0]()
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/graph.py", line 275, in 
dolayout
    self.axes[key].create(self.texrunner)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/axis/axis.py", line 518, in 
create
    self.canvas = self.axis.create(self.data, self.positioner, 
graphtexrunner, self.errorname)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/axis/axis.py", line 205, in 
create
    self.painter.paint(canvas, variants[0], self, positioner)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/axis/painter.py", line 189, 
in paint
    t.temp_labelbox = canvas.texrunner.text_pt(t.temp_x_pt, 
t.temp_y_pt, t.label, labelattrs)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/text.py", line 1171, in text_pt
    return self.text(x * unit.t_pt, y * unit.t_pt, expr, *args, **kwargs)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/text.py", line 1153, in text
    self.execute(expr, self.defaulttexmessagesdefaultrun + 
self.texmessagesdefaultrun + texmessages)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/text.py", line 851, in execute
    self.fontmap = dvifile.readfontmap(self.fontmaps.split())
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/dvifile.py", line 534, in 
readfontmap
    fm = fontmapping(line)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/dvifile.py", line 474, in __init__
    if token.startswith("<"):
AttributeError: 'NoneType' object has no attribute 'startswith'





john-owens-powerbook-g4-15:~/Documents/src/pyx/manual jowens
$ make
python -c "import sys;sys.path[:0]=[\..\];import pyx.version;print 
pyx.version.version+'%'" > pyxversion.tex
python -c "import sys;sys.path[:0]=[\..\];import pyx.version;print 
pyx.version.date+'%'" > pyxdate.tex
export PYTHONPATH=/Users/jowens/Documents/src/pyx/
manual/.. ; python arrows.py
Traceback (most recent call last):
  File "arrows.py", line 7, in ?
    text.preamble(r"\renewcommand{\familydefault}{\ttdefault}")
  File "/Users/jowens/Documents/src/pyx/pyx/text.py", line 1118, in 
preamble
    self.execute(expr, texmessages)
  File "/Users/jowens/Documents/src/pyx/pyx/text.py", line 851, in 
execute
    self.fontmap = dvifile.readfontmap(self.fontmaps.split())
  File "/Users/jowens/Documents/src/pyx/pyx/dvifile.py", line 534, in 
readfontmap
    fm = fontmapping(line)
  File "/Users/jowens/Documents/src/pyx/pyx/dvifile.py", line 474, in 
__init__
    if token.startswith("<"):
AttributeError: 'NoneType' object has no attribute 'startswith'
make: *** [arrows.eps] Error 1

----------------------------------------------------------------------

>Comment By: André Wobst (wobsta)
Date: 2005-06-17 09:35

Message:
Logged In: YES 
user_id=405853

(I'm sorry for the late response. I'm right back from vacation. Could you 
please stick on the 0.7.1 release for our further discussion. The CVS is 
known to be partially broken (although I don't expect your problem to be 
related to that) and its easier to watch for tracebacks on released versions, 
where we can easily reproduce all line numbers in files and tracebacks 
etc.)

The problem you encounter seems to be related to our parsing routine of 
your "psfonts.map". I'm wondering for what case our parser emits a 
NoneType in the token list. Could you please insert a debugging print 
statement at the top of the constructor of the fontmapping class. At 
release 0.7.1 insert a line "print s" at line 499 in the file. Also add a "print 
tokens" right after the 517 and run your test again. You should be able to 
reproduce the problem already at the most simple TeX-using example, 
which is hello.py in the example directory.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442887&aid=1218983&group_id=45430

[PyX-devel] [ pyx-Support Requests-1218983 ] compile error with graphs/minimal example?

[SourceForge.net <no...@so...>]

Support Requests item #1218983, was opened at 2005-06-11 19:17
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442887&aid=1218983&group_id=45430

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: John Owens (john_owens)
Assigned to: Nobody/Anonymous (nobody)
Summary: compile error with graphs/minimal example?

Initial Comment:
I'm trying to compile a PyX program (first time). I have one based on 
graphs/minimal:

#!/usr/bin/env python
from pyx import *

g = graph.graphxy(width=8)
g.plot(graph.data.file("historical-fp-performance.dat", x=1, y=2))
g.writeEPSfile("historical-fp-performance")

after running "python setup.py install" (I did enable the kpathsea 
build as well). This is on python 2.3.5 on OS X 10.4.1. I have tried 
this with both PyX 0.7.1 as well as the CVS version (trace below is 
for the CVS version). 

Error trace follows, then an error trace from "make" in the manual 
directory. Help?

Traceback (most recent call last):
  File "./historical-fp-performance.py", line 6, in ?
    g.writeEPSfile("historical-fp-performance")
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/canvas.py", line 364, in 
writeEPSfile
    document.document([document.page(self, 
**kwargs)]).writeEPSfile(filename)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/document.py", line 131, in 
writeEPSfile
    pswriter.epswriter(self, filename, *args, **kwargs)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/pswriter.py", line 237, in __init__
    bbox = canvas.bbox()
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/graph.py", line 445, in 
bbox
    self.finish()
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/graph.py", line 342, in 
finish
    self.domethods[0]()
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/graph.py", line 275, in 
dolayout
    self.axes[key].create(self.texrunner)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/axis/axis.py", line 518, in 
create
    self.canvas = self.axis.create(self.data, self.positioner, 
graphtexrunner, self.errorname)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/axis/axis.py", line 205, in 
create
    self.painter.paint(canvas, variants[0], self, positioner)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/graph/axis/painter.py", line 189, 
in paint
    t.temp_labelbox = canvas.texrunner.text_pt(t.temp_x_pt, 
t.temp_y_pt, t.label, labelattrs)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/text.py", line 1171, in text_pt
    return self.text(x * unit.t_pt, y * unit.t_pt, expr, *args, **kwargs)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/text.py", line 1153, in text
    self.execute(expr, self.defaulttexmessagesdefaultrun + 
self.texmessagesdefaultrun + texmessages)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/text.py", line 851, in execute
    self.fontmap = dvifile.readfontmap(self.fontmaps.split())
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/dvifile.py", line 534, in 
readfontmap
    fm = fontmapping(line)
  File "/System/Library/Frameworks/Python.framework/Versions/
2.3/lib/python2.3/site-packages/pyx/dvifile.py", line 474, in __init__
    if token.startswith("<"):
AttributeError: 'NoneType' object has no attribute 'startswith'





john-owens-powerbook-g4-15:~/Documents/src/pyx/manual jowens
$ make
python -c "import sys;sys.path[:0]=[\..\];import pyx.version;print 
pyx.version.version+'%'" > pyxversion.tex
python -c "import sys;sys.path[:0]=[\..\];import pyx.version;print 
pyx.version.date+'%'" > pyxdate.tex
export PYTHONPATH=/Users/jowens/Documents/src/pyx/
manual/.. ; python arrows.py
Traceback (most recent call last):
  File "arrows.py", line 7, in ?
    text.preamble(r"\renewcommand{\familydefault}{\ttdefault}")
  File "/Users/jowens/Documents/src/pyx/pyx/text.py", line 1118, in 
preamble
    self.execute(expr, texmessages)
  File "/Users/jowens/Documents/src/pyx/pyx/text.py", line 851, in 
execute
    self.fontmap = dvifile.readfontmap(self.fontmaps.split())
  File "/Users/jowens/Documents/src/pyx/pyx/dvifile.py", line 534, in 
readfontmap
    fm = fontmapping(line)
  File "/Users/jowens/Documents/src/pyx/pyx/dvifile.py", line 474, in 
__init__
    if token.startswith("<"):
AttributeError: 'NoneType' object has no attribute 'startswith'
make: *** [arrows.eps] Error 1

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442887&aid=1218983&group_id=45430

[PyX-devel] teTeX 3.0

[Michael S. <m-s...@us...>]

Hello,

I just tested cvs-PyX together with a self-compiled teTeX-3.0 and found no
errors. Here is what I have tested:

I compiled the pykpathsea, linked it with the teTeX-3.0 kpathsea
library (compiled on debian woody with the ordinary gcc).
The library can find the font files listed in
  * the global tex-trees: psfonts.map
  * the private tex-trees: psfonts.map
  * the private tex-trees: myown.map

The same holds if I use the workaround without compiling the
pykpathsea.

Also the t1strip compiles cleanly. However, there is one caveat: latex
now uses pdfetex instead of tex, even for dvi output. There is some
code in writet1.c especially written for pdftex -- I do not see if
this has any implications on the working of the font-mechanism.

Michael.

-- 
"A mathematician is a device for turning coffee into theorems"
  Paul Erdös.

[PyX-devel] [ pyx-Bugs-1180691 ] incomplete example in ref manual

[SourceForge.net <no...@so...>]

Bugs item #1180691, was opened at 2005-04-11 14:54
Message generated for change (Settings changed) made by wobsta
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=1180691&group_id=45430

Category: None
Group: None
>Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Ralf Utermann (ralfu)
Assigned to: Nobody/Anonymous (nobody)
Summary: incomplete example in ref manual 

Initial Comment:
Reference manual 0.7.1, chapter  2.1:

The definition of 'rect2' is missing the
final 'path.lineto(0, 0)'


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2005-04-11 17:12

Message:
Logged In: YES 
user_id=405853

Right! Fixed in CVS. Thanks for the report!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=1180691&group_id=45430

[PyX-devel] [ pyx-Bugs-1180691 ] incomplete example in ref manual

[SourceForge.net <no...@so...>]

Bugs item #1180691, was opened at 2005-04-11 14:54
Message generated for change (Settings changed) made by wobsta
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=1180691&group_id=45430

Category: None
Group: None
Status: Open
>Resolution: Fixed
Priority: 5
Submitted By: Ralf Utermann (ralfu)
Assigned to: Nobody/Anonymous (nobody)
Summary: incomplete example in ref manual 

Initial Comment:
Reference manual 0.7.1, chapter  2.1:

The definition of 'rect2' is missing the
final 'path.lineto(0, 0)'


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2005-04-11 17:12

Message:
Logged In: YES 
user_id=405853

Right! Fixed in CVS. Thanks for the report!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=1180691&group_id=45430