Hi Alain sorry I haven carefully read up to the end all the README.developers file here the patch
On Tue, Dec 25, 2018 at 9:54 PM Alan W. Irwin <alan.w.irwin1...@gmail.com> wrote: > On 2018-12-25 17:54-0000 António Rodrigues Tomé wrote: > > > Hi alan > > I do not pretend to understand everything you are asking for. > > But i think the changes I purpose completely solve the alpha problem in > qt > > raster drivers. > > 1) I send you three files of the same plot with a yellow background with > > alpha=1, alpha=0.5, Alpha=0 (full background transparency). > > then I upload them to a template of the libreoffice impress just to > > ilustrate the effect. > > Hi António: > > Merry Christmas! > > Those illustrations do look like your changes have solved the > transparency issue for at least the qt raster devices. For example, > that checkerboard pattern is a traditional indication for > non-compositing desktops that you have had semi-transparency success, > indicating in better compositing environments (like your pdf example) > you will actually show the appropriate amount of semi-transparency. > > In my own case, the ImageMagick "display" application for > semi-transparent images displays those with a checkerboard background > pattern to indicate a semi-transparent background was detected. I am > not seeing that pattern currently for qt devices, but it appears from > your own results there is a good chance your change will fix that. > > > 2) I think to commit these changes by git someone must give me permition > in > > the plplot git repository. > > For now, the "git commit" command should be used to commit your > changes to your own local topic branch. Last I heard from you on that > issue it appeared all you needed to do was to execute "git add" first. > Was that a success? > > If so, the current status should be you have two separate commits on > your local topic branch (one for your changes to allow use of qt > devices from a QT application, and the other the above transparency > changes), and the next question is how to communicate those git > commits to us for evaluation. > > That is done with the git format-patch command as documented in > README.developers. > > Once we have your commits in that format, we will likely test them and > amend them (e.g., by adding additional "Tested by:" stanzas to the > your commit message). And assuming those tests are a success we will > then push your amended commit to the master branch of our SF git > server with the normal git credit to you for your (amended) git > commits. > > With regard to the question of pushing your commits directly yourself, > that privilege is reserved to core PLplot developers. And you become > one of those by showing sustained interest using the above git > format-patch method of getting your development work (eventually) > pushed. > > That said, we are always looking for future core PLplot developers and > especially someone with Qt expertise who has a sustained interest! So > let's see how it goes with the above git format-patch approach. > > Alan > __________________________ > Alan W. Irwin > > Programming affiliations with the FreeEOS equation-of-state > implementation for stellar interiors (freeeos.sf.net); the Time > Ephemerides project (timeephem.sf.net); PLplot scientific plotting > software package (plplot.sf.net); the libLASi project > (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); > and the Linux Brochure Project (lbproject.sf.net). > __________________________ > > Linux-powered Science > __________________________ > -- António Rodrigues Tomé Universidade da Beira Interior Instituto D. Luís (lab associado) email address: art...@gmail.com art...@ubi.pt http://www.researcherid.com/rid/A-5681-2013
qtdriversissues.tar.gz
Description: application/gzip
_______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
