ftp.xmission.com/2014.06.ftp.xmission.com.tar/ftp.xmission.com/pub/lists/fractdev/archive/fractdev.200002

Internet Message Format | 2000-02-29 | 81KB

From: Jonathan Osuch <[e-mail]>
Subject: Re: Opening ISO image files
Date: 01 Feb 2000 22:38:33 -0500

>> I had to define NOBSTRING in the makefile, and define SignalHandler in=

unix.h. <<

At one time, I had already done that.  I noticed it was missing from the
latest source.  I probably just forgot to put it in a patch.

The fact that with some distributions of Red Hat you need this and with
others, you don't is quite frustrating.  We need to figure out how to mak=
e
auto config work.

Jonathan

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Phil McRevis <[e-mail]>
Subject: Re: Opening ISO image files
Date: 01 Feb 2000 20:44:51 -0700


In article <[e-mail]>,
    Jonathan Osuch <[e-mail]>  writes:

> We need to figure out how to make
> auto config work.

I have the knowledge to do this now (automake/autoconf/configure).
There are relatively few system dependencies in the xfractint code, but
the bstring one is the one that is a pain.

Unfortunately I am extremely short on time -- I'm writing a book.
Ugh.
--
<http://www.xmission.com/~legalize/>    Legalize Adulthood!
    ``Ain't it funny that they all fire the pistol,
      at the wrong end of the race?''--PDBT
[e-mail]    <http://www.xmission.com/~legalize/who/>

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: Fractint 20.0.6 now public
Date: 01 Feb 2000 23:20:15 -0600

Fractint 20.0.6, the developer version 20.0 patch 6, is now available
via anonymous ftp at ftp.fractint.org/fradev.zip. We intend to release
most, if not all, of the developer versions from now on.

This file has only the executable, a PAR/FRM file by Sylvie Gallet,
and a read.me. It's not a complete distribution - you still need the
version 20.0 files.

Please don't upload this anywhere unless you are willing to keep it
current. These developer versions can change very fast! Also, this
is not an official release, but a bleeding edge version, so be careful.
On the other hand, it has bug fixes, so maybe it is more stable
than a release version :-) Our official position is that there is some
risk in using a developer version for serious art, because we may
make changes that are not forward compatible. Of course we try to
avoid this.

The fractint.org ftp site also has the developer diff files and the
version 20.0 release package and source. This web site is not
intended to replace Noel Giffin's wonderful spanky.triumf.ca; I
expect Noel will have the developer's executable up there soon also.

This version is mostly bug fixes (see the what's new). However
Sylvie Gallet asked us to add the center/mag parameters as
formula parser constants. We accomodated her without exactly
understanding why she wanted this. An example file is included in
fradev.zip. It looks for all the world like a fractal reflected in a lake.
Ms. Gallet never ceases to amaze me :-)

As we get more organized we'll get Xfractint and an integer-free
version posted also.

Enjoy!

Tim Wegner
[e-mail]


------- End of forwarded message -------

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: Xfractint
Date: 07 Feb 2000 22:26:37 -0600

I have updated Xfractint to patch 6. Jonathan pointed out that I
missed incorporating an Xfractint patch a while ago. I have
remedied that. The first 6 DOS patches created only a small
problem which Jonathan will recognise - I have to remove the
"static" keyword for disktarga in diskvidu.c.

Xfractint now compiles cleanly under Mandrake/Red Hat.

Because realdos.c trivially changed to reflect the version change, I
need to make a DOS patch 7.

I'll take care of this and upload XFractint tomorrow,

Tim


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: Re: Xfractint
Date: 09 Feb 2000 00:15:53 -0600

I have uploaded a complete Xfractint distribution updated to 20.0.7.
The file is:

ftp://ftp.fractint.org/xfrac311.zip

The diff files between patch 6 and 7 are in:

ftp://ftp.fractint.org/2000p07.zip

This file contains 2000p07.dif which is for the DOS files, and
2000p07x.dif which is for the Xfractint (non DOS) files. The patch 7
changes are too trivial to be worth downloading the executable, but
I did update fradev.zip.

Tim



Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Jonathan Osuch <[e-mail]>
Subject: Re: Xfractint
Date: 09 Feb 2000 20:54:14 -0500

>> I have updated Xfractint to patch 6. Jonathan pointed out that I =

missed incorporating an Xfractint patch a while ago. I have =

remedied that. The first 6 DOS patches created only a small =

problem which Jonathan will recognize - I have to remove the =

"static" keyword for disktarga in diskvidu.c. <<

I also changed the call to common_startdisk() in the targa_startdisk()
routine in diskvidu.c to match what is in diskvid.c.  Not that it matters=
,
the Targa stuff is broken in Xfractint.

Jonathan

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: Re: Xfractint
Date: 09 Feb 2000 20:46:47 -0600

Jonathan wrote:

> I also changed the call to common_startdisk() in the targa_startdisk()
> routine in diskvidu.c to match what is in diskvid.c.  Not that it matters,
> the Targa stuff is broken in Xfractint.

The important thing is that we get synched. I believe that if you
apply my patch 7 to your patch 6 DOS source, the result is the
same as the non-unix-specific files in xfrac311.zip. Unless I've
goofed, lets make 3.11/20.0.7 the baseline. I'm about ready to
ditch the Xfractint version numbers. Perhaps we should do away
with the Xfractint version system and call both DOS and Xfractint
versions 20.0.7. Every Xfractint patch results in a DOS patch
anyway since the help.src and realdos.c is edited with every patch.

Tim


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Jonathan Osuch <[e-mail]>
Subject: Re: Xfractint
Date: 09 Feb 2000 23:20:42 -0500

Tim wrote,

>> The important thing is that we get synched. I believe that if you =

apply my patch 7 to your patch 6 DOS source, the result is the =

same as the non-unix-specific files in xfrac311.zip. Unless I've =

goofed, lets make 3.11/20.0.7 the baseline. I'm about ready to =

ditch the Xfractint version numbers. Perhaps we should do away =

with the Xfractint version system and call both DOS and Xfractint =

versions 20.0.7. Every Xfractint patch results in a DOS patch =

anyway since the help.src and realdos.c is edited with every patch. <<

Yes, synching is good.  Ditching the Xfractint version numbers makes a lo=
t
of sense.

Jonathan

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Scott D. Boyd" <[e-mail]>
Subject: Compiling erorrs - xfractint 3.11
Date: 09 Feb 2000 23:39:01 -0600

Tried to compile xfractint 3.11 under Redhat Linux 6.1 - kernel 2.2.13,
using gcc 2.7.2.3.

gcc chokes on help.src. I think gcc doesn't like the tilde (~)symbol in
that file. can anybody offer any help?

Here's the output from 'make xfractint':

gcc -I. -DXFRACT -DNOBSTRING   -g -DBIG_ANSI_C -DLINUX    -c hc.c -o hc.o
gcc -I. -DXFRACT -DNOBSTRING   -g -DBIG_ANSI_C -DLINUX -DSRCDIR=\"/usr/src/xfractint\" -c  unix.c
gcc -o hc -I. -DXFRACT -DNOBSTRING -g -DBIG_ANSI_C -DLINUX  hc.o unix.o ./hc /c
HC - FRACTINT Help Compiler.

