From: <jca...@in...> - 2001-11-22 10:51:35
|
On Thursday 01 November 2001 22:06, Alessandro Mirone wrote: | Hello Alan, =2E.. | 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=20 with Alan about plimage. I have applied your original patch and,=20 after some modifications, got plimage to work (I created a x20c.c=20 demo). But I need some clarifications and further work from you,=20 before I commit the changes to cvs. 1-We need a description of usage, including the arguments=20 descriptions. See for example =20 http://plplot.sourceforge.net/resources/docbook-manual/plplotdoc-html-0.4= =2E2/plshade1.html (but plain text is OK). 2-Your patch includes a plmoveimage() and associated functions and=20 PLESC driver functions. These are only used in qplplot.py. Are these=20 functions really necessary? For one thing, one is introducing a=20 function in plcore.c that is only meaningfull for plimage and a=20 particular driver, and for the other side there are lots of PLESCs=20 (if necessary, those could be colapsed just in one=20 PLESC_PLIMAGEOPS(arg)). Also, the "move" operation is not very usual=20 in plots. What is its purpose? 3-In plimage() you use a row vector as argument for the image, but=20 plplot generally uses a 2D matrix for similar calls. Is there any=20 reason for this? I am willing to commit my changes to cvs, without plmoveimage(), and=20 we could latter solve some other issues. What do you thing? Please=20 anwser to the list. Thanks, Joao | Best regards | | Alessandro Mirone | | | _______________________________________________ | Plplot-devel mailing list | Plp...@li... | https://lists.sourceforge.net/lists/listinfo/plplot-devel |