Warp,

it just occurred to me that Mark posted a 3D Mandelbrot image a month
ago. I went back to that post and what do you know, he posted the C
source in p.b.s-f.! I suggest you check it out as Mark's hack at 3D
M-Sets seems better than the one I've seen before (some DOS program so
long ago).

The post in p.b.i. is:

From: "Mark Wagner" <mar### [at] gtenet>
Newsgroups: povray.binaries.images
Subject: 3D Mandelbrot Set
Date: Fri, 1 Oct 1999 01:25:33 -0400
Message-ID: <37f444b0@news.povray.org>

And the one in p.b.s-f. is:

From: "Mark Wagner" <mar### [at] gtenet>
Newsgroups: povray.binaries.scene-files
Subject: 3D Mandelbrot Set
Date: Sat, 2 Oct 1999 01:20:48 -0400
Message-ID: <37f5952a@news.povray.org>

Hope this helps.


Peter Popov
ICQ: 15002700

Post a reply to this message

Actually, I'd appreciate the entire file (as an attachment).  Thanks.

-Nathan

Nieminen Juha <war### [at] punarastascstutfi> wrote in message
news:381ebb28@news.povray.org...
> Nathan Kopp <Nat### [at] koppcom> wrote:
> : Got source?  Send it here and I'll put it in some future version of
UVPov.
> : I guess I need pattern.c, parstxtr.c, some header files... anything
else?
>
>   Thanks to both of you. I can send a diff of the original 3.1g source and
> the patch. Is that enough?
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Nathan Kopp <Nat### [at] koppcom> wrote:
: Actually, I'd appreciate the entire file (as an attachment).  Thanks.

  It's absolutely ok to me. I'm just worried that you will miss some change
if you just compare the files by eye...

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

>  Yes, I was thinking about adding different (predefined) formulas for
>coloring the interior and exterior of the fractals.
>  I thought also about letting the user to specify coloring methods or even
>pixel color calculations, but that would be almost like making a
programmable
>shader, I think.



>  Adding those pattern types was quite easy just by looking how the mandel
>type was done. I have not studied the povray source code so much that I
>could add a completely new type of block with its own syntax.
>
>--


Well, I think the FRACTINT source is free. Why not ask the authors for
permission to simply use the FRACTINT code to parse user formulae? I think
there wouldn't be any need to create that much addition to the POVRAY-code,
because you could create some statement like:

#import "masta_blasta.frm"

and simply let the patched POV read the .frm as FRACTINT does! Then add
identifiers for the formulae in the .frm-file. The patch could have new
class definitions for formulae, and such there wouldn't be a need for
including the formula generation inside the scene language itself.

Good idea, huh? Isn't it?

Then again, the best would of course to have it *in* the scene language. But
the superpatch has some of this functionality, hasn't it? I mean, with the
isosurface primitive (? :)  you specify the implicit equation for the
surface.


I got a little carried away here, because I just love the thought of full
control over fratals in pov! Man! That would be like christmas, easter,
birthday, wedding, and fune... no. But the first ones, all at once!  :)

Simen.

Post a reply to this message

>Fractal-valued isosurfaces.  Big, smooth, snowdrifty julia-set
>landscapes.  Yum.


AARGH! MY HEAD IS EXPLODING! =8O.

*drool* Fractals and POVRAY... yup.

>
>Of course, that means it'll never get released. :)


WHAT?!

Post a reply to this message

On 3 Nov 1999 04:12:45 -0500, Nieminen Juha wrote:
>Nathan Kopp <Nat### [at] koppcom> wrote:
>: Actually, I'd appreciate the entire file (as an attachment).  Thanks.
>
>  It's absolutely ok to me. I'm just worried that you will miss some change
>if you just compare the files by eye...

I actually prefer the entire file as well, but I can handle it in patch form.
You see, I've automated the process of merging entire directory trees into my 
existing source using diff3, and my scripts want whole source files.  Getting 
it in patch form requires me to apply the patches first, then run the scripts.

-- 
These are my opinions.  I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message

On Wed, 3 Nov 1999 14:09:58 +0100, Simen Kvaal wrote:
>>Of course, that means it'll never get released. :)

>WHAT?!

Relax, it was a joke.  See, I've been promising a 3.1g version of the
superpatch for months now...


-- 
These are my opinions.  I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message

Ron Parker <ron### [at] povrayorg> wrote...
>
> I actually prefer the entire file as well, but I can handle it in patch
form.
> You see, I've automated the process of merging entire directory trees into
my
> existing source using diff3, and my scripts want whole source files.
Getting
> it in patch form requires me to apply the patches first, then run the
scripts.
>

I use a nice diff program (I use CSDiff) and make changes by hand.  Have you
found success with diff3?  It kind of scares me to let something make
changes to my source for me, especially after I've hacked up POV as much as
I have.  ;-)

-Nathan

Post a reply to this message

On Thu, 4 Nov 1999 00:09:41 -0500, Nathan Kopp wrote:
>I use a nice diff program (I use CSDiff) and make changes by hand.  Have you
>found success with diff3?  It kind of scares me to let something make
>changes to my source for me, especially after I've hacked up POV as much as
>I have.  ;-)

I've found success with my scripts based on diff3.  diff3 by itself isn't
enough, generally.  I have one script that compares one source directory to
another and copies just the changed files to a new directory, one that does
the merge and puts the results in a new directory, and one that reads the 
results of the merge and builds a series of diff files to help me resolve
the inevitable conflicts (diff3 can mark HUGE blocks of text as conflicts,
even when only something small changed within them, and sometimes when 
nothing changed in one of the merged versions.  Knowing that is quite helpful 
sometimes.)

And of course I keep a backup until I've tested a new patch.  One of these
days I'll get around to finishing installing CVS and I'll stop worrying 
because it'll do most of the hard work for me.

-- 
These are my opinions.  I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message

Nieminen Juha <war### [at] punarastascstutfi> wrote:
: All return values (except type 2 for exterior) are multiplied by FACTOR
: before returning.

  This should be "type 1", not "type 2".

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message