 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 14 Jan 1998 20:53:43 -0800, "Ken Cecka" <cec### [at] televar com>
wrote:
>I'm a little behind the times on this posting, so I decided not to reply to
>the former thread, but start a new one. On Dec. 27th, Tim Grubb asked about
>adding persistent variables to POV. It turns out that POV is already
>capable of them in a round about sort of way. I actually saw this technique
>used in a tree include file a long time ago, but I don't recall who wrote
>it. Anyway, you can achieve persistent variables through the debug stream.
>Redirect the debug output to a file, and write out your variables in the
>form of #declare's to the file. Then include that file to get the previous
>value. I guess an example is the easiest way to demonstrate. I'll attatch
>persistent.ini and persistent.pov. They are just a test of the idea, and in
>no means robust, but I imagine a fairly comprehensive include file could be
>written for this type of thing. Even if not, it's pretty easy to impliment
>in a scene.
>
>Ken
>
As an expansion on your idea, POV-Ray 3.1 will have #fopen, #write,
#read, and #fclose.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Young wrote:
> As an expansion on your idea, POV-Ray 3.1 will have #fopen, #write,
> #read, and #fclose.
So POV will now stand for Persistence Of Variables?
Jerry Anning
cle### [at] dholcom
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
767### [at] compuservecom (Chris Young) writes:
>
> As an expansion on your idea, POV-Ray 3.1 will have #fopen, #write,
> #read, and #fclose.
Doesn't this open the door for POV-Ray viruses?
ThW
--
Tho### [at] uni-konstanzde
http://www.informatik.uni-konstanz.de/~willhalm/
Tschieses lavs ju
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thomas Willhalm <Tho### [at] uni-konstanzde> wrote:
>767### [at] compuservecom (Chris Young) writes:
>>
>> As an expansion on your idea, POV-Ray 3.1 will have #fopen, #write,
>> #read, and #fclose.
>
>Doesn't this open the door for POV-Ray viruses?
Probably not any more than the existing shell-outs (pre render, post render,
post frame, etc. etc. and so forth.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thomas Willhalm <Tho### [at] uni-konstanzde> writes:
> 767### [at] compuservecom (Chris Young) writes:
> >
> > As an expansion on your idea, POV-Ray 3.1 will have #fopen, #write,
> > #read, and #fclose.
>
> Doesn't this open the door for POV-Ray viruses?
I do not think so, since the POV-Ray scene description language is clear
and simple, so you'll be able to detect strange things. That would not be
the case if the POV-Ray format were proprietary, thanks a lot POV-Team.
Roland.
--
bob### [at] casimirrezelenstfr -- Linux, POV-Ray, LaTeX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Young <767### [at] compuservecom> wrote:
>
> As an expansion on your idea, POV-Ray 3.1 will have #fopen, #write,
> #read, and #fclose.
Interesting.. Now we can have Povray viruses. A povray scene which
appends itself to one the include files maybe... Just kidding, I don't
think anyone would (or could) make such a virus.
/ Mathias Broxvall
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
mbr### [at] swipnetseNOSPAM (Mathias Broxvall) writes:
> Interesting.. Now we can have Povray viruses. A povray scene which
> appends itself to one the include files maybe... Just kidding, I don't
> think anyone would (or could) make such a virus.
Anyway, aside from looking at a file before rendering it, one can always
lock files against writing (at least on filesystems like FAT, ext2fs and
Atari's one. I have no experience on other filesystems.).
Roland.
--
bob### [at] casimirrezelenstfr -- Linux, POV-Ray, LaTeX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The ability to have persistent variables will outweigh any possible negatives.
It
will allow utilities authors to take a great step forward in animation.
Also think I'll stir up another long discussion:
What about a Browser that uses .pov scene files? VRML is crappy in my opinion.
That is what happens when it is developed only by people on T3's. The POV
scene file could be transferred much quicker ( although primarily simpler
scenes at
first). The renderer could be written in OGL for xplatform. Still use most of
the
HTML that people are used to. I do not have much knowledge of the POV parser
code and that in itself is huge.
Just a suggestion / idea
Timothy A. Grubb
http://www.wallysoft.com
Roland Mas wrote:
> mbr### [at] swipnetseNOSPAM (Mathias Broxvall) writes:
>
> > Interesting.. Now we can have Povray viruses. A povray scene which
> > appends itself to one the include files maybe... Just kidding, I don't
> > think anyone would (or could) make such a virus.
>
> Anyway, aside from looking at a file before rendering it, one can always
> lock files against writing (at least on filesystems like FAT, ext2fs and
> Atari's one. I have no experience on other filesystems.).
>
> Roland.
> --
> bob### [at] casimirrezelenstfr -- Linux, POV-Ray, LaTeX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mathias Broxvall wrote:
>
> Chris Young <767### [at] compuservecom> wrote:
>
> >
> > As an expansion on your idea, POV-Ray 3.1 will have #fopen, #write,
> > #read, and #fclose.
>
> Interesting.. Now we can have Povray viruses. A povray scene which
> appends itself to one the include files maybe... Just kidding, I don't
> think anyone would (or could) make such a virus.
>
> / Mathias Broxvall
I'd make one (and not release it) just to see if it can be done. I
just can't imagine what one would do with such a thing, malicious or
otherwise.
------------------------------
Chris Jeppesen
Amalthea Distributed Renderer for POV-Ray
http://www.geocities.com/CapeCanaveral/Launchpad/3392/amalthea.html
EMail I will read: Chr### [at] digiquillcom
------------------------------
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