Compiling: help.src
" contains illegal characters.ELPMENU
" contains illegal characters.ELP_INDEX
"  Error help.src 15: Invalid text after a command "
"  Error help.src 36: Invalid text after a command "
"  Error help.src 40: Invalid text after a command "
"  Error help.src 320: Invalid text after a command "
"  Error help.src 385: Invalid text after a command "
"  Error help.src 561: Invalid text after a command "
"  Error help.src 582: Invalid text after a command "
"  Error help.src 616: Invalid text after a command "
"  Error help.src 636: Invalid text after a command "
"  Error help.src 658: Invalid text after a command "
"  Error help.src 660: Invalid text after a command "
"  Error help.src 662: Invalid text after a command "
"  Error help.src 671: Invalid text after a command "
"  Error help.src 673: Invalid text after a command "
"  Error help.src 675: Invalid text after a command "
"  Error help.src 683: Invalid text after a command "
" contains illegal characters.HELPMAIN
"  Error help.src 704: Invalid text after a command "
"  Error help.src 709: Invalid text after a command "
"  Error help.src 750: Invalid text after a command "
"  Error help.src 793: Invalid text after a command "
" contains illegal characters.HELPZOOM
   Fatal help.src 966: Too many errors!

Compiler Status:
      25 Errors
       0 Warnings
make: *** [fractint.hlp] Error 26

Scott Boyd
--
email:  sdboyd at fastlane.net
http://www.fastlane.net/~sdboyd/
Introducing -- Windows 2000 !!
(Don't try this at home... or at work, either.)


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Michael Ganss <[e-mail]>
Subject: Re: Compiling erorrs - xfractint 3.11
Date: 10 Feb 2000 11:42:00 +0100

"Scott D. Boyd" wrote:
>
> Tried to compile xfractint 3.11 under Redhat Linux 6.1 - kernel 2.2.13,
> using gcc 2.7.2.3.
>
> gcc chokes on help.src. I think gcc doesn't like the tilde (~)symbol in
> that file. can anybody offer any help?

It doesn't like the DOS CR+LF. Use unzip -a.

cheers
--
Michael R. Ganss             VI VI VI The editor of the beast.
[e-mail]

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Phil McRevis <[e-mail]>
Subject: Re: Xfractint
Date: 10 Feb 2000 15:30:19 -0700


In article <[e-mail]>,
    Tim Wegner <[e-mail]>  writes:

> Perhaps we should do away
> with the Xfractint version system and call both DOS and Xfractint
> versions 20.0.7.

Yes!!  Since they share the same code base, the different version
numbers just make for confusion anyway.
--
<http://www.xmission.com/~legalize/>    Legalize Adulthood!
    ``Ain't it funny that they all fire the pistol,
      at the wrong end of the race?''--PDBT
[e-mail]    <http://www.xmission.com/~legalize/who/>

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Phil McRevis <[e-mail]>
Subject: Re: Compiling erorrs - xfractint 3.11
Date: 10 Feb 2000 15:33:57 -0700


In article <[e-mail]>,
    Michael Ganss <[e-mail]>  writes:

> It doesn't like the DOS CR+LF. Use unzip -a.

    sed 's/.$//' infile.dos > outfile.txt

also does the trick if you just need to diddle one or two files.
--
<http://www.xmission.com/~legalize/>    Legalize Adulthood!
    ``Ain't it funny that they all fire the pistol,
      at the wrong end of the race?''--PDBT
[e-mail]    <http://www.xmission.com/~legalize/who/>

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Scott D. Boyd" <[e-mail]>
Subject: Re: Compiling erorrs - xfractint 3.11
Date: 10 Feb 2000 22:44:12 -0600

On Thu, 10 Feb 2000, Phil wrote:
> In article <[e-mail]>,
>     Michael Ganss <[e-mail]>  writes:
>
> > It doesn't like the DOS CR+LF. Use unzip -a.
>
>     sed 's/.$//' infile.dos > outfile.txt
>
> also does the trick if you just need to diddle one or two files.

Since all 6 help source-files were of similar format, I used unzip -a. That
worked great. Thanks Phil & Michael!

Scott
--
email:  sdboyd at fastlane.net
http://www.fastlane.net/~sdboyd/
Introducing -- Windows 2000 !!
(Don't try this at home... or at work, either.)


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: Re: Compiling erorrs - xfractint 3.11
Date: 10 Feb 2000 23:14:09 -0600


> > It doesn't like the DOS CR+LF. Use unzip -a.

Oops, my fault. I'll fix tomorrow. Meanwhile, zip -a is indeed an
excellent solution.

Tim


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Jonathan Osuch <[e-mail]>
Subject: Lsystem/IFS bug
Date: 12 Feb 2000 14:26:29 -0500

Tim W.

One of the items on Robin's bug list that caught my attention was that bo=
th
the Lsystem and IFS types would lock up when using a disk video mode with=
 a
resolution greater that 2048 (I use one of 2050x2050 to test this).  I've=

tracked it down to the calcfracinit() routine (in fracsubr.c).  For some
reason, these two types are getting into an infinite loop at init_restart=
:

Can you provide any insight into this?  This is the section where we are
checking to see if we want to use integer/floating/arbitrary precision.

Jonathan

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: Re: Lsystem/IFS bug
Date: 12 Feb 2000 13:37:21 -0600


> One of the items on Robin's bug list that caught my attention was that both
> the Lsystem and IFS types would lock up when using a disk video mode with a
> resolution greater that 2048

OK, I'll look into this.

Is the buglist back up? I removed the link from the webpage.

Tim


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Jonathan Osuch <[e-mail]>
Subject: Re: Lsystem/IFS bug
Date: 12 Feb 2000 16:57:22 -0500

>> Is the buglist back up? I removed the link from the webpage. <<

I don't think so.  I downloaded the page in September/October and saved t=
he
legitimate bugs into a text file.  I've been working from that file, when=

I've been working <G>.

Jonathan

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Jonathan Osuch <[e-mail]>
Subject: Re: Lsystem/IFS bug
Date: 12 Feb 2000 22:32:11 -0500

>> > One of the items on Robin's bug list that caught my attention was th=
at
both
> the Lsystem and IFS types would lock up when using a disk video mode wi=
th
a
> resolution greater that 2048 =


OK, I'll look into this. <<

This is happening because both ifs and lsystem don't have entries for bot=
h
float and integer in the big array in fractalp.c.  That is to say, each h=
as
only one routine that is called and the integer/float decision is made
internal to that routine.

The problem occurs when the integer/float switch goes looking for the flo=
at
version (because the screen resolution is too high) in the array variable=
s
and doesn't find one.

A temporary solution would be to put in a check for ifs and lsystem.  In
the long run, we need to think about possible changes to the data
structure.

Jonathan

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Damien M. Jones" <[e-mail]>
Subject: Re: Lsystem/IFS bug
Date: 12 Feb 2000 22:57:22 -0500

Jonothan,

 - This is happening because both ifs and lsystem don't have
 - entries for both float and integer in the big array in
 - fractalp.c.  That is to say, each has only one routine that
 - is called and the integer/float decision is made internal
 - to that routine.

Fill in the unfilled pointers with pointers to the existing routine? If the
routine determines internally whether to use float or int, then it is
appropriate to be called from either float or int, and both pointers should
reference the same routine.

(Note: I have not looked at the source, if I'm spouting off please feel
free to call me an idiot.)

Damien M. Jones   \\
[e-mail]  \\  Fractalus Galleries & Info:
                    \\  http://www.fractalus.com/

Please do not post my e-mail address on a web site or
in a newsgroup.  Thank you.


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Jonathan Osuch <[e-mail]>
Subject: Re: Lsystem/IFS bug
Date: 13 Feb 2000 10:32:29 -0500

Damien,

>> Fill in the unfilled pointers with pointers to the existing routine? I=
f
the
routine determines internally whether to use float or int, then it is
appropriate to be called from either float or int, and both pointers shou=
ld
reference the same routine. <<

Yes, that's a good idea.  I'll try it, thanks.

Jonathan

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Jonathan Osuch <[e-mail]>
Subject: Re: Lsystem/IFS bug
Date: 13 Feb 2000 12:58:14 -0500

Damien,

>> Fill in the unfilled pointers with pointers to the existing routine? I=
f
the
routine determines internally whether to use float or int, then it is
appropriate to be called from either float or int, and both pointers shou=
ld
reference the same routine. <<

That doesn't quite work.  So far, what works best is to force the use of
floating point using the variable in the fractals data structure.  We'll
end up with this eventually after we eliminate all the integer fractal
code.  But, for now, that doesn't quite work either.

Jonathan

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Jonathan Osuch <[e-mail]>
Subject: Re: Lsystem/IFS bug
Date: 13 Feb 2000 22:58:32 -0500

Tim W.

>> > One of the items on Robin's bug list that caught my attention was th=
at
both
> the Lsystem and IFS types would lock up when using a disk video mode wi=
th
a
> resolution greater that 2048 =


OK, I'll look into this. <<

I've fixed it.  It's a two part solution.  If the resolution is greater
than OLDMAXPIXELS we don't use the grid.  I had thought we were forcing
floating point for this condition, but I don't see it.  I put that in. =

And, therefore, even if the fractal has an integer type, if we aren't usi=
ng
the grid, we shouldn't do the calculations for the integer grid.  This la=
st
is what was causing the infinite loop.

I'll put it in my next patch.  I should put one up this week.  I'm headin=
g
back to Iowa on Friday.

Jonathan

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: Re: Lsystem/IFS bug
Date: 14 Feb 2000 17:07:44 -0600

Jonathan wrote:

> I've fixed it.  It's a two part solution.  If the resolution is greater
> than OLDMAXPIXELS we don't use the grid.  I had thought we were forcing
> floating point for this condition, but I don't see it.  I put that in.
> And, therefore, even if the fractal has an integer type, if we aren't using
> the grid, we shouldn't do the calculations for the integer grid.  This last
> is what was causing the infinite loop.

That is about what I would expect, good job!

> I'll put it in my next patch.  I should put one up this week.  I'm heading
> back to Iowa on Friday.


I'll bet you'll be glad to get home!

Tim


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Phil McRevis <[e-mail]>
Subject: Re: (fractint) Hi there, and a small question to get me started!
Date: 18 Feb 2000 10:14:25 -0700


In article <[e-mail]>,
    "Morgan L. Owens" <[e-mail]>  writes:

> Has there been any discussion on what sort of architecture a future
> Fractint might have?

There has been tons of discussion and even some work from yours truly
before my free time evaporated ;-).

The best thing to do if you're thinking of contributing is to join the
fractint developer's mailing list: send mail to [e-mail]
with 'subscribe fractdev' in the message body.  You can also peruse
the archives of what's been said before on that list at
<ftp://ftp.xmission.com/pub/lists/fractdev/>.

I'd like to humbly suggest that all development threads continue on
the fractdev list and not the fractint list, so as to not bore users
with long threads full of programming details.

I can summarize what's transpired before:

1) fractint needs a 'driver model' in its source code to isolate the
main body of code from things that are platform specific.  'Platform'
here refers to a combination of compiler support, operating system
support, keyboard/mouse input support and of course screen output.

