On 27 January 2015 at 08:16, Arjen Markus <arjen.mar...@deltares.nl> wrote: > Hi Alan, > > > >> -----Original Message----- >> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] >> Sent: Tuesday, January 27, 2015 2:17 AM >> To: Arjen Markus; Phil Rosenberg; Jim Dishaw; PLplot development list >> Subject: Release plans >> >> To Arjen, Phil, and Jim: >> >> I am addressing this post mostly to you guys because you are the only ones >> I am >> aware of that are still working on substantial (i.e., non >> bug-fix) changes for this release cycle. >> >> As release manager, I really appreciate how hard all of you are working on >> improving >> PLplot in the areas of the Fortran binding, wxwidgets device driver, and >> plmeta/plbuf. >> And hopefully most or all of your substantial changes will get into the >> forthcoming >> release (scheduled for February 28th). >> >> The criteria you should consider about substantial (i.e, non bug-fix) >> master branch >> changes at any time but especially this close to release are the >> following: >> >> 1. Is your change thoroughly tested on Windows and Unix (typically >> Linux) with no build issues and no segfaults at run time? >> Testing the wxWidgets on Windows and Linux should be no problem, however I don't have access to a Mac. There are is some Mac specific code in the wxWidgets driver, which I have left alone, but I don't know what impact the changes will make. If anyone has a Mac they can test on that would be really good.
>> 2. Is it better than what it is replacing? I think it is fair to say from >> the topic-branch >> commits I have seen the current Fortran binding and wxwidgets rewrites are >> partially >> disqualified by this criterion, but hopefully that will change soon in >> both cases. My aim for now is that the rendering results by wxWidgets should be no worse than after a resize of the window in the current driver. This is because there are a number of bugs and deficiencies in the buffer that are coming to light. These are currently being addressed by Jim and progress is being made. I would refer to these particular changes as bug fixes as they affect the results of any plreplot call. However there are a significant number of such bugs and they are not all trivial changes of a few lines of code so there is more risk than with smaller changes. When Jim sends me his patches I will look through them and retest them so hopefully with double checking we won't introduce any problems. One thing that I think we will be stuck with is the way rotated text is at the wrong angle when plreplot is used and the aspect ratio is not the same as the original. This is probably going to require a significant change to the buffer and maybe won't get done in time. Although as Jim is dealing with most of the buffer issues I he can probably comment further. My intention is to have an escape option to fix the aspect ratio of the plot so this at least gives a workaround. >> >> My impression is Phil has already achieved one of his desired goals which >> is a >> greatly simplified and easier to maintain wxwidgets device driver. Of >> course, the >> current rendering issues are of concern, but from what Phil has said, he >> is actively >> working on those so the prospects of meeting this criterion soon look >> fairly good. All line width issues are now sorted, the only remaining issue is the 3d text rendering. As I mentioned in my previous email, if anyone has any insider knowledge about how that functions that would be helpful. Otherwise I will simply try to blindly copy what was done in the old wxWidgets graphics context backend, which will therefore meet my aim of "no worse than before." >> >> I don't know the status of the plmeta/plbuf changes with regard to these >> two criteria, >> but I strongly encourage Jim to make his topic branch commits available to >> the >> plplot-devel list via git format-patch so they can be evaluated by these >> criteria by >> everybody. >> >> <aside> And similarly for Arjen (who has been communicating with me by >> tarball >> because he has been having difficulty using git format-patch on Windows). >> Can >> someone here give Arjen advice about a good command-line git client to use >> on >> Windows where the format-patch command "just works"? </aside> >> > I probably have found it in the form of a Cygwin package for dealing with > git. I have not tried it yet, but I have a feeling it is more to my liking > than the one that I had which used the PowerShell. Cygwin git is the version that I use too and I have found it "just works". Usefully you can also use git daemon from Cygwin to share your local repo with computers on your lan. It seems to be read only access, but it helps if you wish to clone your repo to another computer to test, then you can create a patch to pass the changes back up. > >> >> If you cannot meet that deadline, then I suggest you give your highest >> priority to >> finishing the small changes (such as Jim's plmem.c >> changes) that can be committed to master before that deadline. My intention is to have the wxWidgets changes complete in the next couple of weeks so it is available for testing in advance as you say. Phil ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
