Re: [Plplot-devel] Plplot embedded in pyqt + plimage function

[Alan W. I. <ir...@be...>]

Hello Alessandro:

Thanks very much for this interesting contribution.  There has been some
debate here (perhaps that is an understatement) about how to obtain a widget
under python, and apparently you have managed to do it under pyqt.  So I am
most interested in what you have done, but I am going to need some
additional help from you to get this working on my system because I am still
in the middle of learning python, and I have never tried pyqt (although I
saw a recent book about it that was downloadable from the web).

So will you please do the following to help me get started:

(1) Get your changes working with the latest plplot from cvs.  The current
plplot is almost as stable as 5.0.4, a fair amount of new functionality has
been added, and I don't have time right now to try to understand your
changes in enough detail to port them (where necessary) to the latest
plplot. Note to obtain the latest plplot from CVS, follow the anonymous cvs
access directions at http://sourceforge.net/cvs/?group_id=2915.  The
modulename is plplot.  So the last direction translates to

cvs -z3 \
-d:pserver:ano...@cv...:/cvsroot/plplot \
checkout plplot

This will create a directory plplot, and fill it with the directory tree
corresponding to the latest plplot.

(2) Make a clean recursive patch of your changes once you have got them to
work with the latest plplot.  (I looked at the organization of your recent
patch, and I would like to see some changes to that organization.) There are
many ways to do a clean recursive patch, but here is what I recommend:

cp the latest plplot tree that you just downloaded from cvs twice.
cp -a plplot plplot_working
cp -a plplot plplot_patched

You do not touch plplot in any way to keep it as a reference. In
plplot_working you make and test all your changes.  This will add lots of
files that you don't want in your patch.  However, any changes to an
existing file in plplot you copy to the plplot_patched tree, and any new
source files that you want to be part of your patch you copy to the
plplot_patched tree.

diff -Nar -U 5 plplot plplot_patched  > plplot_patch

I use -U 5 rather -u so that plenty of context is given.

IMPORTANT: Look at your recursive patch, plplot_patch, to review all the
changes you have made and to make sure no additional files have gotten into it
that you don't want.

Once I have access to your plplot_patch (e-mailing it to me as an attachment
should be fine) I should be able to apply it to the existing latest tree
from cvs with no muss or fuss with all new files in the directories where
you want them to go.  Put some thought into which directories (or which new
directories) you use for the new files in plplot_patched. Once I get your
changes working, we may want to change locations of files, but it would be
nice if you found good places for them right from the start following what
has already been done for python.

(2) IMPORTANT.  It is important to incorporate new software in as small
chunks as possible to make it more easy for our group to evaluate the
changes.  So for now, in the interests of having your patch accepted, please
exclude *all* changes having to do with plimage.  So for every difference
that appears in the patch, ask the question is this *absolutely necessary*
to get the basic widget to work? Once we sort out any problems associated
with getting the widget to work, then a second patch to implement plimage
should be evaluted on its own merits.

(3) I need a cookbook of how to get this new widget to work.  What version
of libqt?  (I have 2.3.1.) What version of python?  (I have access both to
1.5.2 and 2.0.1, but my Numeric module [version 20.1.0] is for 2.0.1.) What
version of pyqt?  (pyqt is not accessible as a regular Debian package,
AFAIK, so what version, so where should I download your favorite version?)
What plplot ./configure options do you use?  Once you have run make, what
are all the remaining steps you do to get your examples working (excluding
examples, such as example3, which use plimage).  In addition, what changes
have to be made (if any) to the existing xw??.py examples to get them to
work with the new widget.?

Thanks in advance for the additional work I have requested.  But once I have
a clean recursive patch from you against the latest plplot (*excluding
everything to do with plimage for now*), and a cookbook of exactly
what to do to run some examples, I will be most interested in further
evaluation of your work.  It sounds promising, and thanks very much
for the effort you have already put into this.

I would be willing to look at the plimage stuff much later once we get
the basic pyqt widget patch evaluated.

Alan

email: ir...@be...
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6
__________________________

Linux-powered astrophysics
__________________________

On Mon, 29 Oct 2001, Alessandro Mirone wrote:

> Hi,
>  I have posted the following into the patch
> pages on sourceforge :
> -----------------------------------------------------------
>
> By exporting few more xwin basic functions
> it is possible to obtain a qplplot widget
> embedded into pyqt WITHOUT recompiling pyqt ;).
>
>
> I put here the patch. It contains a patch
> for plplot and the qplplot.py module that
> extends pyqt
>
> By the way... the plplot patch also contains
> a plimage new function. it is accelerated
> for the xwin driver.
>
> You can discard it if you dont like it
> but I think that it is useful.
> The other drivers are slow with plimage
> but I hope someone could write the analogous
> to make it fast.
>
> Also the qplplot.py needs volonteers to
> be ported to windows... any volonteer?
>
> Best regards Alessandro Mirone
>
> _______________________________________________
> Plplot-devel mailing list
> Plp...@li...
> https://lists.sourceforge.net/lists/listinfo/plplot-devel
>