2) Designing this support for fractint's existing code base requires
someone who has a 'high level' view of the code so as to make sure
that nothing major is missing in the design.

3) fractint has a LARGE code base.  Printing out the source code in
a double-sided listing results in a stack that is literally 6 inches
thick.  Getting the 'high level' view is time consuming!

4) The 'driver model' should be introduced into the code in such a
fashion that it doesn't require an entire rewrite.

5) Modern platform environments are event-driven (X11, Win32, MacOS,
BeOS), and don't use a polling I/O model like DOS.  Fractint currently
uses a polling I/O mechanism but xfractint snuck in a way to treat
this through events.  It has some warts, but it does work.  The better
long term solution is to reorganize the code into an event-driven
paradigm, but that can wait until after item 4.

I've done 1-3 and part of 4.  Once I got the 'big picture', the job
wasn't as hard as I thought it would be at first.  I think my approach
will unify ports to X11, Win32 and MacOS.  DOS may still work, but it
is a low priority for me ;-).

However, while doing item 4 I ran out of spare cycles to work on
fractint.  I have a code base that is partially completed and still
compiles/limps along on X11, but it needs more work.
--
<http://www.xmission.com/~legalize/>    Legalize Adulthood!
    ``Ain't it funny that they all fire the pistol,
      at the wrong end of the race?''--PDBT
[e-mail]    <http://www.xmission.com/~legalize/who/>

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Morgan L. Owens" <[e-mail]>
Subject: Future Fractint - Speculations
Date: 19 Feb 2000 22:56:46 +1300

<--Decloaking in order to mouth off.-->

   Caveat: I'm not enough of the right sort of programmer to assist
   directly with developing the Fractint code. What follows
   concentrates entirely on generalities and does not go near the
   specifics. Those with appropriate expertise are welcome to provide
   these.


I've been wondering what Fractint will look like in the future. I know
it will be a big job getting it out from under its legacy of late-80s
technology and into something that's not tied down at one end to MS-DOS
and at the other to 256 indexed colour. So I thought it would make sense
to develop something for which the impact from changing platform and
display technology could be compartmentalised, leaving the core Fractint
code itself as untouched as possible.

All this was dreamed up in blissful ignorance; I don't know what it
would like to implement such a model, or how appropriate it may be for
Fractint, or how much like current reengineering efforts it resembles.

This model may fall flat on its face: Java programs run on a virtual
machine which is supposed to insluate it from the peculiarities of the
operating system, but "write once, run anywhere" has yet to properly
eventuate; whether a platform-independent Fractint engine as suggested
here can be sufficiently separated from the platform and still remain
nontrivial has yet to be established.



It comes in four tiers:

1st tier: Speed-critical code library
  Processor-specific assembler is written to take advantage of each
  architecture's particular programming features, such as Pentium's
  triple-precision arithmetic, or the G4's vector operations. For each
  supported architecture a library of such code will be provided. Note
  that the interface for the libraries will all be identical: we're
  insulating the engine from the hardware.

2nd tier: Fractint engine
  Written as portably as possible; does Fractint specific computations.
  The engine includes code for emulating the processor library should
  (parts of) the latter not be available; it'd be a fair sight slower,
  but it will run.

3rd tier: OS-specific shell
  Accommodates the specific details of the soft half of the platform.
  Memory management, filesystem, device I/O - all the donkey work of
  programming for modern systems. One interesting 3rd-tier
  implementation could be a shell for a Photoshop / PSP plugin - in this
  case the image processing application is the "OS". Tasks handled by
  this tier are not to be confused with...

4th tier: Chrome
  The user interface. Bells and whistles, widgets and commands are
  thrown about here. Includes command-line interfaces.

  This has been separated from the 3rd tier so that customised
  interfaces can be written that go beyond merely skinning a
  predetermined UI. vaguely suggestive of this is Robin Bussell's Paste
  & Go utility, (though only suggestive, of course, as it then hands
  control off to Fractint).

  One development of Chrome may be a Fractint-by-net client app. This
  could be served either by a standard 3rd-tier shell with server
  chrome, or a multiprocessing shell that can subdivide and distribute
  requested rendering jobs.

  For the Photoshop plugin shell, the Chrome tier would reduce to a thin
  gilt that does Fractint<->Photoshop API translations. The shell would
  also be much reduced in size from those of standalone applications,
  largely piggybacking off Photoshop. In this specialised situation, the
  Chrome and shell may as well be merged into the one "fractint.8bf"
  file. The Fractint engine will remain separate, but there is already
  fair precendent of this kind of arrangement in existing Photoshop
  plugins.



Considerations of how each tier operates internally are not the concern
here, except for how a tier's internal implementation affects its
interaction with its neighbours.

