From: <ai...@us...> - 2010-02-28 04:55:39
|
Revision: 10829 http://plplot.svn.sourceforge.net/plplot/?rev=10829&view=rev Author: airwin Date: 2010-02-28 04:55:33 +0000 (Sun, 28 Feb 2010) Log Message: ----------- Enter column of test results for static devices (ENABLE_DYNDRIVER=OFF), cmake-2.8.1-rc3, and Debian Lenny. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-02-28 03:40:52 UTC (rev 10828) +++ trunk/README.release 2010-02-28 04:55:33 UTC (rev 10829) @@ -196,23 +196,23 @@ 0. Tests made for release 5.9.6 -Name of tester: airwin airwin airwin airwin -PLplot revision: 10814 10813 10821 10827 -CMake versions: 2.6.4 2.8.1-rc3 2.6.4 2.6.4 -Platform: Lenny Lenny Lenny Lenny -pango/cairo version: system system system system -Qt version: 4.6.1 4.6.1 4.6.1 4.6.1 -BUILD_SHARED_LIBS: ON ON ON OFF -ENABLE_DYNDRIVERS: ON ON OFF OFF -Build? YES YES YES YES -ctest? NO NO NO NO -test_noninteractive? YES YES YES YES -test_interactive? YES YES YES YES +Name of tester: airwin airwin airwin airwin airwin +PLplot revision: 10814 10813 10821 10828 10827 +CMake versions: 2.6.4 2.8.1-rc3 2.6.4 2.8.1-rc3 2.6.4 +Platform: Lenny Lenny Lenny Lenny Lenny +pango/cairo version: system system system system system +Qt version: 4.6.1 4.6.1 4.6.1 4.6.1 4.6.1 +BUILD_SHARED_LIBS: ON ON ON ON OFF +ENABLE_DYNDRIVERS: ON ON OFF OFF OFF +Build? YES YES YES YES YES +ctest? NO NO NO NO NO +test_noninteractive? YES YES YES YES YES +test_interactive? YES YES YES YES YES -Install? YES YES YES YES -test_noninteractive? YES YES YES YES -test_interactive? YES YES YES YES -Notes: a,b,A,B a,b,A,B a,b,A,B,C a,c,A,B +Install? YES YES YES YES YES +test_noninteractive? YES YES YES YES YES +test_interactive? YES YES YES YES YES +Notes: a,b,A,B a,b,A,B a,b,A,B,C a,b,A,B,C a,c,A,B Testing notes (lower case notes concern configuration and build options while upper case notes concern errors): This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2010-02-28 06:10:50
|
Revision: 10830 http://plplot.svn.sourceforge.net/plplot/?rev=10830&view=rev Author: airwin Date: 2010-02-28 06:10:44 +0000 (Sun, 28 Feb 2010) Log Message: ----------- Enter column of test results for the case of a static library build (BUILD_SHARED_LIBS=OFF), cmake-2.8.1-rc3, and Debian Lenny. This completes the first round of my set of six test results (3 major configurations, 2 CMake versions) for Debian Lenny, but I plan further rounds of testing of these configurations when CMake-2.8.1 is released, PLplot bug fixes are made, or there are significant extensions of the tests performed by the two major test targets (test_noninteractive or test_interactive). I also plan to do a final round of testing in the week before the release to confirm no new regressions have been introduced by the usual last-minute flurry of PLplot changes before the release. N.B. Test results are requested for other Linux platforms, Mac OS X or other Unix platforms, and the various Windows platforms. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-02-28 04:55:33 UTC (rev 10829) +++ trunk/README.release 2010-02-28 06:10:44 UTC (rev 10830) @@ -196,23 +196,23 @@ 0. Tests made for release 5.9.6 -Name of tester: airwin airwin airwin airwin airwin -PLplot revision: 10814 10813 10821 10828 10827 -CMake versions: 2.6.4 2.8.1-rc3 2.6.4 2.8.1-rc3 2.6.4 -Platform: Lenny Lenny Lenny Lenny Lenny -pango/cairo version: system system system system system -Qt version: 4.6.1 4.6.1 4.6.1 4.6.1 4.6.1 -BUILD_SHARED_LIBS: ON ON ON ON OFF -ENABLE_DYNDRIVERS: ON ON OFF OFF OFF -Build? YES YES YES YES YES -ctest? NO NO NO NO NO -test_noninteractive? YES YES YES YES YES -test_interactive? YES YES YES YES YES +Name of tester: airwin airwin airwin airwin airwin airwin +PLplot revision: 10814 10813 10821 10828 10827 10829 +CMake versions: 2.6.4 2.8.1-rc3 2.6.4 2.8.1-rc3 2.6.4 2.8.1-rc3 +Platform: Lenny Lenny Lenny Lenny Lenny Lenny +pango/cairo version: system system system system system system +Qt version: 4.6.1 4.6.1 4.6.1 4.6.1 4.6.1 4.6.1 +BUILD_SHARED_LIBS: ON ON ON ON OFF OFF +ENABLE_DYNDRIVERS: ON ON OFF OFF OFF OFF +Build? YES YES YES YES YES YES +ctest? NO NO NO NO NO NO +test_noninteractive? YES YES YES YES YES YES +test_interactive? YES YES YES YES YES YES -Install? YES YES YES YES YES -test_noninteractive? YES YES YES YES YES -test_interactive? YES YES YES YES YES -Notes: a,b,A,B a,b,A,B a,b,A,B,C a,b,A,B,C a,c,A,B +Install? YES YES YES YES YES YES +test_noninteractive? YES YES YES YES YES YES +test_interactive? YES YES YES YES YES YES +Notes: a,b,A,B a,b,A,B a,b,A,B,C a,b,A,B,C a,c,A,B a,c,A,B,D Testing notes (lower case notes concern configuration and build options while upper case notes concern errors): @@ -243,6 +243,10 @@ and install tree. (bug 2960324, https://sourceforge.net/tracker/?func=detail&aid=2960324&group_id=2915&atid=102915). + D. With CMake-2.8.1-rc3 could not build D examples for the case + where static libraries were built. Thus, had to disable D for this + combination of circumstances. + 1. Changes relative to PLplot 5.9.5 (the previous development release) 1.1 Make PLplot aware of LC_NUMERIC locale This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2010-03-01 20:07:35
|
Revision: 10835 http://plplot.svn.sourceforge.net/plplot/?rev=10835&view=rev Author: airwin Date: 2010-03-01 20:07:25 +0000 (Mon, 01 Mar 2010) Log Message: ----------- Revision 10834 fixes the D static linking issue. Update test results accordingly. Revision Links: -------------- http://plplot.svn.sourceforge.net/plplot/?rev=10834&view=rev Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-03-01 20:04:59 UTC (rev 10834) +++ trunk/README.release 2010-03-01 20:07:25 UTC (rev 10835) @@ -197,7 +197,7 @@ 0. Tests made for release 5.9.6 Name of tester: airwin airwin airwin airwin airwin airwin -PLplot revision: 10814 10813 10821 10828 10827 10829 +PLplot revision: 10814 10834 10821 10828 10834 10834 CMake versions: 2.6.4 2.8.1-rc3 2.6.4 2.8.1-rc3 2.6.4 2.8.1-rc3 Platform: Lenny Lenny Lenny Lenny Lenny Lenny pango/cairo version: system system system system system system @@ -212,7 +212,7 @@ Install? YES YES YES YES YES YES test_noninteractive? YES YES YES YES YES YES test_interactive? YES YES YES YES YES YES -Notes: a,b,A,B a,b,A,B a,b,A,B,C a,b,A,B,C a,c,A,B a,c,A,B,D +Notes: a,b,A,B a,b,A,B a,b,A,B,C a,b,A,B,C a,c,A,B a,c,A,B Testing notes (lower case notes concern configuration and build options while upper case notes concern errors): @@ -243,10 +243,6 @@ and install tree. (bug 2960324, https://sourceforge.net/tracker/?func=detail&aid=2960324&group_id=2915&atid=102915). - D. With CMake-2.8.1-rc3 could not build D examples for the case - where static libraries were built. Thus, had to disable D for this - combination of circumstances. - 1. Changes relative to PLplot 5.9.5 (the previous development release) 1.1 Make PLplot aware of LC_NUMERIC locale This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2010-03-01 20:52:47
|
Revision: 10837 http://plplot.svn.sourceforge.net/plplot/?rev=10837&view=rev Author: airwin Date: 2010-03-01 20:52:41 +0000 (Mon, 01 Mar 2010) Log Message: ----------- Include more information about test conditions (e.g., 64-bit hardware). Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-03-01 20:12:43 UTC (rev 10836) +++ trunk/README.release 2010-03-01 20:52:41 UTC (rev 10837) @@ -196,38 +196,45 @@ 0. Tests made for release 5.9.6 -Name of tester: airwin airwin airwin airwin airwin airwin -PLplot revision: 10814 10834 10821 10828 10834 10834 -CMake versions: 2.6.4 2.8.1-rc3 2.6.4 2.8.1-rc3 2.6.4 2.8.1-rc3 -Platform: Lenny Lenny Lenny Lenny Lenny Lenny -pango/cairo version: system system system system system system -Qt version: 4.6.1 4.6.1 4.6.1 4.6.1 4.6.1 4.6.1 -BUILD_SHARED_LIBS: ON ON ON ON OFF OFF -ENABLE_DYNDRIVERS: ON ON OFF OFF OFF OFF -Build? YES YES YES YES YES YES -ctest? NO NO NO NO NO NO -test_noninteractive? YES YES YES YES YES YES -test_interactive? YES YES YES YES YES YES +Name of tester: airwin airwin airwin airwin airwin airwin +PLplot revision: 10814 10834 10821 10828 10834 10834 +CMake versions: 2.6.4 2.8.1-rc3 2.6.4 2.8.1-rc3 2.6.4 2.8.1-rc3 +Platform: Lenny Lenny Lenny Lenny Lenny Lenny +pango/cairo version: system system system system system system +Qt version: 4.6.1 4.6.1 4.6.1 4.6.1 4.6.1 4.6.1 +BUILD_SHARED_LIBS: ON ON ON ON OFF OFF +ENABLE_DYNDRIVERS: ON ON OFF OFF OFF OFF -Install? YES YES YES YES YES YES -test_noninteractive? YES YES YES YES YES YES -test_interactive? YES YES YES YES YES YES -Notes: a,b,A,B a,b,A,B a,b,A,B,C a,b,A,B,C a,c,A,B a,c,A,B +Build? YES YES YES YES YES YES +ctest? NO NO NO NO NO NO +test_noninteractive? YES YES YES YES YES YES +test_interactive? YES YES YES YES YES YES +Install? YES YES YES YES YES YES +test_noninteractive? YES YES YES YES YES YES +test_interactive? YES YES YES YES YES YES + +Notes: a,b,c,A,B a,b,c,A,B a,b,c,A,B,C a,b,c,A,B,C a,b,d,A,B a,b,d,A,B + Testing notes (lower case notes concern configuration and build options while upper case notes concern errors): - a. All suitable dependent libraries installed on system so there are + a. Testing done on 64-bit (AMD64) hardware. + + b. Used parallel make option (-j4) for all builds, installs, and test + targets. + + c. All suitable dependent libraries installed on system so there are no device drivers from default list that are missing from this test. All compilers and bindings-related development packages installed on system so there are no bindings that are missing from this test. - b. Used parallel make option (-j4) for all builds, installs, and test - targets. + d. All suitable dependent libraries installed on system so there are + no device drivers from default list that are missing from this test. + Java, Python, Octave, Perl/PDL, LUA, and OCaml bindings/examples not + available for static library build (BUILD_SHARED_LIBS=OFF) so not + tested. - c. Java, Python, Octave, Perl/PDL, LUA, OCaml bindings/examples not - available for static library build (BUILD_SHARED_LIBS=OFF) so not tested. - A. No obvious configure, build, or install errors. Some well-known rendering bugs (e.g., bug 2960373, https://sourceforge.net/tracker/?func=detail&aid=2960373&group_id=2915&atid=102915 This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2010-04-12 23:07:17
|
Revision: 10911 http://plplot.svn.sourceforge.net/plplot/?rev=10911&view=rev Author: airwin Date: 2010-04-12 23:07:11 +0000 (Mon, 12 Apr 2010) Log Message: ----------- Add announcement of recent plpoin changes. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-04-12 22:21:14 UTC (rev 10910) +++ trunk/README.release 2010-04-12 23:07:11 UTC (rev 10911) @@ -141,6 +141,19 @@ djgpp platform is no longer actively developed, and he no longer uses djgpp himself. +XVI. As of release 5.9.6 plpoin results for ascii codes 92, 94, and 95 +are changed from centred dot, degree symbol, and centred dot glyphs to +the correct backslash, caret, and underscore glyphs that are +associated with those ascii indices. This change is consistent with +the documentation of plpoin and solves a long-standing issue with +backslash, caret, and underscore ascii characters in character strings +used for example by pl[mp]tex. Those who need access to a centred dot +with plpoin should use index 1. The degree symbol is no longer +accessible with plpoin, but it is available in ordinary text input to +PLplot as Hershey escape "#(718)", where 718 is the Hershey index of +the degree symbol, unicode escape "#[0x00B0]" where 0x00B0 is the +unicode index for the degree symbol or direct UTF8 unicode string "°". + INDEX 0. Tests made for release 5.9.6 This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <hez...@us...> - 2010-04-16 22:35:58
|
Revision: 10917 http://plplot.svn.sourceforge.net/plplot/?rev=10917&view=rev Author: hezekiahcarty Date: 2010-04-16 22:35:52 +0000 (Fri, 16 Apr 2010) Log Message: ----------- Update README.release for axis labeling and unverisal transform Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-04-16 22:34:38 UTC (rev 10916) +++ trunk/README.release 2010-04-16 22:35:52 UTC (rev 10917) @@ -163,6 +163,8 @@ 1.1 Make PLplot aware of LC_NUMERIC locale 1.2 Linear gradients have been implemented 1.3 Cairo Windows driver implemented +1.4 Custom axis labeling implemented +1.5 Universal coordinate transform implemented 2. Changes relative to PLplot 5.8.0 (the previous stable release) @@ -206,6 +208,8 @@ 2.36 Make PLplot aware of LC_NUMERIC locale 2.37 Linear gradients have been implemented 2.38 Cairo Windows driver implemented +2.39 Custom axis labeling implemented +2.40 Universal coordinate transform implemented 0. Tests made for release 5.9.6 @@ -349,6 +353,21 @@ interactive cairo driver for Windows similar to xcairo on Linux. Work to improve its functionality is ongoing. +1.4 Custom axis labeling implemented + +Axis text labels can now be customized using the new plslabelfunc function. +This allows a user to specify what text should be draw at a given position +along a plot axis. Example 19 has been updated to illustrate this function's +use through labeling geographic coordinates in degrees North, South, East and +West. + +1.5 Universal coordinate transform implemented + +A custom coordinate transformation function can be set using plstransform. +This transformation function affects all subsequent plot function calls which +work with plot window coordinates. Testing and refinement of this support is +ongoing. + 2. Changes relative to PLplot 5.8.0 (the previous stable release) 2.1 All autotools-related files have now been removed @@ -915,3 +934,18 @@ interactive cairo driver for Windows similar to xcairo on Linux. Work to improve its functionality is ongoing. +2.39 Custom axis labeling implemented + +Axis text labels can now be customized using the new plslabelfunc function. +This allows a user to specify what text should be draw at a given position +along a plot axis. Example 19 has been updated to illustrate this function's +use through labeling geographic coordinates in degrees North, South, East and +West. + +2.40 Universal coordinate transform implemented + +A custom coordinate transformation function can be set using plstransform. +This transformation function affects all subsequent plot function calls which +work with plot window coordinates. Testing and refinement of this support is +ongoing. + This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <hba...@us...> - 2010-04-18 18:22:54
|
Revision: 10921 http://plplot.svn.sourceforge.net/plplot/?rev=10921&view=rev Author: hbabcock Date: 2010-04-18 18:22:48 +0000 (Sun, 18 Apr 2010) Log Message: ----------- Add a note about David arbitrary storage for 2D user data work. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-04-18 17:54:59 UTC (rev 10920) +++ trunk/README.release 2010-04-18 18:22:48 UTC (rev 10921) @@ -165,7 +165,9 @@ 1.3 Cairo Windows driver implemented 1.4 Custom axis labeling implemented 1.5 Universal coordinate transform implemented +1.6 Support for arbitrary storage of 2D user data + 2. Changes relative to PLplot 5.8.0 (the previous stable release) 2.1 All autotools-related files have now been removed @@ -209,8 +211,10 @@ 2.37 Linear gradients have been implemented 2.38 Cairo Windows driver implemented 2.39 Custom axis labeling implemented -2.40 Universal coordinate transform implemented +2.40 Universal coordinate transform implemente +2.41 Support for arbitrary storage of 2D user data + 0. Tests made for release 5.9.6 Name of tester: airwin airwin airwin airwin airwin airwin @@ -267,6 +271,7 @@ and install tree. (bug 2960324, https://sourceforge.net/tracker/?func=detail&aid=2960324&group_id=2915&atid=102915). + 1. Changes relative to PLplot 5.9.5 (the previous development release) 1.1 Make PLplot aware of LC_NUMERIC locale @@ -368,6 +373,61 @@ work with plot window coordinates. Testing and refinement of this support is ongoing. +1.6 Support for arbitrary storage of 2D user data + +This improvement courtesy of David MacMahon adds support for arbitrary +storage of 2D user data. This is very similar to the technique employed +by some existing functions (e.g. plfcont and plfshade) that use "evaluator" +functions to access 2D user data that is stored in an arbtrary format. +The new approach extends the concept of a user-supplied (or predefined) +"evaluator" function to a group of user-supplied (or predefined) "operator" +functions. The operator functions provide for various operations on the +arbitrarily stored 2D data including: get, set, +=, -=, *=, /=, isnan, +minmax, and f2eval. + +To facilitate the passing of an entire family of operator functions (via +function pointers), a plf2ops_t structure is defined to contain a +pointer to each type of operator function. Predefined operator +functions are defined for several common 2D data storage techniques. +Variables (of type plf2ops_t) containing function pointers for these +operator functions are also defined. + +New variants of functions that accept 2D data are created. The new +variants accept the 2D data as two parameters: a pointer to a plf2ops_t +structure containing (pointers to) suitable operator functions and a +PLPointer to the actual 2D data store. Existing functions that accept +2D data are modified to simply pass their parameters to the +corresponding new variant of the function, along with a pointer to the +suitable predefined plf2ops_t stucture of operator function pointers. + +The list of functions for which new variants are created is: +c_plimage, c_plimagefr, c_plmesh, c_plmeshc, c_plot3d, c_plot3dc, +c_plot3dcl, c_plshade1, c_plshades, c_plsurf3d, and c_plsurf3dl, and +c_plgriddata. The new variants are named the same as their +corresponding existing function except that the "c_" prefix is changed +to "plf" (e.g. the new variant of c_plmesh is called plfmesh). + +Adds plfvect declaration to plplot.h and changes the names (and only the +names) of some plfvect arguments to make them slightly clearer. In +order to maintain backwards API compatibility, this function and the +other existing functions that use "evaluator" functions are NOT changed +to use the new operator functions. + +Makes plplot.h and libplplot consistent vis-a-vis pltr0f and pltr2d. +Moves the definitions of pltr2f (already declared in plplot.h) from the +sccont.c files of the FORTRAN 77 and Fortran 95 bindings into plcont.c. +Removes pltr0f declaration from plplot.h. + +Changes x08c.c to demonstrate use of new support for arbitrary storage +of 2D data arrays. Shows how to do surface plots with the following +four types of 2D data arrays: + +1) PLFLT z[nx][ny]; +2) PLfGrid2 z; +3) PLFLT z[nx*ny]; /* row major order */ +4) PLFLT z[nx*ny]; /* column major order */ + + 2. Changes relative to PLplot 5.8.0 (the previous stable release) 2.1 All autotools-related files have now been removed @@ -949,3 +1009,57 @@ work with plot window coordinates. Testing and refinement of this support is ongoing. +2.41 Support for arbitrary storage of 2D user data + +This improvement courtesy of David MacMahon adds support for arbitrary +storage of 2D user data. This is very similar to the technique employed +by some existing functions (e.g. plfcont and plfshade) that use "evaluator" +functions to access 2D user data that is stored in an arbtrary format. +The new approach extends the concept of a user-supplied (or predefined) +"evaluator" function to a group of user-supplied (or predefined) "operator" +functions. The operator functions provide for various operations on the +arbitrarily stored 2D data including: get, set, +=, -=, *=, /=, isnan, +minmax, and f2eval. + +To facilitate the passing of an entire family of operator functions (via +function pointers), a plf2ops_t structure is defined to contain a +pointer to each type of operator function. Predefined operator +functions are defined for several common 2D data storage techniques. +Variables (of type plf2ops_t) containing function pointers for these +operator functions are also defined. + +New variants of functions that accept 2D data are created. The new +variants accept the 2D data as two parameters: a pointer to a plf2ops_t +structure containing (pointers to) suitable operator functions and a +PLPointer to the actual 2D data store. Existing functions that accept +2D data are modified to simply pass their parameters to the +corresponding new variant of the function, along with a pointer to the +suitable predefined plf2ops_t stucture of operator function pointers. + +The list of functions for which new variants are created is: +c_plimage, c_plimagefr, c_plmesh, c_plmeshc, c_plot3d, c_plot3dc, +c_plot3dcl, c_plshade1, c_plshades, c_plsurf3d, and c_plsurf3dl, and +c_plgriddata. The new variants are named the same as their +corresponding existing function except that the "c_" prefix is changed +to "plf" (e.g. the new variant of c_plmesh is called plfmesh). + +Adds plfvect declaration to plplot.h and changes the names (and only the +names) of some plfvect arguments to make them slightly clearer. In +order to maintain backwards API compatibility, this function and the +other existing functions that use "evaluator" functions are NOT changed +to use the new operator functions. + +Makes plplot.h and libplplot consistent vis-a-vis pltr0f and pltr2d. +Moves the definitions of pltr2f (already declared in plplot.h) from the +sccont.c files of the FORTRAN 77 and Fortran 95 bindings into plcont.c. +Removes pltr0f declaration from plplot.h. + +Changes x08c.c to demonstrate use of new support for arbitrary storage +of 2D data arrays. Shows how to do surface plots with the following +four types of 2D data arrays: + +1) PLFLT z[nx][ny]; +2) PLfGrid2 z; +3) PLFLT z[nx*ny]; /* row major order */ +4) PLFLT z[nx*ny]; /* column major order */ + This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <hba...@us...> - 2010-04-18 18:24:34
|
Revision: 10923 http://plplot.svn.sourceforge.net/plplot/?rev=10923&view=rev Author: hbabcock Date: 2010-04-18 18:24:28 +0000 (Sun, 18 Apr 2010) Log Message: ----------- Fix missing typo caused by overzealous use of the backspace key. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-04-18 18:23:45 UTC (rev 10922) +++ trunk/README.release 2010-04-18 18:24:28 UTC (rev 10923) @@ -211,7 +211,7 @@ 2.37 Linear gradients have been implemented 2.38 Cairo Windows driver implemented 2.39 Custom axis labeling implemented -2.40 Universal coordinate transform implemente +2.40 Universal coordinate transform implemented 2.41 Support for arbitrary storage of 2D user data This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2010-04-30 16:23:43
|
Revision: 10955 http://plplot.svn.sourceforge.net/plplot/?rev=10955&view=rev Author: airwin Date: 2010-04-30 16:23:36 +0000 (Fri, 30 Apr 2010) Log Message: ----------- Add description of recent font improvements. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-04-30 02:09:50 UTC (rev 10954) +++ trunk/README.release 2010-04-30 16:23:36 UTC (rev 10955) @@ -166,6 +166,7 @@ 1.4 Custom axis labeling implemented 1.5 Universal coordinate transform implemented 1.6 Support for arbitrary storage of 2D user data +1.7 Font improvements 2. Changes relative to PLplot 5.8.0 (the previous stable release) @@ -213,6 +214,7 @@ 2.39 Custom axis labeling implemented 2.40 Universal coordinate transform implemented 2.41 Support for arbitrary storage of 2D user data +2.42 Font improvements 0. Tests made for release 5.9.6 @@ -427,7 +429,30 @@ 3) PLFLT z[nx*ny]; /* row major order */ 4) PLFLT z[nx*ny]; /* column major order */ +1.7 Font improvements +We have added the underscore to the Hershey glyphs (thanks to David +MacMahon) and slightly rearranged the ascii index to the Hershey +indices so that plpoin now generates the complete set of printable +ascii characters in the correct order for the Hershey fonts (and therefore +the Type1 and TrueType fonts as well). + +We have improved how we access TrueType and Type1 fonts via the Hershey +font index (used by plpoin, plsym, and the Hershey escape sequences in pl*tex +commands). We have added considerably to the Hershey index to Unicode index +translation table both for the compact and extended Hershey indexing scheme, +and we have adopted the standard Unicode to Type1 index translation tables +from http://unicode.org/Public/MAPPINGS/VENDORS/ADOBE/. + +We have also dropped the momentary switch to symbol font that was +implemented in the PLplot core library. That switch was designed to partially +compensate for the lack of symbol glyphs in the standard Type1 fonts. That +was a bad design because it affected TrueType font devices as well as +the desired Type1 font devices. To replace this bad idea we now +change from Type1 standard fonts to the Type1 Symbol font (and vice +versa) whenever there is a glyph lookup failure in the Type1 font +device drivers (ps and pdf). + 2. Changes relative to PLplot 5.8.0 (the previous stable release) 2.1 All autotools-related files have now been removed @@ -1063,3 +1088,27 @@ 3) PLFLT z[nx*ny]; /* row major order */ 4) PLFLT z[nx*ny]; /* column major order */ +2.42 Font improvements + +We have added the underscore to the Hershey glyphs (thanks to David +MacMahon) and slightly rearranged the ascii index to the Hershey +indices so that plpoin now generates the complete set of printable +ascii characters in the correct order for the Hershey fonts (and therefore +the Type1 and TrueType fonts as well). + +We have improved how we access TrueType and Type1 fonts via the Hershey +font index (used by plpoin, plsym, and the Hershey escape sequences in pl*tex +commands). We have added considerably to the Hershey index to Unicode index +translation table both for the compact and extended Hershey indexing scheme, +and we have adopted the standard Unicode to Type1 index translation tables +from http://unicode.org/Public/MAPPINGS/VENDORS/ADOBE/. + +We have also dropped the momentary switch to symbol font that was +implemented in the PLplot core library. That switch was designed to partially +compensate for the lack of symbol glyphs in the standard Type1 fonts. That +was a bad design because it affected TrueType font devices as well as +the desired Type1 font devices. To replace this bad idea we now +change from Type1 standard fonts to the Type1 Symbol font (and vice +versa) whenever there is a glyph lookup failure in the Type1 font +device drivers (ps and pdf). + This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2010-04-30 23:43:26
|
Revision: 10956 http://plplot.svn.sourceforge.net/plplot/?rev=10956&view=rev Author: airwin Date: 2010-04-30 23:43:15 +0000 (Fri, 30 Apr 2010) Log Message: ----------- Instead of giving a table of results for testing reports for 5.9.6 link to http://www.miscdebris.net/plplot_wiki/index.php?title=Testing_PLplot#Testing_Reports for that information. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-04-30 16:23:36 UTC (rev 10955) +++ trunk/README.release 2010-04-30 23:43:15 UTC (rev 10956) @@ -219,61 +219,10 @@ 0. Tests made for release 5.9.6 -Name of tester: airwin airwin airwin airwin airwin airwin -PLplot revision: 10814 10834 10821 10828 10834 10834 -CMake versions: 2.6.4 2.8.1-rc3 2.6.4 2.8.1-rc3 2.6.4 2.8.1-rc3 -Platform: Lenny Lenny Lenny Lenny Lenny Lenny -pango/cairo version: system system system system system system -Qt version: 4.6.1 4.6.1 4.6.1 4.6.1 4.6.1 4.6.1 -BUILD_SHARED_LIBS: ON ON ON ON OFF OFF -ENABLE_DYNDRIVERS: ON ON OFF OFF OFF OFF +See +http://www.miscdebris.net/plplot_wiki/index.php?title=Testing_PLplot#Testing_Reports +for a summary table of all testing done for PLplot-5.9.6. -Build? YES YES YES YES YES YES -ctest? NO NO NO NO NO NO -test_noninteractive? YES YES YES YES YES YES -test_interactive? YES YES YES YES YES YES - -Install? YES YES YES YES YES YES -test_noninteractive? YES YES YES YES YES YES -test_interactive? YES YES YES YES YES YES - -Notes: a,b,c,A,B a,b,c,A,B a,b,c,A,B,C a,b,c,A,B,C a,b,d,A,B a,b,d,A,B - -Testing notes (lower case notes concern configuration and build -options while upper case notes concern errors): - - a. Testing done on 64-bit (AMD64) hardware. - - b. Used parallel make option (-j4) for all builds, installs, and test - targets. - - c. All suitable dependent libraries installed on system so there are - no device drivers from default list that are missing from this test. - All compilers and bindings-related development packages installed on - system so there are no bindings that are missing from this test. - - d. All suitable dependent libraries installed on system so there are - no device drivers from default list that are missing from this test. - Java, Python, Octave, Perl/PDL, LUA, and OCaml bindings/examples not - available for static library build (BUILD_SHARED_LIBS=OFF) so not - tested. - - A. No obvious configure, build, or install errors. Some well-known - rendering bugs (e.g., bug 2960373, - https://sourceforge.net/tracker/?func=detail&aid=2960373&group_id=2915&atid=102915 - or bug 289939, - https://sourceforge.net/tracker/?func=detail&aid=2899393&group_id=2915&atid=102915 - for a few devices or special examples. No run-time errors in tests - other than those noted in additional "upper-case" notes. - - B. test_c_tk subset of test_interactive failed for install - tree. (bug 2960318, https://sourceforge.net/tracker/?func=detail&aid=2960318&group_id=2915&atid=102915). - - C. test_qt_example subset of test_interactive failed for build tree - and install tree. (bug 2960324, - https://sourceforge.net/tracker/?func=detail&aid=2960324&group_id=2915&atid=102915). - - 1. Changes relative to PLplot 5.9.5 (the previous development release) 1.1 Make PLplot aware of LC_NUMERIC locale This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <and...@us...> - 2010-05-18 19:09:12
|
Revision: 11007 http://plplot.svn.sourceforge.net/plplot/?rev=11007&view=rev Author: andrewross Date: 2010-05-18 19:09:05 +0000 (Tue, 18 May 2010) Log Message: ----------- Add note about deprecation of python Numeric support. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-05-18 15:51:23 UTC (rev 11006) +++ trunk/README.release 2010-05-18 19:09:05 UTC (rev 11007) @@ -166,6 +166,14 @@ examples/c/README.cairo). A good replacement for pygcw is our new pyqt4 bindings for PLplot. +XVIII. As of release 5.9.6 we have deprecated support for the python +Numeric array extensions. Numeric is no longer maintained and users +of Numeric are advised to migrate to numpy. Numpy has been the standard +for plplot for some time. If numpy is not present plplot will now +disable python by default. If you still require Numeric support in the +short term then set USE_NUMERIC to ON in cmake. The plplot support +for Numeric will be dropped in a future release. + INDEX 0. Tests made for release 5.9.6 This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2010-05-19 06:36:59
|
Revision: 11009 http://plplot.svn.sourceforge.net/plplot/?rev=11009&view=rev Author: airwin Date: 2010-05-19 06:36:53 +0000 (Wed, 19 May 2010) Log Message: ----------- Change spelling of plplot ==> PLplot where appropriate. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-05-19 06:30:22 UTC (rev 11008) +++ trunk/README.release 2010-05-19 06:36:53 UTC (rev 11009) @@ -169,9 +169,9 @@ XVIII. As of release 5.9.6 we have deprecated support for the python Numeric array extensions. Numeric is no longer maintained and users of Numeric are advised to migrate to numpy. Numpy has been the standard -for plplot for some time. If numpy is not present plplot will now +for PLplot for some time. If numpy is not present PLplot will now disable python by default. If you still require Numeric support in the -short term then set USE_NUMERIC to ON in cmake. The plplot support +short term then set USE_NUMERIC to ON in cmake. The PLplot support for Numeric will be dropped in a future release. INDEX @@ -666,7 +666,7 @@ Also new is an option for the plplot_test.sh script to run the examples using a debugging command. This is enabled using the --debug option. The default it to use the valgrind memory checker. This has highlighted at -least one memory leaks in plplot which have been fixed. It is not part +least one memory leaks in PLplot which have been fixed. It is not part of the standard ctest tests because it can be _very_ slow for a complete set of language bindings and device drivers. @@ -696,7 +696,7 @@ 2.22 Internal changes to function visibility -The internal definitions of functions in plplot have been significantly +The internal definitions of functions in PLplot have been significantly tidied up to allow the use of the -fvisibility=hidden option with newer versions of gcc. This prevents internal functions from being exported to the user where possible. This extends the existing support for this @@ -708,15 +708,15 @@ which allows to open and close dynamic link libraries (DLL) during run-time and call functions from these libraries. As a consequence drivers can now be compiled into single DLLs separate from the core -plplot DLL also in Windows. The cmake option ENABLE_DYNDRIVERS is now -ON by default for Windows if a shared plplot library is built. +PLplot DLL also in Windows. The cmake option ENABLE_DYNDRIVERS is now +ON by default for Windows if a shared PLplot library is built. 2.24 Documentation updates The DocBook documentation has been updated to include many of the C-specific functions (for example plAlloc2dGrid) which are not part of the common API, but are used in the examples and may be helpful -for plplot users. +for PLplot users. 2.25 libnistcd (a.k.a. libcd) now built internally for -dev cgm This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <and...@us...> - 2010-05-27 19:56:50
|
Revision: 11028 http://plplot.svn.sourceforge.net/plplot/?rev=11028&view=rev Author: andrewross Date: 2010-05-27 19:56:43 +0000 (Thu, 27 May 2010) Log Message: ----------- Add note on the problems with gdc on Ubuntu. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-05-27 18:44:18 UTC (rev 11027) +++ trunk/README.release 2010-05-27 19:56:43 UTC (rev 11028) @@ -174,6 +174,14 @@ short term then set USE_NUMERIC to ON in cmake. The PLplot support for Numeric will be dropped in a future release. +XVIV. It has come to out attention that the version of gdc supplied with +several recent versions of Ubuntu has a very serious bug on 64-bit +systems (see https://bugs.launchpad.net/ubuntu/+source/gdc-4.2/+bug/235955) +which causes several of the plplot D examples to crash. If this +affects you, you are recommended to disable the d bindings or switch to +an alternative d compiler (the Digital Mars compiler is reported to +be good). + INDEX 0. Tests made for release 5.9.6 This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <and...@us...> - 2010-05-27 22:00:22
|
Revision: 11031 http://plplot.svn.sourceforge.net/plplot/?rev=11031&view=rev Author: andrewross Date: 2010-05-27 22:00:14 +0000 (Thu, 27 May 2010) Log Message: ----------- Fix typo (thanks for spotting it Hez!). Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-05-27 21:32:29 UTC (rev 11030) +++ trunk/README.release 2010-05-27 22:00:14 UTC (rev 11031) @@ -174,7 +174,7 @@ short term then set USE_NUMERIC to ON in cmake. The PLplot support for Numeric will be dropped in a future release. -XVIV. It has come to out attention that the version of gdc supplied with +XVIV. It has come to our attention that the version of gdc supplied with several recent versions of Ubuntu has a very serious bug on 64-bit systems (see https://bugs.launchpad.net/ubuntu/+source/gdc-4.2/+bug/235955) which causes several of the plplot D examples to crash. If this This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2010-10-02 22:19:25
|
Revision: 11240 http://plplot.svn.sourceforge.net/plplot/?rev=11240&view=rev Author: airwin Date: 2010-10-02 22:19:19 +0000 (Sat, 02 Oct 2010) Log Message: ----------- Add remarks about new pllegend capability to the release notes. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2010-10-02 22:11:06 UTC (rev 11239) +++ trunk/README.release 2010-10-02 22:19:19 UTC (rev 11240) @@ -190,6 +190,7 @@ 1.1 Alpha value support for plotting in memory. 1.2 Add a Qt device for in memory plotting. +1.3 Add discrete legend capability. 2. Changes relative to PLplot 5.8.0 (the previous stable release) @@ -240,6 +241,7 @@ 2.42 Font improvements 2.42 Alpha value support for plotting in memory. 2.43 Add a Qt device for in memory plotting. +2.44 Add discrete legend capability. 0. Tests made for release 5.9.7 @@ -264,7 +266,18 @@ A new device called memqt has been added for in memory plotting using Qt. This device is the Qt equivalent of the memcairo device. +1.3 Add discrete legend capability. +A new routine called pllegend has been added to our core C API. +(N.B. This is an experimental API that may be subject to further +change as we gain more experience with it.) This routine creates a +discrete plot legend with a plotted box, line, and/or line of symbols +for each annotated legend entry. The arguments of pllegend provide +control over the location and size of the legend within the current +subpage as well as the location and characteristics of the elements +(most of which are optional) within that legend. The resulting legend +is clipped at the boundaries of the current subpage + 2. Changes relative to PLplot 5.8.0 (the previous stable release) 2.1 All autotools-related files have now been removed @@ -936,4 +949,16 @@ 2.43 Add a Qt device for in memory plotting. A new device called memqt has been added for in memory plotting using -Qt. This device is the Qt equivalent of the memcairo device. \ No newline at end of file +Qt. This device is the Qt equivalent of the memcairo device. + +2.44 Add discrete legend capability. + +A new routine called pllegend has been added to our core C API. +(N.B. This is an experimental API that may be subject to further +change as we gain more experience with it.) This routine creates a +discrete plot legend with a plotted box, line, and/or line of symbols +for each annotated legend entry. The arguments of pllegend provide +control over the location and size of the legend within the current +subpage as well as the location and characteristics of the elements +(most of which are optional) within that legend. The resulting legend +is clipped at the boundaries of the current subpage This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2011-01-12 05:07:18
|
Revision: 11489 http://plplot.svn.sourceforge.net/plplot/?rev=11489&view=rev Author: airwin Date: 2011-01-12 05:07:12 +0000 (Wed, 12 Jan 2011) Log Message: ----------- Summarize recent changes concerning plstring, plstring3, pllegend, octave, and swig documentation. As per our normal formatting, duplicate the recently committed large polygons comments that are in the section concerning changes since the last stable release (5.8.0) to the earlier section concerning changes since the last release (5.9.7). Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2011-01-12 02:07:03 UTC (rev 11488) +++ trunk/README.release 2011-01-12 05:07:12 UTC (rev 11489) @@ -204,6 +204,12 @@ 1. Changes relative to PLplot 5.9.7 (the previous development release) +1.1 The plstring and plstring3 functions have been added +1.2 The pllegend API has been finalized +1.3 Octave bindings now implemented with swig +1.4 Documentation redone for our swig-generated Python and Octave bindings +1.5 Support large polygons + 2. Changes relative to PLplot 5.8.0 (the previous stable release) 2.1 All autotools-related files have now been removed @@ -254,8 +260,12 @@ 2.43 Add a Qt device for in memory plotting. 2.44 Add discrete legend capability. 2.45 Add full bindings and examples for the D language. +2.46 The plstring and plstring3 functions have been added +2.47 The pllegend API has been finalized +2.48 Octave bindings now implemented with swig +2.49 Documentation redone for our swig-generated Python and Octave bindings +2.50 Support large polygons - -1. Important changes we should have mentioned in previous release announcements. -1.1 Add full bindings and examples for the D language. @@ -284,7 +294,93 @@ 1. Changes relative to PLplot 5.9.7 (the previous development release) +1.1 The plstring and plstring3 functions have been added +The plstring function largely supersedes plpoin and plsym +because many(!) more glyphs are accessible with plstring. The glyph +is specified with a PLplot user string. As with plmtex and plptex, +the user string can contain FCI escapes to determine the font, UTF-8 +code to determine the glyph or else PLplot escapes for Hershey or +unicode text to determine the glyph. Standard examples 4 and 26 use +plstring. + +The plstring3 function largely supersedes plpoin3 for the same (access +to many more glyphs) reasons. Standard example 18 uses plstring3. + +1.2 The pllegend API has been finalized + +The function pllegend allows users to create a discrete plot legend +with a plotted colored box, line, and/or line of symbols for each +annotated legend entry. The pllegend function was first made +available for 5.9.7. Due to feedback from early adopters of pllegend, +we have now added substantially to the pllegend capabilities. and we +now believe pllegend is ready for prime time. The pllegend +capabilities are documented in our docbook documentation and +demonstrated in standard examples 4, 26, and 33. + +N.B. The current set of changes required a backwards-incompatible +change to the pllegend API. This requires users who tried this new +functionality for 5.9.7 to reprogramme their pllegend calls. Since +the pllegend API was labelled experimental for 5.9.7, we will not be +bumping the soversions of the affected PLplot libraries. + +1.3 Octave bindings now implemented with swig + +Octave is a powerful platform that demands a first-class PLplot +solution, but we were finding it difficult to realize that goal +because we were running up against some limitations of the (now +deprecated) matwrap-generated Octave bindings. Accordingly, a +swig-generated version of the Octave bindings has now been implemented +that builds on the prior matwrapped bindings effort but also extends +it with, e.g., bindings for plstring, plstring3, pllegend, and +plcolbar which now make it possible to run examples 4, 18, 26, and 33 +(all of which have now have been updated to use those functions) and +get consistent results with the corresponding C examples. The +swig-generated bindings for Octave are used by default, but the build +system falls back to the matwrapped bindings if swig is not available. +Users can force the matwrapped bindings by using the +-DENABLE_swig_octave=OFF cmake command-line option. + +Like the matwrapped bindings before it, the new swig-generated octave +bindings currently do not have a number of the PLplot functions +wrapped (e.g., "plmap") that are needed by standard example 19. +However, because of the power of swig we now have some confidence we +can solve this issue in the future. + +1.4 Documentation redone for our swig-generated Python and Octave bindings + +Through the docstring %feature, swig can generate documentation +strings for certain of the languages it supports (currently Python, +Octave, and Ruby). We have now removed all such hand-crafted swig +documentation data from bindings/swig-support/plplotcapi.i and +replaced it with generated documentation in the file +bindings/swig-support/swig_documentation.i. That file is generated +from doc/docbook/src/api.xml using the perl script +doc/docbook/bin/api2swigdoc.pl. The build system Unix target +"check_swig_documentation" now runs that script and compares results +with bindings/swig-support/swig_documentation.i in the source tree to +make sure that latter file is consistent with any changes that might +have occurred in doc/docbook/src/api.xml. + +The resulting Octave and Python user-documentation (obtained by 'help +<PLplot_command_name>' in Octave and 'print ("%s" % +<PLplot_command_name>.__doc__)' in Python is much more detailed than +what was available before using the hand-crafted documentation. If we +ever decided to generate PLplot bindings for Ruby with swig, this +high-quality user-documentation would be available for that language +as well. + +1.5 Support large polygons + +Previous releases had an implicit limitation with respect to the +number of vertices in a polygon. This was due to the use of statically +defined arrays (to avoid allocating and freeing memory for each polygon +to be drawn). Jos\xE9 Luis Garc\xEDa Pallero found this limitation and +provided patches to eliminate this limitation. The strategy is +that for small polygons, the original statically defined arrays +are used and for large polygons new arrays are allocated and freed. +This strategy has been applied to all relevant source files. + 2. Changes relative to PLplot 5.8.0 (the previous stable release) 2.1 All autotools-related files have now been removed @@ -987,8 +1083,84 @@ alternative d compiler (the Digital Mars compiler is reported to be good). -2.46 Support large polygons +2.46 The plstring and plstring3 functions have been added +The plstring function largely supersedes plpoin and plsym +because many(!) more glyphs are accessible with plstring. The glyph +is specified with a PLplot user string. As with plmtex and plptex, +the user string can contain FCI escapes to determine the font, UTF-8 +code to determine the glyph or else PLplot escapes for Hershey or +unicode text to determine the glyph. Standard examples 4 and 26 use +plstring. + +The plstring3 function largely supersedes plpoin3 for the same (access +to many more glyphs) reasons. Standard example 18 uses plstring3. + +2.47 The pllegend API has been finalized + +The function pllegend allows users to create a discrete plot legend +with a plotted colored box, line, and/or line of symbols for each +annotated legend entry. The pllegend function was first made +available for 5.9.7. Due to feedback from early adopters of pllegend, +we have now added substantially to the pllegend capabilities. and we +now believe pllegend is ready for prime time. The pllegend +capabilities are documented in our docbook documentation and +demonstrated in standard examples 4, 26, and 33. + +N.B. The current set of changes required a backwards-incompatible +change to the pllegend API. This requires users who tried this new +functionality for 5.9.7 to reprogramme their pllegend calls. Since +the pllegend API was labelled experimental for 5.9.7, we will not be +bumping the soversions of the affected PLplot libraries. + +2.48 Octave bindings now implemented with swig + +Octave is a powerful platform that demands a first-class PLplot +solution, but we were finding it difficult to realize that goal +because we were running up against some limitations of the (now +deprecated) matwrap-generated Octave bindings. Accordingly, a +swig-generated version of the Octave bindings has now been implemented +that builds on the prior matwrapped bindings effort but also extends +it with, e.g., bindings for plstring, plstring3, pllegend, and +plcolbar which now make it possible to run examples 4, 18, 26, and 33 +(all of which have now have been updated to use those functions) and +get consistent results with the corresponding C examples. The +swig-generated bindings for Octave are used by default, but the build +system falls back to the matwrapped bindings if swig is not available. +Users can force the matwrapped bindings by using the +-DENABLE_swig_octave=OFF cmake command-line option. + +Like the matwrapped bindings before it, the new swig-generated octave +bindings currently do not have a number of the PLplot functions +wrapped (e.g., "plmap") that are needed by standard example 19. +However, because of the power of swig we now have some confidence we +can solve this issue in the future. + +2.49 Documentation redone for our swig-generated Python and Octave bindings + +Through the docstring %feature, swig can generate documentation +strings for certain of the languages it supports (currently Python, +Octave, and Ruby). We have now removed all such hand-crafted swig +documentation data from bindings/swig-support/plplotcapi.i and +replaced it with generated documentation in the file +bindings/swig-support/swig_documentation.i. That file is generated +from doc/docbook/src/api.xml using the perl script +doc/docbook/bin/api2swigdoc.pl. The build system Unix target +"check_swig_documentation" now runs that script and compares results +with bindings/swig-support/swig_documentation.i in the source tree to +make sure that latter file is consistent with any changes that might +have occurred in doc/docbook/src/api.xml. + +The resulting Octave and Python user-documentation (obtained by 'help +<PLplot_command_name>' in Octave and 'print ("%s" % +<PLplot_command_name>.__doc__)' in Python is much more detailed than +what was available before using the hand-crafted documentation. If we +ever decided to generate PLplot bindings for Ruby with swig, this +high-quality user-documentation would be available for that language +as well. + +2.50 Support large polygons + Previous releases had an implicit limitation with respect to the number of vertices in a polygon. This was due to the use of statically defined arrays (to avoid allocating and freeing memory for each polygon This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2011-01-27 20:44:01
|
Revision: 11514 http://plplot.svn.sourceforge.net/plplot/?rev=11514&view=rev Author: airwin Date: 2011-01-27 20:27:42 +0000 (Thu, 27 Jan 2011) Log Message: ----------- Describe recent work with making PLplot constants available for both f77 and f95. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2011-01-27 19:03:39 UTC (rev 11513) +++ trunk/README.release 2011-01-27 20:27:42 UTC (rev 11514) @@ -194,6 +194,15 @@ example 23) or better yet, UTF-8 strings (e.g., "ε") to specify exactly what unicode glyph they want. +XX. As of release 5.9.8, the full set of PLplot constants have been +made available to our Fortran 95 users as part of the plplot module. +This means those users will have to remove any parameter statements +where they have previously defined the PLplot constants (whose names +typically start with "PL_" for themselves. For a complete list of the +affected constants, see the #defines in swig-support/plplotcapi.i +which are used internally to help generate the plplot module. See +also Index item 2.51 below. + INDEX -1. Important changes we should have mentioned in previous release announcements. @@ -209,6 +218,7 @@ 1.3 Octave bindings now implemented with swig 1.4 Documentation redone for our swig-generated Python and Octave bindings 1.5 Support large polygons +1.6 Complete set of PLplot parameters now available for Fortran 2. Changes relative to PLplot 5.8.0 (the previous stable release) @@ -265,6 +275,7 @@ 2.48 Octave bindings now implemented with swig 2.49 Documentation redone for our swig-generated Python and Octave bindings 2.50 Support large polygons +2.51 Complete set of PLplot parameters now available for Fortran -1. Important changes we should have mentioned in previous release announcements. @@ -381,6 +392,39 @@ are used and for large polygons new arrays are allocated and freed. This strategy has been applied to all relevant source files. +1.6 Complete set of PLplot parameters now available for Fortran + +The #defines in bindings/swig-support/plplotcapi.i (which are +consistent with those in include/plplot.h) define the complete set of +important PLplot constants (whose names typically start with "PL_"). +We have implemented automatic methods of transforming that complete +set of #defines into Fortran parameters that can be used from either +Fortran 77 or Fortran 95. + +For Fortran 77, the user must insert an + + include 'plplot_parameters.h' + +statement in every function/subroutine/main programme where he expects +to use PLplot constants (whose names typically start with "PL_". (See +examples/f77/*.fm4 for examples of this method). When compiling he +must also insert the appropriate -I option to find this file (in +bindings/f77/ in the source tree and currently in +$prefix/lib/fortran/include/plplot$version in the install tree +although that install location may be subject to change). Note, the +above method does not interfere with existing apps which have +necessarily been forced to define the needed PLplot constants for +themselves. But for future f77 use, the above statement is +more convenient and much less subject to error than a whole bunch of +parameter statements for the required constants. + +For Fortran 95, the complete set of parameters are made available as +part of the plplot module. So access to this complete set of +parameters is automatic wherever the "use plplot" statement is used. +This is extremely convenient for new Fortran 95 apps that use PLplot, +but, in general, changes will have to be made for existing apps. (See +announcement XX above for the details). + 2. Changes relative to PLplot 5.8.0 (the previous stable release) 2.1 All autotools-related files have now been removed @@ -1169,3 +1213,36 @@ that for small polygons, the original statically defined arrays are used and for large polygons new arrays are allocated and freed. This strategy has been applied to all relevant source files. + +2.51 Complete set of PLplot parameters now available for Fortran + +The #defines in bindings/swig-support/plplotcapi.i (which are +consistent with those in include/plplot.h) define the complete set of +important PLplot constants (whose names typically start with "PL_"). +We have implemented automatic methods of transforming that complete +set of #defines into Fortran parameters that can be used from either +Fortran 77 or Fortran 95. + +For Fortran 77, the user must insert an + + include 'plplot_parameters.h' + +statement in every function/subroutine/main programme where he expects +to use PLplot constants (whose names typically start with "PL_". (See +examples/f77/*.fm4 for examples of this method). When compiling he +must also insert the appropriate -I option to find this file (in +bindings/f77/ in the source tree and currently in +$prefix/lib/fortran/include/plplot$version in the install tree +although that install location may be subject to change). Note, the +above method does not interfere with existing apps which have +necessarily been forced to define the needed PLplot constants for +themselves. But for future f77 use, the above statement is +more convenient and much less subject to error than a whole bunch of +parameter statements for the required constants. + +For Fortran 95, the complete set of parameters are made available as +part of the plplot module. So access to this complete set of +parameters is automatic wherever the "use plplot" statement is used. +This is extremely convenient for new Fortran 95 apps that use PLplot, +but, in general, changes will have to be made for existing apps. (See +announcement XX above for the details). This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2011-03-15 19:13:16
|
Revision: 11627 http://plplot.svn.sourceforge.net/plplot/?rev=11627&view=rev Author: airwin Date: 2011-03-15 19:13:08 +0000 (Tue, 15 Mar 2011) Log Message: ----------- Announcement of const modifier API changes. This announcement anticipates the change Andrew intends to make for the C++ case that was discussed on list and also anticipates the soversion bump that should occur (because of the backwards-incompatible API change) for both libplplotd and libplplotcxxd as part of our release process. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2011-03-14 07:30:06 UTC (rev 11626) +++ trunk/README.release 2011-03-15 19:13:08 UTC (rev 11627) @@ -203,6 +203,46 @@ which are used internally to help generate the plplot module. See also Index item 2.51 below. +XXI. As of release 5.9.8 there has been widespread const modifier +changes in the API for libplplotd and libplplotcxxd. Those +backwards-incompatible API changes are indicated in the usual way by a +soversion bump in those two libraries which will force all apps and +libraries that depend on those two libraries to be rebuilt. + +Specifically, we have changed the following arguments in the C library +(libplplotd) case + +type * name1 ==> const type * name1 +type * name2 ==> const type ** name2 + +and the following arguments in the C++ library (libplplotcxxd) case + +type * name1 ==> const type * name1 +type * name1 ==> const type * const * name2 + +where name1 is the name of a singly dimensioned array whose values +are not changed internally by the PLplot libraries and +name2 is the name of a doubly dimensioned array whose values +are not changed internally by the PLplot libraries. + +The general documentation and safety justification for such const +modifier changes to our API is given in +http://www.cprogramming.com/tutorial/const_correctness.html. +Essentially, the above const modifier changes constitute our +guarantee that the associated arrays are not changed internally +by the PLplot libraries. + +Although it is necessary to rebuild all apps and libraries that depend +on libplplotd and/or libplplotcxxd, that rebuild should be possible +with unchanged source code without build errors in all cases. For C +apps and libraries (depending on libplplotd) there will be additional +build warnings due to a limitation in the C standard discussed at +http://c-faq.com/ansi/constmismatch.html unless all doubly dimensioned +arrays (but not singly dimensioned) are explicitly cast to (const type +**). However, such source code changes will not be necessary to avoid +warning messages for the C++ (libplplotcxxd) change because of the +double use of const in the above "const type * const * name2" change. + INDEX -1. Important changes we should have mentioned in previous release announcements. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2011-03-19 21:33:59
|
Revision: 11655 http://plplot.svn.sourceforge.net/plplot/?rev=11655&view=rev Author: airwin Date: 2011-03-19 21:33:53 +0000 (Sat, 19 Mar 2011) Log Message: ----------- Tweak plcolbar ==> plcolorbar. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2011-03-19 21:21:23 UTC (rev 11654) +++ trunk/README.release 2011-03-19 21:33:53 UTC (rev 11655) @@ -384,7 +384,7 @@ matwrap-generated Octave bindings. Accordingly, a swig-generated version of the Octave bindings has now been implemented that builds on the prior matwrapped bindings effort but also extends it with, e.g., -bindings for plstring, plstring3, pllegend, and plcolbar. These new +bindings for plstring, plstring3, pllegend, and plcolorbar. These new octave bindings (which now completely replace the prior matwrapped bindings) make it possible to run examples 4, 18, 26, and 33 (all of which have now have been updated to use those functions) and get @@ -1203,7 +1203,7 @@ matwrap-generated Octave bindings. Accordingly, a swig-generated version of the Octave bindings has now been implemented that builds on the prior matwrapped bindings effort but also extends it with, e.g., -bindings for plstring, plstring3, pllegend, and plcolbar. These new +bindings for plstring, plstring3, pllegend, and plcolorbar. These new octave bindings (which now completely replace the prior matwrapped bindings) make it possible to run examples 4, 18, 26, and 33 (all of which have now have been updated to use those functions) and get This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <hez...@us...> - 2011-04-09 17:22:09
|
Revision: 11691 http://plplot.svn.sourceforge.net/plplot/?rev=11691&view=rev Author: hezekiahcarty Date: 2011-04-09 17:22:02 +0000 (Sat, 09 Apr 2011) Log Message: ----------- Add notice of plarc API change to release notes Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2011-04-09 08:12:56 UTC (rev 11690) +++ trunk/README.release 2011-04-09 17:22:02 UTC (rev 11691) @@ -260,6 +260,7 @@ 1.4 Documentation redone for our swig-generated Python and Octave bindings 1.5 Support large polygons 1.6 Complete set of PLplot parameters now available for Fortran +1.7 Change to plarc API for rotation support 2. Changes relative to PLplot 5.8.0 (the previous stable release) @@ -463,6 +464,13 @@ but, in general, changes will have to be made for existing apps. (See announcement XX above for the details). +1.7 Change to plarc API + +The plarc API now has a rotation parameter which will eventually allow +for rotated arcs. PLplot does not currently support rotated arcs, but +the plarc function signature has been modified to avoid changing the API +when this functionality is added. + 2. Changes relative to PLplot 5.8.0 (the previous stable release) 2.1 All autotools-related files have now been removed This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2011-04-10 07:42:08
|
Revision: 11692 http://plplot.svn.sourceforge.net/plplot/?rev=11692&view=rev Author: airwin Date: 2011-04-10 07:42:00 +0000 (Sun, 10 Apr 2011) Log Message: ----------- Rearrange official notices so that they are in reverse release order. That puts the official notices for the latest release in the most prominent position at the top of the stack. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2011-04-09 17:22:02 UTC (rev 11691) +++ trunk/README.release 2011-04-10 07:42:00 UTC (rev 11692) @@ -17,177 +17,19 @@ Official Notices for Users. -I. As of release 5.9.1 we have removed our previously deprecated -autotools-based build system. Instead, use the CMake-based build system -following the directions in the INSTALL file. +(5.9.8) For unicode-aware devices we now follow what is done for the +Hershey font case for epsilon, theta, and phi. This means the #ge, +#gh, and #gf escapes now give users the Greek lunate epsilon, the +ordinary Greek lower case theta, and the Greek symbol phi for Unicode +fonts just like has occurred since the dawn of PLplot history for the +Hershey font case. Previously these legacy escapes were assigned to +ordinary Greek lower-case epsilon, the Greek symbol theta (= script +theta), and the ordinary Greek lower case phi for unicode fonts +inconsistently with what occurred for Hershey fonts. This change gets +rid of this inconsistency, that is the #g escapes should give the best +unicode approximation to the Hershey glyph result that is possible for +unicode-aware devices. -II. As of release 5.9.1 we no longer support Octave-2.1.73 which has a -variety of run-time issues in our tests of the Octave examples on different -platforms. In contrast our tests show we get good run-time results with all -our Octave examples for Octave-3.0.1. Also, that is the recommended stable -version of Octave at http://www.gnu.org/software/octave/download.html so -that is the only version of Octave we support at this time. - -III. As of release 5.9.1 we have decided for consistency sake to change the -PLplot stream variables plsc->vpwxmi, plsc->vpwxma, plsc->vpwymi, and -plsc->vpwyma and the results returned by plgvpw to reflect the exact window -limit values input by users using plwind. Previously to this change, the -stream variables and the values returned by plgvpw reflected the internal -slightly expanded range of window limits used by PLplot so that the user's -specified limits would be on the graph. Two users noted this slight -difference, and we agree with them it should not be there. Note that -internally, PLplot still uses the expanded ranges so most users results will -be identical. However, you may notice some small changes to your plot -results if you use these stream variables directly (only possible in C/C++) -or use plgvpw. - -IV. As of release 5.9.2 we have set HAVE_PTHREAD (now called -PL_HAVE_PTHREAD as of release 5.9.8) to ON by default for all -platforms other than Darwin. Darwin will follow later once it appears -the Apple version of X supports it. - -V. As of release 5.9.3 our build system requires CMake version 2.6.0 or -higher. - -VI. As of release 5.9.3 we have deprecated the gcw device driver and the -related gnome2 and pygcw bindings since these are essentially unmaintained. -For example, the gcw device and associated bindings still depends on the -plfreetype approach for accessing unicode fonts which has known issues -(inconsistent text offsets, inconvenient font setting capabilities, and -incorrect rendering of CTL languages). To avoid these issues we advise -using the xcairo device and the externally supplied XDrawable or Cairo -context associated with the xcairo device and the extcairo device (see -examples/c/README.cairo) instead. If you still absolutely must use -dev gcw -or the related gnome2 or pygcw bindings despite the known problems, then -they can still be accessed by setting PLD_gcw, ENABLE_gnome2, and/or -ENABLE_pygcw to ON. -N.B. This announcement has been superseded by the subsequent retirement -of gcw, gnome2, and pygcw, see announcement XVII. - -VII. As of release 5.9.3 we have deprecated the gd device driver which -implements the png, jpeg, and gif devices. This device driver is -essentially unmaintained. For example, it still depends on the plfreetype -approach for accessing unicode fonts which has known issues (inconsistent -text offsets, inconvenient font setting capabilities, and incorrect -rendering of CTL languages). To avoid these issues for PNG format, we -advise using the pngcairo or pngqt devices. To avoid these issues for the -JPEG format, we advise using the jpgqt device. PNG is normally considered a -better raster format than GIF, but if you absolutely require GIF format, we -advise using the pngcairo or pngqt devices and then downgrading the results -to the GIF format using the ImageMagick "convert" application. For those -platforms where libgd (the dependency of the gd device driver) is accessible -while the required dependencies of the cairo and/or qt devices are not -accessible, you can still use these deprecated devices by setting PLD_png, -PLD_jpeg, or PLD_gif to ON. - -VIII. As of release 5.9.3 we have re-enabled the tk, itk, and itcl components -of PLplot by default that were disabled by default as of release 5.9.1 due -to segfaults. The cause of the segfaults was a bug (now fixed) in how -pthread support was implemented for the Tk-related components of PLplot. - -IX. As of release 5.9.4 we have deprecated the pbm device driver (containing -the pbm device) because glibc detects a catastrophic double free. - -X. As of release 5.9.5 we have removed pyqt3 access to PLplot and -replaced it by pyqt4 access to PLplot (see details below). - -XI. As of release 5.9.5 the only method of specifying a non-default compiler -(and associated compiler options) that we support is the environment -variable approach, e.g., - -export CC='gcc -g -fvisibility=hidden' -export CXX='g++ -g -fvisibility=hidden' -export FC='gfortran -g -fvisibility=hidden' - -All other CMake methods of specifying a non-default compiler and associated -compiler options will not be supported until CMake bug 9220 is fixed, see -discussion below of the soft-landing re-implementation for details. - -XII. As of release 5.9.5 we have retired the hpgl driver (containing the -hp7470, hp7580, and lj_hpgl devices), the impress driver (containing the imp -device), the ljii driver (containing the ljii and ljiip devices), and the -tek driver (containing the conex, mskermit, tek4107, tek4107f, tek4010, -tek4010f, versaterm, vlt, and xterm devices). Retirement means we have -removed the build options which would allow these devices to build and -install. Recent tests have shown a number of run-time issues (hpgl, -impress, and ljii) or build-time issues (tek) with these devices, and as far -as we know there is no more user interest in them. Therefore, we have -decided to retire these devices rather than fix them. - -XIII. As of release 5.9.6 we have retired the pbm driver containing the pbm -(actually portable pixmap) file device. This device is quite primitive and -poorly maintained. It ignores unicode fonts (i.e., uses the Hershey font -fallback), falls back to ugly software fills, doesn't support alpha -transparency, etc. It also has a serious run-time issue with example 2 -(double free detected by glibc) which probably indicates some fundamental -issue with the 100 colours in cmap0 for that example. For those who really -need portable pixmap results, we suggest using the ImageMagick convert -programme, e.g., "convert examples/x24c01.pngqt test.ppm" or "convert -examples/x24c01.pngcairo test.ppm" to produce good-looking portable pixmap -results from our best png device results. - -XIV. As of release 5.9.6 we have retired the linuxvga driver -containing the linuxvga interactive device. This device is quite -primitive, difficult to test, and poorly maintained. It ignores -unicode fonts (i.e., uses the Hershey font fallback), falls back to -ugly software fills, doesn't support alpha transparency, etc. It is -Linux only, can only be run as root, and svgalib (the library used by -linuxsvga) is not supported by some mainstream (e.g., Intel) chipsets. -All of these characteristics make it difficult to even test this -device much less use it for anything serious. Finally, it has had a -well-known issue for years (incorrect colours) which has never been -fixed indicating nobody is interested in maintaining this device. - -XV. As of release 5.9.6 we have retired our platform support of djgpp -that used to reside in sys/dos/djgpp. The developer (Andrew Roach) -who used to maintain those support files for djgpp feels that the -djgpp platform is no longer actively developed, and he no longer uses -djgpp himself. - -XVI. As of release 5.9.6 plpoin results for ascii codes 92, 94, and 95 -are changed from centred dot, degree symbol, and centred dot glyphs to -the correct backslash, caret, and underscore glyphs that are -associated with those ascii indices. This change is consistent with -the documentation of plpoin and solves a long-standing issue with -backslash, caret, and underscore ascii characters in character strings -used for example by pl[mp]tex. Those who need access to a centred dot -with plpoin should use index 1. The degree symbol is no longer -accessible with plpoin, but it is available in ordinary text input to -PLplot as Hershey escape "#(718)", where 718 is the Hershey index of -the degree symbol, unicode escape "#[0x00B0]" where 0x00B0 is the -unicode index for the degree symbol or direct UTF8 unicode string "°". - -XVII. As of release 5.9.6 we have retired the gcw device driver and -the related gnome2 and pygcw bindings since these are unmaintained and -there are good replacements. These components of PLplot were -deprecated as of release 5.9.3. A good replacement for the gcw device -is either the xcairo or qtwidget device. A good replacement for the -gnome2 bindings is the externally supplied XDrawable or Cairo context -associated with the xcairo device and the extcairo device (see -examples/c/README.cairo). A good replacement for pygcw is our new -pyqt4 bindings for PLplot. - -XVIII. As of release 5.9.6 we have deprecated support for the python -Numeric array extensions. Numeric is no longer maintained and users -of Numeric are advised to migrate to numpy. Numpy has been the standard -for PLplot for some time. If numpy is not present PLplot will now -disable python by default. If you still require Numeric support in the -short term then set USE_NUMERIC to ON in cmake. The PLplot support -for Numeric will be dropped in a future release. - -XIX. As of release 5.9.8, and for unicode-aware devices we now follow -what is done for the Hershey font case for epsilon, theta, and phi. -This means the #ge, #gh, and #gf escapes now give users the Greek -lunate epsilon, the ordinary Greek lower case theta, and the Greek -symbol phi for Unicode fonts just like has occurred since the dawn of -PLplot history for the Hershey font case. Previously these legacy escapes -were assigned to ordinary Greek lower-case epsilon, the Greek symbol theta -(= script theta), and the ordinary Greek lower case phi for unicode -fonts inconsistently with what occurred for Hershey fonts. This change -gets rid of this inconsistency, that is the #g escapes should give -the best unicode approximation to the Hershey glyph result that is possible -for unicode-aware devices. - In general we encourage users of unicode-aware devices who might dislike the Greek glyph Hershey-lookalike choices they get with the legacy #g escapes to use instead either PLplot unicode escapes (e.g., @@ -195,20 +37,20 @@ example 23) or better yet, UTF-8 strings (e.g., "ε") to specify exactly what unicode glyph they want. -XX. As of release 5.9.8, the full set of PLplot constants have been -made available to our Fortran 95 users as part of the plplot module. -This means those users will have to remove any parameter statements -where they have previously defined the PLplot constants (whose names -typically start with "PL_" for themselves. For a complete list of the -affected constants, see the #defines in swig-support/plplotcapi.i -which are used internally to help generate the plplot module. See -also Index item 2.51 below. +(5.9.8) The full set of PLplot constants have been made available to +our Fortran 95 users as part of the plplot module. This means those +users will have to remove any parameter statements where they have +previously defined the PLplot constants (whose names typically start +with "PL_" for themselves. For a complete list of the affected +constants, see the #defines in swig-support/plplotcapi.i which are +used internally to help generate the plplot module. See also Index +item 2.51 below. -XXI. As of release 5.9.8 there has been widespread const modifier -changes in the API for libplplotd and libplplotcxxd. Those -backwards-incompatible API changes are indicated in the usual way by a -soversion bump in those two libraries which will force all apps and -libraries that depend on those two libraries to be rebuilt. +(5.9.8) There has been widespread const modifier changes in the API +for libplplotd and libplplotcxxd. Those backwards-incompatible API +changes are indicated in the usual way by a soversion bump in those +two libraries which will force all apps and libraries that depend on +those two libraries to be rebuilt. Specifically, we have changed the following arguments in the C library (libplplotd) case @@ -221,17 +63,17 @@ type * name1 ==> const type * name1 type * name1 ==> const type * const * name2 -where name1 is the name of a singly dimensioned array whose values -are not changed internally by the PLplot libraries and -name2 is the name of a doubly dimensioned array whose values -are not changed internally by the PLplot libraries. +where name1 is the name of a singly dimensioned array whose values are +not changed internally by the PLplot libraries and name2 is the name +of a doubly dimensioned array whose values are not changed internally +by the PLplot libraries. The general documentation and safety justification for such const modifier changes to our API is given in http://www.cprogramming.com/tutorial/const_correctness.html. -Essentially, the above const modifier changes constitute our -guarantee that the associated arrays are not changed internally -by the PLplot libraries. +Essentially, the above const modifier changes constitute our guarantee +that the associated arrays are not changed internally by the PLplot +libraries. Although it is necessary to rebuild all apps and libraries that depend on libplplotd and/or libplplotcxxd, that rebuild should be possible @@ -244,6 +86,166 @@ warning messages for the C++ (libplplotcxxd) change because of the double use of const in the above "const type * const * name2" change. +(5.9.6) We have retired the pbm driver containing the pbm (actually +portable pixmap) file device. This device is quite primitive and +poorly maintained. It ignores unicode fonts (i.e., uses the Hershey +font fallback), falls back to ugly software fills, doesn't support +alpha transparency, etc. It also has a serious run-time issue with +example 2 (double free detected by glibc) which probably indicates +some fundamental issue with the 100 colours in cmap0 for that +example. For those who really need portable pixmap results, we suggest +using the ImageMagick convert programme, e.g., "convert +examples/x24c01.pngqt test.ppm" or "convert examples/x24c01.pngcairo +test.ppm" to produce good-looking portable pixmap results from our +best png device results. + +(5.9.6) We have retired the linuxvga driver containing the linuxvga +interactive device. This device is quite primitive, difficult to +test, and poorly maintained. It ignores unicode fonts (i.e., uses the +Hershey font fallback), falls back to ugly software fills, doesn't +support alpha transparency, etc. It is Linux only, can only be run as +root, and svgalib (the library used by linuxsvga) is not supported by +some mainstream (e.g., Intel) chipsets. All of these characteristics +make it difficult to even test this device much less use it for +anything serious. Finally, it has had a well-known issue for years +(incorrect colours) which has never been fixed indicating nobody is +interested in maintaining this device. + +(5.9.6) We have retired our platform support of djgpp that used to +reside in sys/dos/djgpp. The developer (Andrew Roach) who used to +maintain those support files for djgpp feels that the djgpp platform +is no longer actively developed, and he no longer uses djgpp himself. + +(5.9.6) We have changed plpoin results for ascii codes 92, 94, and 95 +from centred dot, degree symbol, and centred dot glyphs to the correct +backslash, caret, and underscore glyphs that are associated with those +ascii indices. This change is consistent with the documentation of +plpoin and solves a long-standing issue with backslash, caret, and +underscore ascii characters in character strings used for example by +pl[mp]tex. Those who need access to a centred dot with plpoin should +use index 1. The degree symbol is no longer accessible with plpoin, +but it is available in ordinary text input to PLplot as Hershey escape +"#(718)", where 718 is the Hershey index of the degree symbol, unicode +escape "#[0x00B0]" where 0x00B0 is the unicode index for the degree +symbol or direct UTF8 unicode string "°". + +(5.9.6) We have retired the gcw device driver and the related gnome2 +and pygcw bindings since these are unmaintained and there are good +replacements. These components of PLplot were deprecated as of +release 5.9.3. A good replacement for the gcw device is either the +xcairo or qtwidget device. A good replacement for the gnome2 bindings +is the externally supplied XDrawable or Cairo context associated with +the xcairo device and the extcairo device (see +examples/c/README.cairo). A good replacement for pygcw is our new +pyqt4 bindings for PLplot. + +(5.9.6) We have deprecated support for the python Numeric array +extensions. Numeric is no longer maintained and users of Numeric are +advised to migrate to numpy. Numpy has been the standard for PLplot +for some time. If numpy is not present PLplot will now disable python +by default. If you still require Numeric support in the short term +then set USE_NUMERIC to ON in cmake. The PLplot support for Numeric +will be dropped in a future release. + +(5.9.5) We have removed pyqt3 access to PLplot and replaced it by +pyqt4 access to PLplot (see details below). + +(5.9.5) The only method of specifying a non-default compiler (and +associated compiler options) that we support is the environment +variable approach, e.g., + +export CC='gcc -g -fvisibility=hidden' +export CXX='g++ -g -fvisibility=hidden' +export FC='gfortran -g -fvisibility=hidden' + +All other CMake methods of specifying a non-default compiler and +associated compiler options will not be supported until CMake bug 9220 +is fixed, see discussion below of the soft-landing re-implementation +for details. + +(5.9.5) We have retired the hpgl driver (containing the hp7470, +hp7580, and lj_hpgl devices), the impress driver (containing the imp +device), the ljii driver (containing the ljii and ljiip devices), and +the tek driver (containing the conex, mskermit, tek4107, tek4107f, +tek4010, tek4010f, versaterm, vlt, and xterm devices). Retirement +means we have removed the build options which would allow these +devices to build and install. Recent tests have shown a number of +run-time issues (hpgl, impress, and ljii) or build-time issues (tek) +with these devices, and as far as we know there is no more user +interest in them. Therefore, we have decided to retire these devices +rather than fix them. + +(5.9.4) We have deprecated the pbm device driver (containing the pbm +device) because glibc detects a catastrophic double free. + +(5.9.3) Our build system requires CMake version 2.6.0 or higher. + +(5.9.3) We have deprecated the gcw device driver and the related +gnome2 and pygcw bindings since these are essentially unmaintained. +For example, the gcw device and associated bindings still depends on +the plfreetype approach for accessing unicode fonts which has known +issues (inconsistent text offsets, inconvenient font setting +capabilities, and incorrect rendering of CTL languages). To avoid +these issues we advise using the xcairo device and the externally +supplied XDrawable or Cairo context associated with the xcairo device +and the extcairo device (see examples/c/README.cairo) instead. If you +still absolutely must use -dev gcw or the related gnome2 or pygcw +bindings despite the known problems, then they can still be accessed +by setting PLD_gcw, ENABLE_gnome2, and/or ENABLE_pygcw to ON. + +(5.9.3) We have deprecated the gd device driver which implements the +png, jpeg, and gif devices. This device driver is essentially +unmaintained. For example, it still depends on the plfreetype approach +for accessing unicode fonts which has known issues (inconsistent text +offsets, inconvenient font setting capabilities, and incorrect +rendering of CTL languages). To avoid these issues for PNG format, we +advise using the pngcairo or pngqt devices. To avoid these issues for +the JPEG format, we advise using the jpgqt device. PNG is normally +considered a better raster format than GIF, but if you absolutely +require GIF format, we advise using the pngcairo or pngqt devices and +then downgrading the results to the GIF format using the ImageMagick +"convert" application. For those platforms where libgd (the +dependency of the gd device driver) is accessible while the required +dependencies of the cairo and/or qt devices are not accessible, you +can still use these deprecated devices by setting PLD_png, PLD_jpeg, +or PLD_gif to ON. + +(5.9.3) We have re-enabled the tk, itk, and itcl components of PLplot +by default that were disabled by default as of release 5.9.1 due to +segfaults. The cause of the segfaults was a bug (now fixed) in how +pthread support was implemented for the Tk-related components of +PLplot. + +(5.9.2) We have set HAVE_PTHREAD (now called PL_HAVE_PTHREAD as of +release 5.9.8) to ON by default for all platforms other than Darwin. +Darwin will follow later once it appears the Apple version of X +supports it. + +(5.9.1) We have removed our previously deprecated autotools-based +build system. Instead, use the CMake-based build system following the +directions in the INSTALL file. + +(5.9.1) We no longer support Octave-2.1.73 which has a variety of +run-time issues in our tests of the Octave examples on different +platforms. In contrast our tests show we get good run-time results +with all our Octave examples for Octave-3.0.1. Also, that is the +recommended stable version of Octave at +http://www.gnu.org/software/octave/download.html so that is the only +version of Octave we support at this time. + +(5.9.1) We have decided for consistency sake to change the PLplot +stream variables plsc->vpwxmi, plsc->vpwxma, plsc->vpwymi, and +plsc->vpwyma and the results returned by plgvpw to reflect the exact +window limit values input by users using plwind. Previously to this +change, the stream variables and the values returned by plgvpw +reflected the internal slightly expanded range of window limits used +by PLplot so that the user's specified limits would be on the graph. +Two users noted this slight difference, and we agree with them it +should not be there. Note that internally, PLplot still uses the +expanded ranges so most users results will be identical. However, you +may notice some small changes to your plot results if you use these +stream variables directly (only possible in C/C++) or use plgvpw. + INDEX -1. Important changes we should have mentioned in previous release announcements. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <hez...@us...> - 2011-04-10 20:59:28
|
Revision: 11693 http://plplot.svn.sourceforge.net/plplot/?rev=11693&view=rev Author: hezekiahcarty Date: 2011-04-10 20:59:22 +0000 (Sun, 10 Apr 2011) Log Message: ----------- Move the plarc API change to a more appropriate spot; Announce plarc plarc did not previously have an entry in the "changes since 5.8.0" section of README.release. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2011-04-10 07:42:00 UTC (rev 11692) +++ trunk/README.release 2011-04-10 20:59:22 UTC (rev 11693) @@ -86,6 +86,12 @@ warning messages for the C++ (libplplotcxxd) change because of the double use of const in the above "const type * const * name2" change. +(5.9.8) The plarc API has changed in release 5.9.8. The plarc API now +has a rotation parameter which will eventually allow for rotated arcs. +PLplot does not currently support rotated arcs, but the plarc function +signature has been modified to avoid changing the API when this +functionality is added. + (5.9.6) We have retired the pbm driver containing the pbm (actually portable pixmap) file device. This device is quite primitive and poorly maintained. It ignores unicode fonts (i.e., uses the Hershey @@ -262,7 +268,6 @@ 1.4 Documentation redone for our swig-generated Python and Octave bindings 1.5 Support large polygons 1.6 Complete set of PLplot parameters now available for Fortran -1.7 Change to plarc API for rotation support 2. Changes relative to PLplot 5.8.0 (the previous stable release) @@ -320,6 +325,7 @@ 2.49 Documentation redone for our swig-generated Python and Octave bindings 2.50 Support large polygons 2.51 Complete set of PLplot parameters now available for Fortran +2.52 The plarc function has been added -1. Important changes we should have mentioned in previous release announcements. @@ -466,13 +472,6 @@ but, in general, changes will have to be made for existing apps. (See announcement XX above for the details). -1.7 Change to plarc API - -The plarc API now has a rotation parameter which will eventually allow -for rotated arcs. PLplot does not currently support rotated arcs, but -the plarc function signature has been modified to avoid changing the API -when this functionality is added. - 2. Changes relative to PLplot 5.8.0 (the previous stable release) 2.1 All autotools-related files have now been removed @@ -1291,3 +1290,8 @@ This is extremely convenient for new Fortran 95 apps that use PLplot, but, in general, changes will have to be made for existing apps. (See announcement XX above for the details). + +2.52 The plarc function has been added + +The plarc function allows drawing filled and outlined arcs in PLplot. +Standard example 3 uses plarc. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2011-10-09 21:54:05
|
Revision: 11943 http://plplot.svn.sourceforge.net/plplot/?rev=11943&view=rev Author: airwin Date: 2011-10-09 21:53:58 +0000 (Sun, 09 Oct 2011) Log Message: ----------- Reorganize in preparation for the forthcoming 5.9.9 release including removal of all the remarks about changes relative to the 5.9.7 release, official notices concerning the broken build fixes for Windows, and the disabling of ocaml by default. Also add detailed listing of all the testing done for this release. Spell check. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2011-10-09 19:58:44 UTC (rev 11942) +++ trunk/README.release 2011-10-09 21:53:58 UTC (rev 11943) @@ -15,8 +15,94 @@ (LGPL), and the disclaimer of all warranties, given in the COPYING.LIB file. -Official Notices for Users. +INDEX +OFFICIAL NOTICES FOR USERS + +CHANGES + +-1. Important changes we should have mentioned in previous release announcements. + +-1.1 Add full bindings and examples for the D language. + +0. Tests made for release 5.9.9 + +1. Changes relative to PLplot 5.9.8 (the previous development release) + +2. Changes relative to PLplot 5.8.0 (the previous stable release) + +2.1 All autotools-related files have now been removed +2.2 Build system bug fixes +2.3 Build system improvements +2.4 Implement build-system infrastructure for installed Ada bindings and +examples +2.5 Code cleanup +2.6 Date / time labels for axes +2.7 Alpha value support +2.8 New PLplot functions +2.9 External libLASi library improvements affecting our psttf device +2.10 Improvements to the cairo driver family +2.11 wxWidgets driver improvements +2.12 pdf driver improvements +2.13 svg driver improvements +2.14 Ada language support +2.15 OCaml language support +2.16 Perl/PDL language support +2.17 Update to various language bindings +2.18 Update to various examples +2.19 Extension of our test framework +2.20 Rename test subdirectory to plplot_test +2.21 Website support files updated +2.22 Internal changes to function visibility +2.23 Dynamic driver support in Windows +2.24 Documentation updates +2.25 libnistcd (a.k.a. libcd) now built internally for -dev cgm +2.26 get-drv-info now changed to test-drv-info +2.27 Text clipping now enabled by default for the cairo devices +2.28 A powerful qt device driver has been implemented +2.29 The PLplot API is now accessible from Qt GUI applications +2.30 NaN / Inf support for some PLplot functions +2.31 Various bug fixes +2.32 Cairo driver improvements +2.33 PyQt changes +2.34 Color Palettes +2.35 Re-implementation of a "soft landing" when a bad/missing compiler is +detected +2.36 Make PLplot aware of LC_NUMERIC locale +2.37 Linear gradients have been implemented +2.38 Cairo Windows driver implemented +2.39 Custom axis labeling implemented +2.40 Universal coordinate transform implemented +2.41 Support for arbitrary storage of 2D user data +2.42 Font improvements +2.42 Alpha value support for plotting in memory. +2.43 Add a Qt device for in memory plotting. +2.44 Add discrete legend capability. +2.45 Add full bindings and examples for the D language. +2.46 The plstring and plstring3 functions have been added +2.47 The pllegend API has been finalized +2.48 Octave bindings now implemented with swig +2.49 Documentation redone for our swig-generated Python and Octave bindings +2.50 Support large polygons +2.51 Complete set of PLplot parameters now available for Fortran +2.52 The plarc function has been added + +OFFICIAL NOTICES FOR USERS + +(5.9.9) This is a quick release to deal with two broken build issues +that were recently discovered for our Windows platform. Windows users should +avoid 5.9.8 because of these problems for that release, and instead use +5.9.9 which has been heavily tested on a number of platforms including +Windows, see "Tests made for release 5.9.9" below. + +(5.9.9) During our extensive testing of this release we noticed a segfault +with the OCaml bindings/examples. Follow up with valgrind indicated +some widespread memory management issues with our OCaml +bindings/examples. Therefore, we have disabled OCaml by default for +this release and hope to reinstate it again just as soon as we figure +out these issues. If you want to try it anyway for this release +specify the -DENABLE_ocaml=ON cmake option. + (5.9.8) For unicode-aware devices we now follow what is done for the Hershey font case for epsilon, theta, and phi. This means the #ge, #gh, and #gf escapes now give users the Greek lunate epsilon, the @@ -252,79 +338,12 @@ may notice some small changes to your plot results if you use these stream variables directly (only possible in C/C++) or use plgvpw. -INDEX +CHANGES -1. Important changes we should have mentioned in previous release announcements. -1.1 Add full bindings and examples for the D language. -0. Tests made for release 5.9.9 - -1. Changes relative to PLplot 5.9.8 (the previous development release) - - -2. Changes relative to PLplot 5.8.0 (the previous stable release) - -2.1 All autotools-related files have now been removed -2.2 Build system bug fixes -2.3 Build system improvements -2.4 Implement build-system infrastructure for installed Ada bindings and -examples -2.5 Code cleanup -2.6 Date / time labels for axes -2.7 Alpha value support -2.8 New PLplot functions -2.9 External libLASi library improvements affecting our psttf device -2.10 Improvements to the cairo driver family -2.11 wxWidgets driver improvements -2.12 pdf driver improvements -2.13 svg driver improvements -2.14 Ada language support -2.15 OCaml language support -2.16 Perl/PDL language support -2.17 Update to various language bindings -2.18 Update to various examples -2.19 Extension of our test framework -2.20 Rename test subdirectory to plplot_test -2.21 Website support files updated -2.22 Internal changes to function visibility -2.23 Dynamic driver support in Windows -2.24 Documentation updates -2.25 libnistcd (a.k.a. libcd) now built internally for -dev cgm -2.26 get-drv-info now changed to test-drv-info -2.27 Text clipping now enabled by default for the cairo devices -2.28 A powerful qt device driver has been implemented -2.29 The PLplot API is now accessible from Qt GUI applications -2.30 NaN / Inf support for some PLplot functions -2.31 Various bug fixes -2.32 Cairo driver improvements -2.33 PyQt changes -2.34 Color Palettes -2.35 Re-implementation of a "soft landing" when a bad/missing compiler is -detected -2.36 Make PLplot aware of LC_NUMERIC locale -2.37 Linear gradients have been implemented -2.38 Cairo Windows driver implemented -2.39 Custom axis labeling implemented -2.40 Universal coordinate transform implemented -2.41 Support for arbitrary storage of 2D user data -2.42 Font improvements -2.42 Alpha value support for plotting in memory. -2.43 Add a Qt device for in memory plotting. -2.44 Add discrete legend capability. -2.45 Add full bindings and examples for the D language. -2.46 The plstring and plstring3 functions have been added -2.47 The pllegend API has been finalized -2.48 Octave bindings now implemented with swig -2.49 Documentation redone for our swig-generated Python and Octave bindings -2.50 Support large polygons -2.51 Complete set of PLplot parameters now available for Fortran -2.52 The plarc function has been added - --1. Important changes we should have mentioned in previous release announcements. - --1.1 Add full bindings and examples for the D language. - As of release 5.9.5 we added full bindings and examples for the D language. The results for the D examples are generally consistent with the corresponding C examples which helps to verify the D @@ -340,132 +359,74 @@ good). -0. Tests made for release 5.9.8 +0. Tests made for release 5.9.9 -See -http://www.miscdebris.net/plplot_wiki/index.php?title=Testing_PLplot#Testing_Reports -for a summary table of all testing done for PLplot-5.9.8. +* (Alan W. Irwin) A fully loaded (all Linux bindings other than PDL, + all Linux device drivers including our qt and cairo device drivers) Debian Squeeze + Linux platform gave a good result for the + scripts/comprehensive_test.sh script. This script runs 7 major + tests for each of our three principal build configurations (shared + library/dynamic device drivers, shared libraries/nondynamic device + drivers, static libraries/nondynamic device drivers). Those 7 tests + are ctest and the test_noninteractive and test_interactive targets + in the build tree, the test_noninteractive and test_interactive + targets configured with CMake in the installed examples tree, and + the traditional (MakeFile + pkg-config) test_noninteractive and + test_interactive targets in the installed examples tree. +* (Andrew Ross) For one Ubuntu platform the test_noninteractive and + test_interactive targets for the shared libraries and dynamic + drivers case gave good results. This was for a fully loaded + platform including our qt and cairo device drivers. -1. Changes relative to PLplot 5.9.7 (the previous development release) +* (Hezekiah M. Carty) scripts/comprehensive_test.sh failed on a Ubuntu + Linux platform because of a segfault in one of the qt devices. We + have tentatively ascribed this issue to issues with the Qt4 stack of + libraries on that platform since this bad qt result contrasts with + the good qt result on the previous two Linux platforms. -1.1 The plstring and plstring3 functions have been added +* (Arjen Markus) MinGW/MSYS installed on a lightly loaded (at least + compared to Linux tests) Windows XP system gives good results for + the test_noninteractive target in the build tree for the shared + library/dynamic device drivers case. -The plstring function largely supersedes plpoin and plsym -because many(!) more glyphs are accessible with plstring. The glyph -is specified with a PLplot user string. As with plmtex and plptex, -the user string can contain FCI escapes to determine the font, UTF-8 -code to determine the glyph or else PLplot escapes for Hershey or -unicode text to determine the glyph. Standard examples 4 and 26 use -plstring. +* (Arjen Markus) The combination of Microsoft Visual C/C++ version 9.0 + and Intel Fortran compilers installed on a lightly loaded Windows XP + system gives good results for the "all" target for the shared + library/dynamic device drivers case. That target just builds the + software. In addition, some run-time testing was done by hand with + no sign of any run-time trouble. -The plstring3 function largely supersedes plpoin3 for the same (access -to many more glyphs) reasons. Standard example 18 uses plstring3. +* (Jerry Bauck) Mac OS X 10.6.8 (Snow Leopard) platform with Ada + bindings and good coverage of devices (e.g., qt and cairo) but + lightly loaded with regard to non-Ada bindings give fairly good + results for ctest and the test_noninteractive target for the shared + library/dynamic device drivers case. All tests passed including qt + and cairo device driver tests, but when looking at detailed results + some missing circular symbol issues were discovered for the pscairo + results. We don't understand this issue because the cairo devices + give both superb and reliable results on our Linux platforms. The + cairo device driver depends on a subset (e.g., pango and cairo) of + the GTK+ stack of libraries. These results were obtained for GTK+ + version 2.18.5. -1.2 The pllegend API has been finalized +* (Werner Smekal) Mac OS X 10.7.1, XCode 4.1 platform that is lightly + loaded (e.g., GTK+ but no Qt4) gave mixed results for ctest and the + test_noninteractive target for the shared library/dynamic device + drivers case. The build worked without issues, and also everything + but cairo devices at run time. However, all cairo device results + had major run-time errors (e.g., segfaults). In this case the GTK+ + library was newer than we have tested before (version 2.24 from the + Homebrew packaging effort as compared to 2.21 that gives such good + results on Linux) so there may be a mismatch between our cairo + device driver and this newer version of GTK+ that needs to be sorted + out. -The function pllegend allows users to create a discrete plot legend -with a plotted colored box, line, and/or line of symbols for each -annotated legend entry. The pllegend function was first made -available for 5.9.7. Due to feedback from early adopters of pllegend, -we have now added substantially to the pllegend capabilities. and we -now believe pllegend is ready for prime time. The pllegend -capabilities are documented in our docbook documentation and -demonstrated in standard examples 4, 26, and 33. +1. Changes relative to PLplot 5.9.8 (the previous development release) -N.B. The current set of changes required a backwards-incompatible -change to the pllegend API. This requires users who tried this new -functionality for 5.9.7 to reprogramme their pllegend calls. Since -the pllegend API was labelled experimental for 5.9.7, we will not be -bumping the soversions of the affected PLplot libraries. +No notable new features. This is a bug fix release. See the above +announcements. -1.3 Octave bindings now implemented with swig - -Octave is a powerful platform that demands a first-class PLplot -solution, but we were finding it difficult to realize that goal -because we were running up against limitations of the previous -matwrap-generated Octave bindings. Accordingly, a swig-generated -version of the Octave bindings has now been implemented that builds on -the prior matwrapped bindings effort but also extends it with, e.g., -bindings for plstring, plstring3, pllegend, and plcolorbar. These new -octave bindings (which now completely replace the prior matwrapped -bindings) make it possible to run examples 4, 18, 26, and 33 (all of -which have now have been updated to use those functions) and get -consistent results with the corresponding C examples. - -Like the matwrapped bindings before it, the new swig-generated octave -bindings currently do not have a number of the PLplot functions -wrapped (e.g., "plmap") that are needed by standard example 19. -However, because of the power of swig we now have some confidence we -can solve this issue in the future. - -1.4 Documentation redone for our swig-generated Python and Octave bindings - -Through the docstring %feature, swig can generate documentation -strings for certain of the languages it supports (currently Python, -Octave, and Ruby). We have now removed all such hand-crafted swig -documentation data from bindings/swig-support/plplotcapi.i and -replaced it with generated documentation in the file -bindings/swig-support/swig_documentation.i. That file is generated -from doc/docbook/src/api.xml using the perl script -doc/docbook/bin/api2swigdoc.pl. The build system Unix target -"check_swig_documentation" now runs that script and compares results -with bindings/swig-support/swig_documentation.i in the source tree to -make sure that latter file is consistent with any changes that might -have occurred in doc/docbook/src/api.xml. - -The resulting Octave and Python user-documentation (obtained by 'help -<PLplot_command_name>' in Octave and 'print ("%s" % -<PLplot_command_name>.__doc__)' in Python is much more detailed than -what was available before using the hand-crafted documentation. If we -ever decided to generate PLplot bindings for Ruby with swig, this -high-quality user-documentation would be available for that language -as well. - -1.5 Support large polygons - -Previous releases had an implicit limitation with respect to the -number of vertices in a polygon. This was due to the use of statically -defined arrays (to avoid allocating and freeing memory for each polygon -to be drawn). Jos\xE9 Luis Garc\xEDa Pallero found this limitation and -provided patches to eliminate this limitation. The strategy is -that for small polygons, the original statically defined arrays -are used and for large polygons new arrays are allocated and freed. -This strategy has been applied to all relevant source files. - -1.6 Complete set of PLplot parameters now available for Fortran - -The #defines in bindings/swig-support/plplotcapi.i (which are -consistent with those in include/plplot.h) define the complete set of -important PLplot constants (whose names typically start with "PL_"). -We have implemented automatic methods of transforming that complete -set of #defines into Fortran parameters that can be used from either -Fortran 77 or Fortran 95. - -For Fortran 77, the user must insert an - - include 'plplot_parameters.h' - -statement in every function/subroutine/main programme where he expects -to use PLplot constants (whose names typically start with "PL_". (See -examples/f77/*.fm4 for examples of this method). When compiling he -must also insert the appropriate -I option to find this file (in -bindings/f77/ in the source tree and currently in -$prefix/lib/fortran/include/plplot$version in the install tree -although that install location may be subject to change). Note, the -above method does not interfere with existing apps which have -necessarily been forced to define the needed PLplot constants for -themselves. But for future f77 use, the above statement is -more convenient and much less subject to error than a whole bunch of -parameter statements for the required constants. - -For Fortran 95, the complete set of parameters are made available as -part of the plplot module. So access to this complete set of -parameters is automatic wherever the "use plplot" statement is used. -This is extremely convenient for new Fortran 95 apps that use PLplot, -but, in general, changes will have to be made for existing apps. (See -announcement XX above for the details). - 2. Changes relative to PLplot 5.8.0 (the previous stable release) 2.1 All autotools-related files have now been removed @@ -888,7 +849,7 @@ - Fixes for the qt examples with dynamic drivers disabled - Fixes to several tcl examples so they work with plserver - Fix pkg-config files to work correctly with Debug / Release build types set -- Make fortran command line argument parsing work with shared libraries on Windows +- Make Fortran command line argument parsing work with shared libraries on Windows 2.32 Cairo driver improvements @@ -1052,7 +1013,7 @@ This improvement courtesy of David MacMahon adds support for arbitrary storage of 2D user data. This is very similar to the technique employed by some existing functions (e.g. plfcont and plfshade) that use "evaluator" -functions to access 2D user data that is stored in an arbtrary format. +functions to access 2D user data that is stored in an arbitrary format. The new approach extends the concept of a user-supplied (or predefined) "evaluator" function to a group of user-supplied (or predefined) "operator" functions. The operator functions provide for various operations on the @@ -1072,7 +1033,7 @@ PLPointer to the actual 2D data store. Existing functions that accept 2D data are modified to simply pass their parameters to the corresponding new variant of the function, along with a pointer to the -suitable predefined plf2ops_t stucture of operator function pointers. +suitable predefined plf2ops_t structure of operator function pointers. The list of functions for which new variants are created is: c_plimage, c_plimagefr, c_plmesh, c_plmeshc, c_plot3d, c_plot3dc, @@ -1189,7 +1150,7 @@ available for 5.9.7. Due to feedback from early adopters of pllegend, we have now added substantially to the pllegend capabilities. and we now believe pllegend is ready for prime time. The pllegend -capabilities are documented in our docbook documentation and +capabilities are documented in our DocBook documentation and demonstrated in standard examples 4, 26, and 33. N.B. The current set of changes required a backwards-incompatible This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ai...@us...> - 2011-10-10 05:47:30
|
Revision: 11944 http://plplot.svn.sourceforge.net/plplot/?rev=11944&view=rev Author: airwin Date: 2011-10-10 05:47:24 +0000 (Mon, 10 Oct 2011) Log Message: ----------- Update status of OCaml testing. Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2011-10-09 21:53:58 UTC (rev 11943) +++ trunk/README.release 2011-10-10 05:47:24 UTC (rev 11944) @@ -362,8 +362,8 @@ 0. Tests made for release 5.9.9 * (Alan W. Irwin) A fully loaded (all Linux bindings other than PDL, - all Linux device drivers including our qt and cairo device drivers) Debian Squeeze - Linux platform gave a good result for the + all Linux device drivers including our qt and cairo device drivers) + Debian Squeeze Linux platform gave a good result for the scripts/comprehensive_test.sh script. This script runs 7 major tests for each of our three principal build configurations (shared library/dynamic device drivers, shared libraries/nondynamic device @@ -372,7 +372,9 @@ in the build tree, the test_noninteractive and test_interactive targets configured with CMake in the installed examples tree, and the traditional (MakeFile + pkg-config) test_noninteractive and - test_interactive targets in the installed examples tree. + test_interactive targets in the installed examples tree. These + tests were done with OCaml disabled because of a segfault and a + series of bad valgrind test results that occurred for OCaml 3.11.2. * (Andrew Ross) For one Ubuntu platform the test_noninteractive and test_interactive targets for the shared libraries and dynamic @@ -383,7 +385,9 @@ Linux platform because of a segfault in one of the qt devices. We have tentatively ascribed this issue to issues with the Qt4 stack of libraries on that platform since this bad qt result contrasts with - the good qt result on the previous two Linux platforms. + the good qt result on the previous two Linux platforms. When qt devices + were ignored, clean valgrind results were obtained for OCaml-3.12.1 + (in contrast to the bad valgrind results seen for OCaml-3.11.2 above). * (Arjen Markus) MinGW/MSYS installed on a lightly loaded (at least compared to Linux tests) Windows XP system gives good results for This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <hez...@us...> - 2011-10-10 13:38:07
|
Revision: 11946 http://plplot.svn.sourceforge.net/plplot/?rev=11946&view=rev Author: hezekiahcarty Date: 2011-10-10 13:38:01 +0000 (Mon, 10 Oct 2011) Log Message: ----------- Update README.release with more information on the OCaml bindings Modified Paths: -------------- trunk/README.release Modified: trunk/README.release =================================================================== --- trunk/README.release 2011-10-10 13:37:55 UTC (rev 11945) +++ trunk/README.release 2011-10-10 13:38:01 UTC (rev 11946) @@ -95,14 +95,6 @@ 5.9.9 which has been heavily tested on a number of platforms including Windows, see "Tests made for release 5.9.9" below. -(5.9.9) During our extensive testing of this release we noticed a segfault -with the OCaml bindings/examples. Follow up with valgrind indicated -some widespread memory management issues with our OCaml -bindings/examples. Therefore, we have disabled OCaml by default for -this release and hope to reinstate it again just as soon as we figure -out these issues. If you want to try it anyway for this release -specify the -DENABLE_ocaml=ON cmake option. - (5.9.8) For unicode-aware devices we now follow what is done for the Hershey font case for epsilon, theta, and phi. This means the #ge, #gh, and #gf escapes now give users the Greek lunate epsilon, the @@ -382,12 +374,12 @@ platform including our qt and cairo device drivers. * (Hezekiah M. Carty) scripts/comprehensive_test.sh failed on a Ubuntu - Linux platform because of a segfault in one of the qt devices. We + Linux platform because of segfaults in the qt devices. We have tentatively ascribed this issue to issues with the Qt4 stack of libraries on that platform since this bad qt result contrasts with the good qt result on the previous two Linux platforms. When qt devices - were ignored, clean valgrind results were obtained for OCaml-3.12.1 - (in contrast to the bad valgrind results seen for OCaml-3.11.2 above). + were ignored, clean valgrind results were obtained for OCaml-3.12.1 and + OCaml-3.11.2 (in contrast to the results seen for OCaml-3.11.2 above). * (Arjen Markus) MinGW/MSYS installed on a lightly loaded (at least compared to Linux tests) Windows XP system gives good results for This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |