Michael Hipp wrote, at 23.08.2007 16:03:
> Hello, just "discovered" PythonReports. Looks good. Well thought out.
thank you.
> Question #1: What is the project status? Is it alive and well?
i think so.
i don't use PythonReports myself just now, but as far as i know my other
colleagues do, and i didn't get any problem reports since last release.
> Question #2: Is this fixable? (from wxPrint.py)
>
> """wxPython print classes
>
> Warning: this module is malfunctional. Print preview is badly broken
> due to wxDC limitations. Printer output may be broken too.
>
> """
>
> Or is it a a limitation of wxWidgets/MSW that can't be overcome?
i cannot find the solution, if there is any. i don't think the fix is
possible at the python side, but i don't want to be categorical about it.
the problem with print preview is that the relative size of the text
strings varies with zoom level change. i heard that someone worked
around it by disabling the zoom, but, of course, that is not a solution.
the problem is not specific to the windows platform; wxGTK acts in the
same way.
besides, the bar code rendering is badly broken. the display is quite
astounding, and i have absolutely no idea what's happening. i have
tried several different approaches to work around that (including
Blit()ing of a correct bitmap to the output DC), but none of them
resulted in satisfactory output.
> Question #3: Are contributions from outsiders welcome?
yes. contributions to either project design, the code, or - especially
- the documentation are welcome. warn you, however, that the patches
are probable to be edited before applying.
best wishes,
alex.
|