Once interfacing issues between these tiers is established, development
on each tier could proceed more-or-less independently of the others; for
example, work on a Mac OS X port need only concentrate on the third
and fourth tiers (assuming that the engine was written as to be as OS-
unspecific as it should have been), and even the initial chrome can be a
Spartan affair without hampering the shell development. Having checked
that the engine is working to spec and written the shell, _then_ work
can begin on a hard-working G4 library and an all-singing all-dancing
Aqua interface.

Nevertheless, initial development will see all four tiers being
developed simultaneously, since aforementioned interfacing issues have
to be dealt with; and that can only be by establishing just what needs
doing, where it needs to be implemented and for those tasks that
need to straddle tier boundaries, just what needs to be passed between
the tiers in order to achieve them and in what form. For example, the
library does not need to know the screen coordinates of the point
currently being iterated on, but it does need to know its location in
the fractal's own coordinate system. (The two coordinate systems may
match, but that's the engine's concern, as is whether it's using
boundary-trace or one-pass drawing methods). Similarly, the shell does
not need to know how to parse a user formula or compile one into library
instructions, but it does need to know how to read one from the disk.
(The shell does need to understand enough about what a user formula
looks like to know where one starts and ends, but it doesn't have to
go into any more detail than that.)

With four tiers operating, with each insulating those above from those
below, there are four APIs that need to be developed, with two of them
(the engine's and the shell's) consisting of both "upward" and
"downward" interfacing.

Needless to say, dividing the code base in this way will lead to a more
fluid pace for Fractint development, with new platforms being
accommodated for, new versions of existing tiers being written, and a
variety of user interfaces to select from. So I can already see one
component of the interface: getVersion() returns a (read-only) string
for purposes of identification. This shouldn't be used to switch between
blocks of code at higher tiers (except maybe the 4th). Rather, it is to
allow display of the various version numbers in the user's
implementation in something like:
"Fractint v21.1 * PentiumIII v1.5 * Redhat Linux v6.1 * GooView v0.beta."
representing the versions of respectively the engine, the library, the
shell, and the chrome.

Licensing and distribution would be on a per-component basis decided by
the authors. Apart from new versions, the engine itself would remain
consistent across all implementations and would be identified (as
indicated in the previous paragraph) as being the one true Fractint.
Processor libraries, OS shells and interface chrome would be distributed
as separate components, although "default" implementations of each of
these must be distributed with the Fractint engine under the same terms
as Fractint itself (this goes for source code as well as precompiled
incarnations). Alternate implementations of each of these components
(with the exception of the engine) may be distributed in other ways and
under other licenses at the discretion of the author(s).

Well, that's what I was thinking.

<Engaging Lurk Mode(?)>

Morgan L. Owens
"Fractint: The Next Generation"



Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Jonathan" <[e-mail]>
Subject: Buglist
Date: 20 Feb 2000 20:43:33 -0600

This is a multi-part message in MIME format.

------=_NextPart_000_000C_01BF7BE3.274FD840
Content-Type: text/plain;
    charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Tim,

Robin's buglist is back up.  Currently it only has two bugs on it.  I =
believe we have already fixed the first one.  That was the problem with =
the formula parser.  The second one is a problem that occurs when =
inside=3Dstartrail is used with the circle fractal type.  I haven't been =
able to track this one down.

Jonathan


------=_NextPart_000_000C_01BF7BE3.274FD840
Content-Type: text/html;
    charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Tim,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>Robin's buglist is back up.  Currently it only =
has two=20
bugs on it.  I believe we have already fixed the first one.  =
That was=20
the problem with the formula parser.  The second one is a problem =
that=20
occurs when inside=3Dstartrail is used with the circle fractal =
type.  I=20
haven't been able to track this one down.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>Jonathan</FONT></DIV>
<DIV> </DIV></BODY></HTML>

------=_NextPart_000_000C_01BF7BE3.274FD840--


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: Re: Buglist
Date: 20 Feb 2000 22:06:53 -0600


> Robin's buglist is back up.

Yes, so I restored the link to it at www.fractint.org

> Currently it only has two bugs on it.

I saved at later copy of it via browser save-as that has more recent
information, and have put it at

http://www.fractint.org/buglist.htm

Now folks, I am a compleat idiot about html, but if you enter a bug
using the above link it updates the buglist at Robin's site <grin!> If
you look at Robin's site, there is a stupid test bug I entered in
exactly that way.

Hopefully Robin will update the buglist with the this later copy.

I received the following today:

QUOTE
I seem to have lost your post referring to the developers list so will
pass this to you. The 'c' key has to be hit twice to start color
cycling. The '+' and '-' keys work normally. It threw me momentarily
when the screen just went to a solid color. Kind of a minor glitch
but there may be a deeper implication.
END QUOTE

Tim



Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Jonathan Osuch" <[e-mail]>
Subject: Re: Buglist
Date: 21 Feb 2000 10:13:45 -0600

Tim,

> QUOTE
> I seem to have lost your post referring to the developers list so will
> pass this to you. The 'c' key has to be hit twice to start color
> cycling. The '+' and '-' keys work normally. It threw me momentarily
> when the screen just went to a solid color. Kind of a minor glitch
> but there may be a deeper implication.
> END QUOTE

It's worked that way as far back as version 15.1.

Jonathan




Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: [e-mail]
Subject: RE: Buglist
Date: 21 Feb 2000 12:18 0000

Hi Folks,

>Robin's buglist is back up.  Currently it only has two bugs on it.  I
>believe we have already fixed the first one.

Yep I managed to get in some html maintenance time this weekend...
and about time too!

I also didn't manage to find a very recent archive of the list so if anyone
has some later bugs I'd welcome a mailing of them.

I'm in the middle of sorting out the wishlist into more manageable
chunks too, I'll probably get rid of the rather underused 'comments from
stone soup group' frame too, any objections?

Oddly enough I couldn't access ftp.fractint.org over the weekend, it
was pingable but not accessable via FTP, did anyone else have this
problem?


Cheers,
         Robin.


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: [e-mail]
Subject: RE: Re: Buglist
Date: 21 Feb 2000 18:05 0000

>I saved at later copy of it via browser save-as that has more recent
>information, and have put it at
>
>http://www.fractint.org/buglist.htm

AHA! thanks Tim, I'll sort that out.


> if you enter a bug
>using the above link it updates the buglist at Robin's site <grin!> If

That's because the form still sends all it' s info to ukonline's server
where
the CGI script there merrily updates my page if you look at the source
you'll find the address in the <form> tag.

BTW Tim, if you want me to take on the task of webmaster for
www.fractint.org I'd be glad to do so ( don't worry, I back things up
properly now, no more online disasters! )

> The 'c' key has to be hit twice to start color
>cycling.

This is more of a documentation problem methinks, for a long as I can
remember with fractint, the C key always entered cycle mode in
paused status. This makes sense if you want to select one of the preset
palettes without rotating the palette so that the colour intensity maps to
the iteration value.... and more obviously it's the key to hit before
(l)oading
or (s)aving a map file.

Overall more 'feature'  than 'bug' I'd say :-)

I've just finished reading "the cathedral and the bazaar" and the
followups...
good stuff! I'd recommend it to anyone here.

On the same trip to the bookstore ( well more like click to the
bookstore,
it was Amazon.co.uk) I picked  up The Algorithm Design Manual
which is chock full of good information on just about every problem
a programmer is likely to encounter, you can find some excerpts and
source code at the stony brook algorithm repository at:
http://www.cs.sunysb.edu/~algorith/
a good site if you're not into wheel re-invention :-)

Cheers,
         Robin.





Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Damien M. Jones" <[e-mail]>
Subject: RE: Buglist
Date: 21 Feb 2000 19:56:23 -0500

Robin,

 - Oddly enough I couldn't access ftp.fractint.org over the weekend,
 - it was pingable but not accessable via FTP, did anyone else have
 - this problem?

