Hey every one
here is an easy one what about adding in the sprits so that you can have
sprites3d()
which well look a lot better then the points3d, if you can do it faster give
it a try
its in the openGL Superbook I got the 5 edition and as I looked threw every
page
I saw the code for it,, if you have the 4 edition it might be in there too , I
think it would
give PDL a upgraded look, as we have all put a lot of time in to PDL why not
have it look
like Raytraced
if you don't do it I will, but it gonna be a while .... I get on one thing and
it always turn in to another...
________________________________
From: David Mertens <[email protected]>
To: chm <[email protected]>
Cc: [email protected]
Sent: Saturday, September 17, 2011 10:30 AM
Subject: Re: [Perldl] plans and lists for PDL-2.4.10 development
Hi Chris, all,
I gotta say that all of these ideas look good, but my heart is not in
them, except possibly working on PP warnings, general documentation,
and the PDL book. The two driving factors for my interests these days
are (1) finishing and releasing my own new plotting module based on
the Prima toolkit, and (2) giving an introduction to PDL at the next
Chicago PerlMongers meeting (late October). The first item involves
some very sophisticated code generation, and my efforts to document my
own code generation machinery has led me to study the PP Rules very
closely. As a side effect, I may update the documentation to PDL::PP
as well as work on warnings for strange items when PP is parsing
things. The second item may lead to me to work on the documentation
for slices as well as PP, and maybe even take up the PDL book.
I hate to come out and say "I'll be working on X" because I often end
up not getting much work done after such pronouncements. However, the
two underlying motivations aren't going away. I use my plotting
library already in my work, and I *will* be giving a talk at the PM
meeting. So the chances of this stuff getting done is higher than in
the past, I hope.
Another item that I would be interested in working on, but is likely
to slip through the cracks, is the callback slice operation, which
should probably actually be called 'on_change' instead. That has great
potential for use as well as improvement. If I end up using it in my
plotting library, I may work on it and submit it. Otherwise, I'll need
enthusiasm from the community to finish it.
David
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
