On Dec 2, 2009, at 12:04 AM, Alan W. Irwin wrote:
> On 2009-12-01 17:58-0800 Alan W. Irwin wrote:
>
>> There have been no comments about the plgradient API, and I
>> certainly do not
>> forsee that changing in the future. Therefore, it is time to
>> propagate
>> plgradient to all our languag
Here is a full status report showing what still needs to be done to
finish the gradient work:
As of revision 10676, our svg, qt, and cairo device drivers support native
gradients, and that is all I plan to work on native gradients (other than
bug fixing) for our device drivers. The results look m
I have just finished implementing native gradients for the remaining
qt devices (revision 10675).
The whole exercise was my first really positive experience with C++. For
example, I feel I am finally beginning to understand OOP (especially
inheritance) after years of avoiding thinking about it.
O
I have now finished propagating plgradient to the c++, d, f77, f95, java,
lua, and python bindings and the corresponding examples 25 and 30 that use
plgradient. All give identical results to the corresponding C results.
(Ignore the comment about lua issues for example 30 in the commit message.
Tha
Hi Alan,
ah, I will have a look at that - I checked the F77 case
and realised why the plfill and plline entries were missing.
For F95 we have Fortran wrappers that ultimately call
the C versions. The reason is that we can then hide the
parameter for the number of points (that is one other
reason f
On 2009-12-02 09:18+0100 Arjen Markus wrote:
> Hi Alan,
>
> On 2009-12-02 08:04, Alan W. Irwin wrote:
>
>> f77 and f95 have also been completed as of revision 10665. For both f77 and
>> f95 there appear to be some *.def file updates still to do for plgradient.
>> I assume the windows Fortran 77 an
Hi Alan,
On 2009-12-02 08:04, Alan W. Irwin wrote:
> f77 and f95 have also been completed as of revision 10665. For both f77 and
> f95 there appear to be some *.def file updates still to do for plgradient.
> I assume the windows Fortran 77 and 95 example builds will be broken because
> of that la
On 2009-12-01 17:58-0800 Alan W. Irwin wrote:
> There have been no comments about the plgradient API, and I certainly do not
> forsee that changing in the future. Therefore, it is time to propagate
> plgradient to all our languages and adjust examples 25 and 30 accordingly.
>
> I have just (revis
There have been no comments about the plgradient API, and I certainly do not
forsee that changing in the future. Therefore, it is time to propagate
plgradient to all our languages and adjust examples 25 and 30 accordingly.
I have just (revision 10662) completed that process for C++, D, and python