ftp.fractint.org is only for anonymous access. If you're trying to log in
with a name and password, you need to go through julia.fractalus.com. Also,
when the server was moved to its new location (now within walking distance
of my desk at work) somehow there was a foul-up and the FTP server wasn't
restarted. That's fixed, so that if the machine ever spontaneously reboots
it should restart the FTP server.

Damien M. Jones   \\
[e-mail]  \\  Fractalus Galleries & Info:
                    \\  http://www.fractalus.com/

Please do not post my e-mail address on a web site or
in a newsgroup.  Thank you.


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: RE: Re: Buglist
Date: 21 Feb 2000 19:53:21 -0600


> BTW Tim, if you want me to take on the task of webmaster for
> www.fractint.org I'd be glad to do so ( don't worry, I back things up
> properly now, no more online disasters! )

It's yours. I would like to have a page or two or maybe muck around
with what you do from time to time, but you are hereby the
webmaster.

My concept is to make Fractint.org more the developer's
headquarters, and to have a prominent link to spanky for the user
pages, until such a time as Noel can no longer maintain his pages
or for whatever reason doesn't want to. Our main page could have
more than one link to his page.

I can help back up the page via FTP. Have you gotten your ssh
account to work?

Tim


>
> > The 'c' key has to be hit twice to start color
> >cycling.
>
> This is more of a documentation problem methinks, for a long as I can
> remember with fractint, the C key always entered cycle mode in
> paused status. This makes sense if you want to select one of the preset
> palettes without rotating the palette so that the colour intensity maps to
> the iteration value.... and more obviously it's the key to hit before
> (l)oading
> or (s)aving a map file.
>
> Overall more 'feature'  than 'bug' I'd say :-)
>
> I've just finished reading "the cathedral and the bazaar" and the
> followups...
> good stuff! I'd recommend it to anyone here.
>
> On the same trip to the bookstore ( well more like click to the
> bookstore,
> it was Amazon.co.uk) I picked  up The Algorithm Design Manual
> which is chock full of good information on just about every problem
> a programmer is likely to encounter, you can find some excerpts and
> source code at the stony brook algorithm repository at:
> http://www.cs.sunysb.edu/~algorith/
> a good site if you're not into wheel re-invention :-)
>
> Cheers,
>          Robin.
>
>
>
>
>
> --------------------------------------------------------------
> Thanks for using Fractdev, The Fractint Developer's Discussion List
> Post Message:   [e-mail]
> Get Commands:   [e-mail] "help"
> Administrator:  [e-mail]
> Unsubscribe:    [e-mail] "unsubscribe fractdev"



Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Damien M. Jones" <[e-mail]>
Subject: RE: Re: Buglist
Date: 21 Feb 2000 22:22:41 -0500

Robin, Tim,

 - > BTW Tim, if you want me to take on the task of webmaster for
 - > www.fractint.org I'd be glad to do so ( don't worry, I back
 - > things up properly now, no more online disasters! )
 -
 - It's yours. I would like to have a page or two or maybe muck
 - around with what you do from time to time, but you are hereby
 - the webmaster.

I've transferred ownership of the files in the web site directory to Robin.

 - I can help back up the page via FTP.

wget is installed if you want to write some scripts to automate fetching
the web page via HTTP. I can grant Robin cron privileges, if you want to go
that route.

Damien M. Jones   \\
[e-mail]  \\  Fractalus Galleries & Info:
                    \\  http://www.fractalus.com/

Please do not post my e-mail address on a web site or
in a newsgroup.  Thank you.


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Scott D. Boyd" <[e-mail]>
Subject: Xfractint 3.11 binary
Date: 22 Feb 2000 00:10:24 -0600

I know most everyone on this list would probably compile their own Xfractint,
but I thought I'd go ahead and announce my update to my Xfractint binary under
Linux.

A binary package of Xfractint 3.11, based on fractint 20.0.7 is now avaible at:
http://www.fastlane.net/~sdboyd/xfractint.html .
(The link to download the .tar.gz file is available on that page.) This binary
was compiled and is running great on Linux-Mandrake 6.1, kernel 2.2.13, xfree86
3.3.5 and KDE 1.1.2. (That setup is running on an AMD K6-2 - 450Mhz box.)

Scott D. Boyd
 --
