From: Alessandro M. <mi...@es...> - 2001-11-22 17:01:25
|
Hi Jo=E3o, it's great that you got plimage working!! I will certainly send a description of plimage. I agree that plmoveimage is not necessary and = we can discard it by the moment. Yes it is a good idea to collapse all those PLESC. I would like to keep the PLESC that disactivate the pixmap and metabuffer. That is because I am planning to = write things like xhairs ( or whatever shape ) from python. That lets you the freedom to ( just imagine) select a polygonal shape from an image for an integral or whatever having at the same time a visual representetion of the shape. The shape changes continuosly and might be very general so it's good to manage that from python. About the call to plimage we can discuss the arguments.. I have no particular preference so may be we could generate an analogous of pgimage. What do you plan todo? You commit a working plimage and the we refine the plesc? Or you want me to refine the plescs? As you prefer. By the moment I'll send a description of plimage = to generate the html Ciao Alessandro Jo=E3o Cardoso wrote: > = > On Thursday 01 November 2001 22:06, Alessandro Mirone wrote: > | Hello Alan, > ... > | If you agree I would like to submit to your kind evaluation, in > | the next weeks, small bunches of code ( as you suggested) in order > | to implement step by step a plimage that fits our needs and > | hopefully those of the plplot community. > = > I don't know if there has been some further particular conversations > with Alan about plimage. I have applied your original patch and, > after some modifications, got plimage to work (I created a x20c.c > demo). But I need some clarifications and further work from you, > before I commit the changes to cvs. > = > 1-We need a description of usage, including the arguments > descriptions. See for example > http://plplot.sourceforge.net/resources/docbook-manual/plplotdoc-html-0= =2E4.2/plshade1.html > (but plain text is OK). > = > 2-Your patch includes a plmoveimage() and associated functions and > PLESC driver functions. These are only used in qplplot.py. Are these > functions really necessary? For one thing, one is introducing a > function in plcore.c that is only meaningfull for plimage and a > particular driver, and for the other side there are lots of PLESCs > (if necessary, those could be colapsed just in one > PLESC_PLIMAGEOPS(arg)). Also, the "move" operation is not very usual > in plots. What is its purpose? > = > 3-In plimage() you use a row vector as argument for the image, but > plplot generally uses a 2D matrix for similar calls. Is there any > reason for this? > = > I am willing to commit my changes to cvs, without plmoveimage(), and > we could latter solve some other issues. What do you thing? Please > anwser to the list. > = > Thanks, > Joao > = > | Best regards > | > | Alessandro Mirone > | > | > | _______________________________________________ > | Plplot-devel mailing list > | Plp...@li... > | https://lists.sourceforge.net/lists/listinfo/plplot-devel |