 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> I guess this image doesn't need too much explanation. Another feature to
> be included in that branch of mine.
yes, please.
I can see a number of uses for the ability to parse plain-text in povray,
beginning with a procedural texture for rendering text to monitors on computers,
which would free you of the burden of making a properly formatted and scaled
image map, and allow greater freedom with the screen texture.
what I'd like to see is the ability to specify an optional delimiter in read(),
but I suppose you could always just read in a line and break it on your own
criteria later.
What's the word on the new SDL? Or will there be one?
Regards,
A.D.B.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 02.08.2013 00:07, schrieb Anthony D. Baye:
> What's the word on the new SDL? Or will there be one?
It is high on the agenda; some thoughts have already been invested into
the architecture behind it (such as, what virtual machine to use, or
what framework to use to implement the parser), and there are a number
of requirements floating around for the new language; but actual
implementation will not start before 3.7.0 is out the door.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka wrote:
> I guess this image doesn't need too much explanation. Another feature to
> be included in that branch of mine.
It is cool to be able to read arbitrary files! But it probably
requires some "sscanf"-like functionality as well to be really useful
(except simply rendering text such as book pages, newspapers, ...)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