email:  [e-mail]
http://www.fastlane.net/~sdboyd/
Introducing -- Windows 2000 !!
(Don't try this at home... or at work, either.)


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Phil McRevis <[e-mail]>
Subject: Re: open source resource
Date: 23 Feb 2000 10:05:15 -0700


In article <[e-mail]>,
    "Damien M. Jones" <[e-mail]>  writes:

> Xmission has far more in the way of resources than I do, but they may not
> always be willing to use those resources. I don't know. Xmission seems to
> be pretty "with it" for an ISP.

Swinging resources on the Xmission side is no problem; "the owner is a
personal friend of mine" ;-).  Also, I don't mind ponying up a little
cash if that's what xmission requires.
--
<http://www.xmission.com/~legalize/>    Legalize Adulthood!
    ``Ain't it funny that they all fire the pistol,
      at the wrong end of the race?''--PDBT
[e-mail]    <http://www.xmission.com/~legalize/who/>

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Jonathan Osuch" <[e-mail]>
Subject: WinFract Source
Date: 27 Feb 2000 15:37:01 -0600

Tim,

Is the WinFract source available?  Do we want to have it available on
fractint.org?

Jonathan



Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Jonathan Osuch" <[e-mail]>
Subject: Bug list
Date: 27 Feb 2000 15:35:15 -0600

Robin,

Have any responses been sent to people reporting bugs to the bug list?  If
not, I'll do that for the ones I know about.

Jonathan



Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Jonathan Osuch" <[e-mail]>
Subject: ismand in jiim.c
Date: 27 Feb 2000 16:47:04 -0600

Tim,

Do you have any recollection of why you included the line with ismand in
JIIM.C?  If you do a cntrl-<o> on a partially completed formula image that
uses ismand, this line swaps the fractal type.  I don't think that was
intended.  This bug is on the bug list.

Jonathan



Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Phil McRevis <[e-mail]>
Subject: Re: WinFract Source
Date: 28 Feb 2000 12:46:32 -0700


In article <003e01bf816b$68fc1d20$d7d4b5d1@bananasenior>,
    "Jonathan Osuch" <[e-mail]>  writes:

> Is the WinFract source available?

It is available, but it lags the current fractin/xfractint somewhat.
I believe winfract was last synched to the source base at version
18.2
--
<http://www.xmission.com/~legalize/>    Legalize Adulthood!
    ``Ain't it funny that they all fire the pistol,
      at the wrong end of the race?''--PDBT
[e-mail]    <http://www.xmission.com/~legalize/who/>

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: Re: Bug list
Date: 28 Feb 2000 16:56:45 -0600

Jonathan asked:

> Have any responses been sent to people reporting bugs to the bug list?  If
> not, I'll do that for the ones I know about.

(I just got back from out of town, a quick trip to Baltimore to visit
my son at his college.)

I'd prefer that we edit the buglist directly and state the resolution of
the bug. That would be easy to do if Robin could rehost the buglist
at fractint.org. Otherwise Robin will have to do it himself. Or maybe
Robin will be inspired to give us a tool to edit th status of the bug.

The reason for doing it this way is so users can check the list
before they report a bug, and so we can keep track of where we are.

We need some categories like open, reproduced, fixed in version
x.y.z or some such.

Tim

------- End of forwarded message -------

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Phil McRevis <[e-mail]>
Subject: Re: WinFract Source
Date: 28 Feb 2000 16:03:33 -0700


In article <003e01bf816b$68fc1d20$d7d4b5d1@bananasenior>,
    "Jonathan Osuch" <[e-mail]>  writes:
> Is the WinFract source available?

I stuck this at
<ftp://ftp.xmission.com/pub/users/l/legalize/fractals/>
--
<http://www.xmission.com/~legalize/>    Legalize Adulthood!
    ``Ain't it funny that they all fire the pistol,
      at the wrong end of the race?''--PDBT
[e-mail]    <http://www.xmission.com/~legalize/who/>

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Phil McRevis <[e-mail]>
Subject: Re: Bug list
Date: 28 Feb 2000 16:04:30 -0700


In article <[e-mail]>,
    Tim Wegner <[e-mail]>  writes:

> The reason for doing it this way is so users can check the list
> before they report a bug, and so we can keep track of where we are.
>
> We need some categories like open, reproduced, fixed in version
> x.y.z or some such.

I don't know what sourcegear or whatever offers in the way of bug
tracking, but there is the GNU gnats package that tracks bug reports.

--
<http://www.xmission.com/~legalize/>    Legalize Adulthood!
    ``Ain't it funny that they all fire the pistol,
      at the wrong end of the race?''--PDBT
[e-mail]    <http://www.xmission.com/~legalize/who/>

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Morgan L. Owens" <[e-mail]>
Subject: Re: Bug list
Date: 29 Feb 2000 13:26:33 +1300

At 16:04 28/02/2000 -0700, you wrote:
>
>In article <[e-mail]>,
>    Tim Wegner <[e-mail]>  writes:
>
>> The reason for doing it this way is so users can check the list
>> before they report a bug, and so we can keep track of where we are.
>>
>> We need some categories like open, reproduced, fixed in version
>> x.y.z or some such.
>
>I don't know what sourcegear or whatever offers in the way of bug
>tracking, but there is the GNU gnats package that tracks bug reports.
>
Mozilla.org has made its bug-tracking/development environment available
from their site.

Morgan L. Owens



Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Jonathan Osuch" <[e-mail]>
Subject: Re: Bug list
Date: 28 Feb 2000 20:26:25 -0600

Tim responded:

> I'd prefer that we edit the buglist directly and state the resolution of
> the bug. That would be easy to do if Robin could rehost the buglist
> at fractint.org. Otherwise Robin will have to do it himself. Or maybe
> Robin will be inspired to give us a tool to edit th status of the bug.
>
> The reason for doing it this way is so users can check the list
> before they report a bug, and so we can keep track of where we are.
>
> We need some categories like open, reproduced, fixed in version
> x.y.z or some such.

I agree.  However, I think we need to directly contact the reporters of bugs
to let them know the bugs have been fixed and where they can find an updated
executable.  Granted, except for actually contacting people, we can do all
that with editing the bug list.  Just a thought.

Jonathan



Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: Re: ismand in jiim.c
Date: 28 Feb 2000 22:54:59 -0600

Jonathan  asked:

> Do you have any recollection of why you included the line with ismand in
> JIIM.C?  If you do a cntrl-<o> on a partially completed formula image that
> uses ismand, this line swaps the fractal type.  I don't think that was
> intended.  This bug is on the bug list.

That change is in patch 1960p5.dif. I'm not positive whose patch it was, but
probably George's.

If that line is not needed for orbits it could be changed by protecting it with
   if(which != ORBIT)
   {
      ismand = (short)(1 - ismand);
   }


Here's the whole diff in case you don't have it.

Tim

*** FRAMAIN2.C    Fri May 30 00:22:20 1997
--- \fractint\FRAMAIN2.C    Sat May 31 22:20:52 1997
***************
*** 1515,1519 ****
     current.old_demm_colors = (short)old_demm_colors;
     current.logcalc         = (short)Log_Fly_Calc;
!    current.ismand          = ismand;
     far_memcpy(current.dac,dacbox,256*3);
     switch(fractype)
--- 1515,1519 ----
     current.old_demm_colors = (short)old_demm_colors;
     current.logcalc         = (short)Log_Fly_Calc;
!    current.ismand          = (short)ismand;
     far_memcpy(current.dac,dacbox,256*3);
     switch(fractype)
*** PROMPTS1.C    Sat Mar 15 13:52:58 1997
--- \fractint\PROMPTS1.C    Sun Jun  1 14:25:52 1997
***************
*** 1534,1537 ****
--- 1534,1543 ----
     }

+    if((curtype==FORMULA || curtype==FFORMULA) && uses_ismand) {
+       choices[promptnum] = (char far *)s_ismand;
+       paramvalues[promptnum].type = 'y';
+       paramvalues[promptnum++].uval.ch.val = ismand?1:0;
+    }
+
     if (caller                           /* <z> command ? */
  /*      && (display3d > 0 || promptnum == 0)) */
***************
*** 1651,1658 ****
               paramvalues[promptnum+1].uval.ch.val != minor_method)
              ret = 1;
!          major_method = (enum Major)paramvalues[promptnum  ].uval.ch.val;
!          minor_method = (enum Minor)paramvalues[promptnum+1].uval.ch.val;
        }
!
  gfp_exit:
     curfractalspecific = &fractalspecific[fractype];
--- 1657,1672 ----
               paramvalues[promptnum+1].uval.ch.val != minor_method)
              ret = 1;
!          major_method = (enum Major)paramvalues[promptnum++].uval.ch.val;
!          minor_method = (enum Minor)paramvalues[promptnum++].uval.ch.val;
        }
!      if((curtype==FORMULA || curtype==FFORMULA) && uses_ismand)
!      {
!         if (ismand != (short int)paramvalues[promptnum].uval.ch.val)
!         {
!            ismand = (short int)paramvalues[promptnum].uval.ch.val;
!            ret = 1;
!         }
!         ++promptnum;
!      }
  gfp_exit:
     curfractalspecific = &fractalspecific[fractype];
*** PARSER.C    Fri May 30 00:22:22 1997
--- \fractint\PARSER.C    Sun Jun  1 21:22:14 1997
***************
*** 86,90 ****
  void (far * far *f)(void) = (void(far * far *)(void))0; /* static CAE fp */

! int ismand = 1;

  unsigned posp, vsp, LastOp;     /* CAE fp made non-static */
--- 86,90 ----
  void (far * far *f)(void) = (void(far * far *)(void))0; /* static CAE fp */

! short int ismand = 1;

  unsigned posp, vsp, LastOp;     /* CAE fp made non-static */
***************
*** 100,104 ****
  static int Randomized;
  static unsigned long RandNum;
! int uses_p1, uses_p2, uses_p3, uses_jump;

  #ifndef XFRACT
--- 100,105 ----
  static int Randomized;
  static unsigned long RandNum;
! short uses_p1, uses_p2, uses_p3, uses_jump;
! short uses_ismand;

  #ifndef XFRACT
***************
*** 1689,1692 ****
--- 1690,1695 ----
              if(n == 8)        /* The formula uses 'p3'. */
                 uses_p3 = 1;
+             if(n == 13)        /* The formula uses 'ismand'. */
+                uses_ismand = 1;
              if(n == 10 || n == 11 || n == 12)
                 if(MathType == L_MATH)
***************
*** 3188,3192 ****
     Delta16 = bitshift - 16;
     bitshiftless1 = bitshift-1;
!    uses_p1 = uses_p2 = uses_p3 = uses_jump = 0;
  }

--- 3191,3195 ----
     Delta16 = bitshift - 16;
     bitshiftless1 = bitshift-1;
!    uses_p1 = uses_p2 = uses_p3 = uses_jump = uses_ismand = 0;
  }

*** JIIM.C    Fri May 30 00:22:22 1997
--- \fractint\JIIM.C    Sun Jun  1 21:24:54 1997
***************
*** 986,989 ****
--- 986,990 ----
              default:
                 still = 0;
+                ismand = (short)(1 - ismand);
              }  /* switch */
              if(kbdchar == 's' || kbdchar == 'S')
*** MISCRES.C    Sat May  3 14:38:02 1997
--- \fractint\MISCRES.C    Sun Jun  1 13:18:40 1997
***************
*** 815,819 ****
     sprintf(msg,"xdots %d ydots %d sxdots %d sydots
%d",xdots,ydots,sxdots,sydots);
     putstring(s_row++,2,C_GENERAL_HI,msg);
!    sprintf(msg,"xxstart %d xxstop %d yystart %d yystop %d %s ",
        xxstart,xxstop,yystart,yystop,
  #ifndef XFRACT
--- 815,819 ----
     sprintf(msg,"xdots %d ydots %d sxdots %d sydots
%d",xdots,ydots,sxdots,sydots);
     putstring(s_row++,2,C_GENERAL_HI,msg);
!    sprintf(msg,"xxstart %d xxstop %d yystart %d yystop %d %s
uses_ismand %d",
        xxstart,xxstop,yystart,yystop,
  #ifndef XFRACT
***************
*** 822,826 ****
        curfractalspecific->orbitcalc ==  Formula?"slow parser":
        curfractalspecific->orbitcalc ==  BadFormula?"bad formula":
!       "");
     putstring(s_row++,2,C_GENERAL_HI,msg);
  /*
--- 822,826 ----
        curfractalspecific->orbitcalc ==  Formula?"slow parser":
        curfractalspecific->orbitcalc ==  BadFormula?"bad formula":
!       "",uses_ismand);
     putstring(s_row++,2,C_GENERAL_HI,msg);
  /*
*** REALDOS.C    Fri May 30 00:22:22 1997
--- \fractint\REALDOS.C    Sun Jun  1 21:15:02 1997
***************
*** 26,30 ****
  */
  int release=1960;  /* this has 2 implied decimals; increment it every synch
*/
! int patchlevel=4; /* patchlevel for DOS version */
  #ifdef XFRACT
  int xrelease=304;
--- 26,30 ----
  */
  int release=1960;  /* this has 2 implied decimals; increment it every synch
*/
! int patchlevel=5; /* patchlevel for DOS version */
  #ifdef XFRACT
  int xrelease=304;
***************
*** 323,327 ****
  #else
     if (debugflag == 3002) return;
! /* #define DEVELOPMENT */
  #ifdef DEVELOPMENT
     putstring(0,2,C_TITLE_DEV,"Development Version");
--- 323,327 ----
  #else
     if (debugflag == 3002) return;
! #define DEVELOPMENT
  #ifdef DEVELOPMENT
     putstring(0,2,C_TITLE_DEV,"Development Version");
*** ENCODER.C    Fri May 30 00:22:22 1997
--- \fractint\ENCODER.C    Sun Jun  1 20:43:50 1997
***************
*** 794,797 ****
--- 794,799 ----
        fsave_info.uses_p2 = (short) uses_p2;
        fsave_info.uses_p3 = (short) uses_p3;
+       fsave_info.uses_ismand = (short) uses_ismand;
+       fsave_info.ismand = (short) ismand;
     }
     else
***************
*** 800,803 ****
--- 802,807 ----
        fsave_info.uses_p2 = 0;
        fsave_info.uses_p3 = 0;
+       fsave_info.uses_ismand = 0;
+       fsave_info.ismand = 0;
     }
     for (i = 0; i < sizeof(fsave_info.future) / sizeof(short); i++)
***************
*** 951,955 ****
     save_info->logcalc = (short) Log_Fly_Calc;
     save_info->stoppass = (short) stoppass;
-    save_info->ismand = (short) ismand;
     for (i = 0; i < sizeof(save_info->future) / sizeof(short); i++)
        save_info->future[i] = 0;
--- 955,958 ----
*** LOADFILE.C    Fri May 30 00:22:22 1997
--- \fractint\LOADFILE.C    Sun Jun  1 20:42:58 1997
***************
*** 292,296 ****
        Log_Fly_Calc = read_info.logcalc;
        stoppass     = read_info.stoppass;
-       ismand       = read_info.ismand;
     }

--- 292,295 ----
***************
*** 368,371 ****
--- 367,372 ----
                  uses_p2 = blk_3_info.uses_p2;
                  uses_p3 = blk_3_info.uses_p3;
+                 uses_ismand = blk_3_info.uses_ismand;
+                 ismand = blk_3_info.ismand;
                  break;
               }
***************
*** 569,572 ****
--- 570,575 ----
                       blk_3_info->uses_p2 = 1;
                       blk_3_info->uses_p3 = 1;
+                      blk_3_info->uses_ismand = 0;
+                      blk_3_info->ismand = 1;
                    }
                    else {
***************
*** 574,577 ****
--- 577,582 ----
                       blk_3_info->uses_p2 = fload_info.uses_p2;
                       blk_3_info->uses_p3 = fload_info.uses_p3;
+                      blk_3_info->uses_ismand = fload_info.uses_ismand;
+                      blk_3_info->ismand = fload_info.ismand;
                    }
                    break;
*** CMDFILES.C    Fri May 30 00:22:22 1997
--- \fractint\CMDFILES.C    Sun Jun  1 20:46:58 1997
***************
*** 1481,1485 ****
     if (far_strcmp(variable,s_ismand) == 0 ) {        /* ismand=? */
        if (yesnoval[0] < 0) goto badarg;
!       ismand = yesnoval[0];
        return 1;
        }
--- 1481,1485 ----
     if (far_strcmp(variable,s_ismand) == 0 ) {        /* ismand=? */
        if (yesnoval[0] < 0) goto badarg;
!       ismand = (short int)yesnoval[0];
        return 1;
        }
*** MISCOVL.C    Fri May 30 00:22:22 1997
--- \fractint\MISCOVL.C    Sun Jun  1 20:48:48 1997
***************
*** 576,581 ****
           put_filename(s_formulafile,FormFileName);
           put_parm( s_seqs,s_formulaname,FormName);
!          if (ismand == 0)
!             put_parm(" %s=n",s_ismand);
        }
        if (fractype == LSYSTEM)
--- 576,581 ----
           put_filename(s_formulafile,FormFileName);
           put_parm( s_seqs,s_formulaname,FormName);
!          if (uses_ismand)
!             put_parm(" %s=%c",s_ismand,ismand?'y':'n');
        }
        if (fractype == LSYSTEM)
*** FRACTINT.H    Fri May 30 00:22:24 1997
--- \fractint\FRACTINT.H    Sun Jun  1 20:17:02 1997
***************
*** 238,243 ****
      short logcalc;
      short stoppass;
!     short ismand;
!     short future[23];     /* for stuff we haven't thought of yet */
  };

--- 238,242 ----
      short logcalc;
      short stoppass;
!     short future[24];     /* for stuff we haven't thought of yet */
  };

***************
*** 345,349 ****
      short uses_p2;
      short uses_p3;
!     short future[10];       /* for stuff we haven't thought of, yet */
  };

--- 344,350 ----
      short uses_p2;
      short uses_p3;
!     short uses_ismand;
!     short ismand;
!     short future[8];       /* for stuff we haven't thought of, yet */
  };

***************
*** 855,861 ****
     int length;
     char form_name[40];
!    int uses_p1;
!    int uses_p2;
!    int uses_p3;
     };

--- 856,864 ----
     int length;
     char form_name[40];
!    short uses_p1;
!    short uses_p2;
!    short uses_p3;
!    short uses_ismand;
!    short ismand;
     };

*** EXTERNS.H    Fri May 30 00:22:24 1997
--- \fractint\EXTERNS.H    Sun Jun  1 21:22:44 1997
***************
*** 205,209 ****
  extern int                   invert;
  extern int                   istruecolor;
! extern int                   ismand;
  extern int                   ixstart;
  extern int                   ixstop;
--- 205,209 ----
  extern int                   invert;
  extern int                   istruecolor;
! extern short                 ismand;
  extern int                   ixstart;
  extern int                   ixstop;
***************
*** 716,722 ****
  extern BYTE                  used_extra;
  extern BYTE                  usemag;
! extern int                   uses_p1;
! extern int                   uses_p2;
! extern int                   uses_p3;
  extern int                   use_old_distest;
  extern int                   use_old_period;
--- 716,723 ----
  extern BYTE                  used_extra;
  extern BYTE                  usemag;
! extern short                 uses_ismand;
! extern short                 uses_p1;
! extern short                 uses_p2;
! extern short                 uses_p3;
  extern int                   use_old_distest;
  extern int                   use_old_period;
*** HELP.SRC    Fri May 30 00:22:24 1997
--- \fractint\HELP.SRC    Sun Jun  1 21:42:24 1997
***************
*** 268,272 ****
  ~Topic=New Features in 19.7
  Version 19.7 is an update of Fractint based on the developer's
!   version 19.60 patch 3. New features include:
  Patch 4\
  Beginning of George's parser changes. Added support for formula
--- 268,277 ----
  ~Topic=New Features in 19.7
  Version 19.7 is an update of Fractint based on the developer's
!   version 19.60 patch 5. New features include:
! Patch 5\
! Additional changes for the formula Mandelbrot/Julia changes. Since
!   ismand is stored differently now, patch 4 GIFs using ismand won't
!   restore correctly.
!
  Patch 4\
  Beginning of George's parser changes. Added support for formula


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Thore Berntsen <[e-mail]>
Subject: RE: Bug list
Date: 29 Feb 2000 08:27:14 +0100

I have read Your discussions about the "new" Fractint. I hope You keep the
batch mode. It's very nice and useful (not only for screen savers)

Thore Berntsen
Norway

    -----Original Message-----
    From:    Tim Wegner [SMTP:[e-mail]]
    Sent:    28. februar 2000 23:57
    To:    [e-mail]
    Subject:    Re: Bug list

    Jonathan asked:

    > Have any responses been sent to people reporting bugs to the bug
list?  If
    > not, I'll do that for the ones I know about.

    (I just got back from out of town, a quick trip to Baltimore to
visit
    my son at his college.)

    I'd prefer that we edit the buglist directly and state the
resolution of
    the bug. That would be easy to do if Robin could rehost the buglist
    at fractint.org. Otherwise Robin will have to do it himself. Or
maybe
    Robin will be inspired to give us a tool to edit th status of the
bug.

    The reason for doing it this way is so users can check the list
    before they report a bug, and so we can keep track of where we are.

    We need some categories like open, reproduced, fixed in version
    x.y.z or some such.

    Tim

    ------- End of forwarded message -------

    --------------------------------------------------------------
    Thanks for using Fractdev, The Fractint Developer's Discussion List
    Post Message:   [e-mail]
    Get Commands:   [e-mail] "help"
    Administrator:  [e-mail]
    Unsubscribe:    [e-mail] "unsubscribe fractdev"

Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Jonathan Osuch" <[e-mail]>
Subject: Re: ismand in jiim.c
Date: 29 Feb 2000 16:53:23 -0600

Tim Responded,

>That change is in patch 1960p5.dif. I'm not positive whose patch it was,
but
>probably George's.

>If that line is not needed for orbits it could be changed by protecting it
with
>   if(which != ORBIT)
>   {
>      ismand = (short)(1 - ismand);
>   }

If ismand isn't used by orbits (it isn't), what is this statement doing
here?  The switch gets done in FRAMAIN2.C.  I believe it is an error.
Perhaps left over from an initial try at switching from mandel to julia.
I've taken it out in my version and have not seen any unexpected.  I'll look
at it in more depth tonight.

Jonathan




Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: Re: ismand in jiim.c
Date: 29 Feb 2000 18:08:16 -0600


> If ismand isn't used by orbits (it isn't), what is this statement doing
> here?  The switch gets done in FRAMAIN2.C.  I believe it is an error.

I think you are correct. I don't see any use for it. It isn't where
ismand is set for formula mandelbrot/julia toggle.

Tim


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: Wes Lower's notes
Date: 29 Feb 2000 18:33:52 -0600

I've just had an exchange of emails with Wes Loewer (Wesley & Jane
Loewer <[e-mail]>), the arbitrary precision library author. He
is teaching in Mombasa, Kenya, and  his wife Jane just had their third child.
Understandably, he hasn't had much time for Fractint. Some of his thoughts
about fractint are below, after this message.

Jonathan and I have discussed a more or less literal port of Fractint to the
djgpp environment as a first step.  We could keep this synched with
Xfractint. Once accomplished, we could begin a major purge of ugliness
required by the old memory model. Most of Wes's ideas are consistent with
this plan. We could also look at Rich's Xfractint changes and Paul de
Leeuw's Windows version code at the same time.

Tim

Wes's comments:

I sure wish I could get back into the programming scene.  There's so
much I'd like to do for Fractint.  Here's my personal wish list off
the top of my head:

- Convert everything to C++ and use overloaded functions/operators for all
the dozen different number formats we use.  Then go back and recode speed
critical parts in straight C (or even asm with gnu-gas?).  In the process,
get rid of some of the number formats which are not really needed anymore.
- Make center/mag the default storage.  Deep zooms could be stored with 2
big-numbers and 4 normal floating point numbers instead of 6 big-numbers.
Store numbers in binary/hex instead of (or in addition to) base ten in
.par files. - Impliment non-linear interpolation between points
(non-linear synchronous orbits) - Impliment real time zooming like the
Xaos program.  That's really slick. - Impliment a text mode for images
where you use different ascii characters instead of different colors.
This would be useful if you were debugging code in text mode. - make it
portable between MS-Windows/Xwindows/Linux SVGA-lib. - use PNG -
expand
the 3d capabilities to do simple, limited ray-tracing of 3d fractals - use
the formula parser to allow equations for Red, Green, Blue in 15/16/24 bit
images.  Instead of trying to hard code different methods of coloring
(maxit, zmag, bof, iter, real, ...), make it limitless by using formulas.


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: "Jonathan Osuch" <[e-mail]>
Subject: Re: ismand in jiim.c
Date: 29 Feb 2000 20:17:50 -0600

Tim,

>> If ismand isn't used by orbits (it isn't), what is this statement doing
>> here?  The switch gets done in FRAMAIN2.C.  I believe it is an error.

> I think you are correct. I don't see any use for it. It isn't where
> ismand is set for formula mandelbrot/julia toggle.

As it stands, yes, it's an error.  But, it got me to thinking about using a
view window to view the julia corresponding to the crosshair location, like
we use for the mandel/julia switch.  Except we wouldn't be able to use the
jiim() routine.  Perhaps a user alterable jmaxit would allow the calculation
to be quick enough to be practical.

Jonathan



Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"


-------------------------------------------------------------------------------

From: Tim Wegner <[e-mail]>
Subject: Re: ismand in jiim.c
Date: 29 Feb 2000 22:21:48 -0600

Jonathan,

> As it stands, yes, it's an error.  But, it got me to thinking about using a
> view window to view the julia corresponding to the crosshair location, like
> we use for the mandel/julia switch.  Except we wouldn't be able to use the
> jiim() routine.

We could if we allowed a way to code up the inverse of the iteration
formula in the parser.

But I think this is low priority compared to truecolor support. :-)

Tim


Thanks for using Fractdev, The Fractint Developer's Discussion List
Post Message:   [e-mail]
Get Commands:   [e-mail] "help"
Administrator:  [e-mail]
Unsubscribe:    [e-mail] "unsubscribe fractdev"