ftp.xmission.com/2014.06.ftp.xmission.com.tar/ftp.xmission.com/pub/lists/fractdev/archive/v01.n031

Internet Message Format | 2000-06-02 | 41KB

From: [e-mail] (fractdev-digest)
To: [e-mail]
Subject: fractdev-digest V1 #31
Reply-To: fractdev-digest
Sender: [e-mail]
Errors-To: [e-mail]
Precedence: bulk


fractdev-digest          Friday, June 2 2000          Volume 01 : Number 031




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

Date: Sun, 9 Apr 2000 01:23:40 -0500
From: "Scott D. Boyd" <[e-mail]>
Subject: Re: Concatenated strings

Tim,

On Sun, 09 Apr 2000, you wrote:

> BTW  I saw a bug - when one cursor's around the fractal type list,
> sometimes the type name is written too far to the right, I need to
> look into this.
>
This doesn't happen to me in either 20.0.7 or 20.0.10. Does this happen to
you only in Xfractint? If so, it might be the terminal session you're using.
What terminal session are you using?

I have discovered what might be a bug in both Xfractint 20.0.7 and 20.0.10. In
the fractal-type list, select mandelcloud. Just leave the next parameter screen
as is and press Enter. Xfractint promptly exits and closes both windows without
even so much as a "Goodbye"!

Scott Boyd

 --
email:  [e-mail]
http://www.fastlane.net/~sdboyd/
Introducing Windows 2000 !! -- Reduced to only 65,000 bugs !!



- --------------------------------------------------------------
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"

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

Date: Sun, 9 Apr 2000 20:31:55 -0500
From: "Jonathan Osuch" <[e-mail]>
Subject: Re: Concatenated strings

Scott,

> I have discovered what might be a bug in both Xfractint 20.0.7 and
20.0.10. In
> the fractal-type list, select mandelcloud. Just leave the next parameter
screen
> as is and press Enter. Xfractint promptly exits and closes both windows
without
> even so much as a "Goodbye"!

Yes, that's a bug.  The cellular type does this also, when you press the
space bar twice.  I tried to find my list of known Xfractint problems to see
if this was on it, but it appears to be lost in the mists of time.  I'll
start a new list.  That way I'm sure to find the old one.

(later)  Yep, I found it while looking for something to respond to a
different email.  The type=mandelcloud isn't on it.

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"

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

Date: Fri, 14 Apr 2000 00:44:27 -0500
From: "Scott D. Boyd" <[e-mail]>
Subject: Bugs found in Xfractint 20.0.10

These bugs may or may not be local to my computer. Will someone
please try these on their Linux system? I am using Linux-Mandrake 6.1 with
kernel 2.0.13

Bug #1 only happens in Xfractint 20.0.10.
Bug #2 happens in both Xfractint 3.11 (Fractint 20.0.7) and Xfractint 20.0.10.

1: When ever I press Shift-2 (or '@') Xfractint shuts down.
   (This keypress works OK in Xfractint 3.11 (aka 20.0.7)).

2: Start Xfractint and draw the default fractal.
   Go back to the main menu
   Shell to Linux, then type exit to get back to Xfractint.
   "Press operation key, or <Esc> to return to Main Menu"
    will be messed up. (displayed as garbage characters)
   Press Esc to return to main menu
   Press 't' - Xfractint will shut down.
   Or press 'x' and change a parameter, then press 'Enter' -
   Xfractint will shut down.
Other menu keys will also cause Xfractint to shut down,
sometimes immediately, sometimes within 2-3 keypresses.

I thought this might be something wrong with my computer, so I re-booted into
Linux and KDE. Still encountered the two bugs. I also tried the above steps
while at the prompt (running Xfractint in diskvideo mode). Xfractint would shut
down, and also print "Segmentation fault" as the error message to the screen.


 Scott Boyd
- --
email:  [e-mail]
http://www.fastlane.net/~sdboyd/
Introducing Windows 2000 !! -- Reduced to only 65,000 bugs !!



- --------------------------------------------------------------
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"

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

Date: Fri, 14 Apr 2000 13:10:02 -0500
From: "Jonathan Osuch" <[e-mail]>
Subject: Re: Bugs found in Xfractint 20.0.10

Scott,

> These bugs may or may not be local to my computer. Will someone
> please try these on their Linux system? I am using Linux-Mandrake 6.1 with
> kernel 2.0.13

> Bug #1 only happens in Xfractint 20.0.10.
> Bug #2 happens in both Xfractint 3.11 (Fractint 20.0.7) and Xfractint
20.0.10.

Neither problem shows up on mine.  I'm using Linux-Mandrake 7.0 with kernel
2.0.14.

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"

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

Date: Sat, 15 Apr 2000 23:07:49 -0400
From: "Damien M. Jones" <[e-mail]>
Subject: Re: Bugs found in Xfractint 20.0.10

Hey gang,

 - > Bug #1 only happens in Xfractint 20.0.10.
 - > Bug #2 happens in both Xfractint 3.11 (Fractint 20.0.7) and Xfractint
 - 20.0.10.
 -
 - Neither problem shows up on mine.  I'm using Linux-Mandrake 7.0 with
 - kernel 2.0.14.

I just got Caldera's eDesktop (OpenLinux) installed on my home system as a
dual-boot with Windows 2000. If I get a chance this weekend, I'll give
Xfractint a shot and see what happens.

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"

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

Date: Mon, 17 Apr 2000 20:48:25 -0500
From: "Jonathan Osuch" <[e-mail]>
Subject: Allegro Graphics Package

Tim,

I'm looking seriously at the Allegro Graphics Package for use with Fractint.
The main reason is portability.  It has ports to djgpp, some Windows
compilers (Borland), Unix/Linux, and BEOS.  It includes drivers for mice,
sound, keyboard, and a high precision timer.

The svgalib package has specific video drivers (not VESA) which appears to
be very limiting.  OTOH, Allegro can use FreeBE/AF, a low level video driver
interface with all the features of VESA 3.0.

Are there any other packages we should look at?  Are there other
considerations?

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"

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

Date: Mon, 17 Apr 2000 22:01:50 -0600
From: Tim Wegner <[e-mail]>
Subject: Re: Allegro Graphics Package

Jonathan wrote:

> I'm looking seriously at the Allegro Graphics Package for use with Fractint.
> The main reason is portability.  It has ports to djgpp, some Windows
> compilers (Borland), Unix/Linux, and BEOS.  It includes drivers for mice,
> sound, keyboard, and a high precision timer.

Yes, Allegro is very portable, and as you said it has additional stuff
like sound we can use. It is meant for game programmers, but even
though we don't need it all, we can use it to good advantage.

> The svgalib package has specific video drivers (not VESA) which appears to
> be very limiting.

I didn't realize it wasn't VESA. That about rules it out IMHO.
Console graphics have to be VESA or we're dead. Although VESA
support for the higher resolutions is problematic on some boards
these days ...

>  OTOH, Allegro can use FreeBE/AF, a low level video driver
> interface with all the features of VESA 3.0.

That sounds good.

> Are there any other packages we should look at?  Are there other
> considerations?

I think that's about it for non-X operation. Going this route is just to
get us permanently into a 32 bit platform. The non-graphics
console itself will be getting more rare. However I still think this
would be a good step for us even if just a transition. And I'll bet the
console will be with us for a while yet. Does Allegro have an X
incarnation that can run in an Xterm?

The other relevant packages would be portable GUIs. The main
choices are WxWindows and GTK toolkit. But you don't have to
worry about that just yet. I think making a simple-minded port of
the DOS Fractint (maybe the float-only version) to djgpp/Linux
would be a good step, and not impossibly hard. These should be
maintained in synch with Xfractint, but leave the medium model
fractint behind.

Once accomplished, there are all kinds of global
cleanup/restructuring/rearchitecting that could be done. I hope we
can make use of some of Rich's X massage work.

I have two more Kalman filter classes, this Thursday and next,
then I hope I can free up some time for this. The perpetual dream
:-)

BTW Kalman filters are amazing. A Kalman filter is an algorithm for
taking measurements on the fly to calculate a state vector (as in
position and velocity of a spacecraft), but it is smart enough to
keep track of how good the measurements are, and to use the
better ones more, as well as keeping track of how good it's current
estimate of the state is, and factor that in along with the
measurements. This is, quite literally, rocket science :-). Wonderful
for orbit determination software.

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"

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

Date: Tue, 18 Apr 2000 09:08:24 -0400 (EDT)
From: [e-mail] (Kragen Sitaker)
Subject: Re: Allegro Graphics Package

Tim Wegner writes:
> > The svgalib package has specific video drivers (not VESA) which appears to
> > be very limiting.
>
> I didn't realize it wasn't VESA. That about rules it out IMHO.
> Console graphics have to be VESA or we're dead. Although VESA
> support for the higher resolutions is problematic on some boards
> these days ...

IIRC, there are problems running real-mode VESA drivers in
protected-mode Linux.  svgalib and X are Linux's answers to VESA.

About running Allegro in an xterm: xterm is more or less limited to
displaying text.  I've displayed graphics in xterms by using a small
font and displaying text, but this is slow and not recommended.
XwinAlleg opens a new window IIRC.

- --
<[e-mail]>       Kragen Sitaker     <http://www.pobox.com/~kragen/>
The Internet stock bubble didn't burst on 1999-11-08.  Hurrah!
<URL:http://www.pobox.com/~kragen/bubble.html>
The power didn't go out on 2000-01-01 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"

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

Date: Tue, 18 Apr 2000 11:39:22 -0600
From: Phil McRevis <[e-mail]>
Subject: Re: Allegro Graphics Package

Whatever you decide to use PLEASE introduce an abstraction layer that
is *not* allegro.  I feel this is very important if you really want to
keep portability.  Once you tie yourself to a particular package --
even one that claims to be portable and I've looked at allegro and its
not bad -- you also tie yourself to its weaknesses.  Please don't
design in another round of dependency weaknesses (like our current
dependency on DOS/VGA specifics), or we'll just have to fight this
battle again at some later date.  This was my intention behind the
driver abstraction that I massaged into the code.  It is not dependent
on anything specifically, it merely provides abstract function.
- --
<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"

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

Date: Tue, 18 Apr 2000 11:41:08 -0600
From: Phil McRevis <[e-mail]>
Subject: Re: Allegro Graphics Package

You really don't want to try and do graphics in an xterm!  Xterm is
not meant for that!  Its for text!

Unless you intend to provide a text-driver a la XaoS, I would advise
forgetting completely about anything running in an xterm.

One of the biggest kludges in xfractint right now is that you *must*
run it in an xterm and the code has all this crap littered everywhere
to deal with both curses *and* Xlib!  All that curses code needs to be
removed and text I/O should be done with xlib.  If that approach had
been taken originally, the xfractint code would be much simpler and
would support the PC key mappings better.
- --
<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"

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

Date: Tue, 18 Apr 2000 17:01:56 -0500
From: "Jonathan Osuch" <[e-mail]>
Subject: Re: Allegro Graphics Package

Tim wrote,

> Although VESA support for the higher resolutions is problematic on some
boards
> these days ...

That is the purpose of FreeBE/AF.  I believe it is similar (identical?) to
univbe.

> Does Allegro have an X incarnation that can run in an Xterm?

Allegro can use either X or svgalib under Linux.

> A Kalman filter is an algorithm for taking measurements on the fly to
calculate a state
> vector (as in position and velocity of a spacecraft), but it is smart
enough to keep track
> of how good the measurements are, and to use the better ones more, as well
as
> keeping track of how good it's current estimate of the state is, and
factor that in along
> with the measurements. This is, quite literally, rocket science :-).

Cool!  What are you going to do with this knowledge when you are done with
the class?

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"

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

Date: Tue, 18 Apr 2000 20:36:42 -0600
From: Tim Wegner <[e-mail]>
Subject: Re: Allegro Graphics Package

> Cool!  What are you going to do with this knowledge when you are done with
> the class?

I use it directly at work. I am working with GPS receiver models
that contain Kalman filters, and we use Kalman filters to do orbit
determination for the space shuttle and the space station.

Kalman filters can be used in almost any situation where
measurements are youse to calculate something.

I haven't figured out any application to fractals ...  yet :-)

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"

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

Date: Wed, 19 Apr 2000 16:20:30 -0500
From: "Scott D. Boyd" <[e-mail]>
Subject: Xfractint 20.0.10

I have been looking thru the source of Xfractint-20.0.10 trying to find the
reason why it crashes with a segfault whenever I press Shift-2 from the main
menu. I have discovered that the modified version of 20.0.9 that I worked on
(which I called xfractint-dev) doesn't crash. I had submitted the changes to Tim
Wegner, which he changed somewhat, and posted to the ftp server as
xfractint-20.0.10. I still need to go through the 20.0.9 source and apply my
original changes one-by-one, compile, and test.

Anyway.... Here's something interesting I have discovered:
When I run Xfractint in an xterm window, I can't use the Function keys. I need
to use the Shift-n keys as indicated in the man page. *But*, when I run
Xfractint in a Konsole window (KDE's version of xterm), the function keys work
fine. Apparently there are some differences in the way Konsole and Xterm map
the keyboard.

Tim - you told me that the Function keys worked fine in your Xfractint. Are you
running it from an xterm session, or something else?

Scott Boyd

- --
email:  [e-mail]
http://www.fastlane.net/~sdboyd/

- --------------------------------------------------------------
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"

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

Date: Wed, 19 Apr 2000 17:45:56 -0600
From: Tim Wegner <[e-mail]>
Subject: Re: Xfractint 20.0.10

Scott wrote:

> I had submitted the changes to Tim
> Wegner, which he changed somewhat,

Actually, I changed them a lot! I hope I didn't mess things up, by I
guess I did. The intent of my changes was just to eliminate many
of the #ifdef's. I didn't intend to actually change the executable
code from what you had. I guess I should look through the changes.

> Tim - you told me that the Function keys worked fine in your Xfractint. Are you
> running it from an xterm session, or something else?

KDE/Xterm session. I have a lot of trouble with
Gnome/Enlightenment. I am using Linux-Mandrake 7.0.

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"

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

Date: Fri, 21 Apr 2000 15:10:31 -0500
From: "Jonathan Osuch" <[e-mail]>
Subject: Patch 2000P11

Tim,

I put patch 11 on the ftp site, along with a DOS executable.  This patch is
so small for two reasons.  I intend to start the process of interfacing with
the Allegro package.  Using Rich's work as a starting point, of course.  I
don't want any bug fixes lost in the muck.

The second reason is that business will be taking me to Arkansas for the
next week or two and I won't be online.  I'll be around until Sunday
evening.

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"

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

Date: Fri, 28 Apr 2000 09:52:59 GMT
From: "Rupert Millard" <[e-mail]>
Subject: (fractint) 3d transform doesn't work in float only version

Hello,

I thought about putting this on the buglist but I think it's a fundamental
problem with float-only:

In the float-only version of Fractint 3d transforms don't work.

From,

Rupert

website: http://www.geocities.com/kangarupert
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com


- --------------------------------------------------------------
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"

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

Date: Sat, 13 May 2000 16:22:10 -0600
From: Tim Wegner <[e-mail]>
Subject: Re: (fractint) 3d transform doesn't work in float only version

Rupert wrote:

> I thought about putting this on the buglist but I think it's a fundamental
> problem with float-only:
>
> In the float-only version of Fractint 3d transforms don't work.

Thanks, I'll fix this. There are some integer math dependencies in
3D which won't pose any difficulty to fix.

Couple of news items.

1. My wife Susan and I had an enjoyable evening with Scott Boyd
and his wife Sarah in Galveston.

2. Jonathan had some problems with his laptop, but has recovered
and has merged the float-only version with Xfractint, and is working
on merging Rich's changes.

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"

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

Date: Sun, 14 May 2000 17:27:29 -0600
From: Tim Wegner <[e-mail]>
Subject: Re: (fractint) 3d transform doesn't work in float only version

I updated the FTP area so all the patch 11 files are now there. Let
me know if any problem. I also did chmod 664 for all the files, but I
couldn't change the files that Jonathan owns. It would probably be
good if either Jonathan or Damien changed the permissions to 664
so anyone in the group can delete or update the files. Not a big
deal though.

As part of his project, Jonathan merged the float-only version with
Xfractint, but didn't save the result of this before he started merging
in Rich's changes. I'll probably reconstruct this. Our "official"
Xfractint might as well be based on the float-only version since
Xfractint doesn't support integer math anyway.

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"

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

Date: Mon, 15 May 2000 00:23:15 -0400
From: "Damien M. Jones" <[e-mail]>
Subject: Re: (fractint) 3d transform doesn't work in float only version

Tim,

 - I also did chmod 664 for all the files, but I couldn't change
 - the files that Jonathan owns. It would probably be good if
 - either Jonathan or Damien changed the permissions to 664
 - so anyone in the group can delete or update the files.

Done.

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"

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

Date: Mon, 15 May 2000 20:51:28 -0500
From: "Jonathan Osuch" <[e-mail]>
Subject: Re: (fractint) 3d transform doesn't work in float only version

Tim wrote,

> As part of his project, Jonathan merged the float-only version with
> Xfractint, but didn't save the result of this before he started merging
> in Rich's changes. I'll probably reconstruct this. Our "official"
> Xfractint might as well be based on the float-only version since
> Xfractint doesn't support integer math anyway.

I could probably do that tomorrow.  One problem is that we won't be able to
make a diff to it.  I've removed 7 or 8 files that had no use in Xfractint.
Until we get ported back to Windows/DOS, this leaves us with two radically
different sets of source code.  But, you knew that.   8-))

I've finished incorporating Rich's modifications and although it compiles,
it doesn't exactly run.  I get a graphics window but no image.  All text,
when it can be made to appear, is not formatted.  I will try to get the
Allegro package tied in and then worry about getting it to run.  I'm afraid
I might be missing the big picture about how this is supposed to work.
Rich, can you add some insight?

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"

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

Date: Tue, 16 May 2000 10:29:51 -0600
From: Phil McRevis <[e-mail]>
Subject: Re: (fractint) 3d transform doesn't work in float only version

In article <001301bfbed9$567a4ea0$0100a8c0@bananasenior>,
    "Jonathan Osuch" <[e-mail]>  writes:

> I've finished incorporating Rich's modifications and although it compiles,
> it doesn't exactly run.  I get a graphics window but no image.

The code base I had drew graphics but no text.  This was because the
text was previously done through curses, which is definately the wrong
way to do it.  Text should be done through Xlib or something else
layered on Xlib, not hacked up through curses in an xterm window.

> I'm afraid
> I might be missing the big picture about how this is supposed to work.
> Rich, can you add some insight?

Its just an interface for abstracting the graphics and text output
with a current "driver" selected.  A driver is essentially a structure
of function pointers that perform the operations in the interface.  A
new interface was not designed, rather the existing output functions
were made part of the driver interface.  So instead of calling
DoSomething(), you call driver->DoSomething() where the driver pointer
is initialized to the appropriate structure when you select a video
mode, etc.

The initialization code picks an initial driver depending on your
operating environment (i.e. an Xlib driver if you're running under
unix, a Win32 driver if you're running under Windows, etc.).

The "select video mode" code obviously has to be rewritten to
incorporate this idea.
- --
<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"

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

Date: Thu, 25 May 2000 20:08:10 -0500
From: "Jonathan Osuch" <[e-mail]>
Subject: Allegro package Xfractint

Folks,

I have incorporated the Allegro package into a float only version of Rich's
"driver" source.  It's up and running.  I have graphics and text in the same
window, but no mouse or text cursor movement.  Since just about everything
is broken, I won't provide a to-do list.  8-))

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"

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

Date: Fri, 26 May 2000 10:19:16 -0600
From: Phil McRevis <[e-mail]>
Subject: Re: Allegro package Xfractint

In article <000f01bfc6af$20be92c0$0100a8c0@bananasenior>,
    "Jonathan Osuch" <[e-mail]>  writes:

> It's up and running.

Cool!

> I have graphics and text in the same
> window, but no mouse or text cursor movement.

If you have the energy for it, we should revamp the input towards an
event-based system.  For DOS you can always invent your own "message
pump".  (Can't you get DOS to invoke an interrupt routine when a key
is pressed or mouse is moved that queues the input data for later
processing?  I never really programmed in DOS.)  This would make the
porting to window systems much, much easier.  Currently xfractint
hacks this in by having the polling I/O routines examine the event
queue.  Fractint polls often enough that events don't lag too far
behind, but its really awkward.

Surprisingly this polling only happens in a handful of places around
the fractint source because things are fairly well abstracted, i.e.
there is a routine for presenting the text-based "dialogs" that
fractint uses for parameters and so-on and this is pretty much reused
everwhere that such a thing is needed, so its not like you have to
modify one routine for each dialog to make the dialogs event-based.
- --
<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"

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

Date: Fri, 26 May 2000 20:26:49 -0500
From: "Jonathan Osuch" <[e-mail]>
Subject: Re: Allegro package Xfractint

Rich,

> If you have the energy for it, we should revamp the input towards an
> event-based system.  For DOS you can always invent your own "message
> pump".  (Can't you get DOS to invoke an interrupt routine when a key
 > is pressed or mouse is moved that queues the input data for later
> processing?  I never really programmed in DOS.)

The Allegro package has a djgpp implementation.  So, in theory, it should be
set up for DOS once we get the Unix version running.  Can you give me a
brief explanation on how to implement an event-based system?  With so much
of the code currently broken, now would be a great time to make that change.

As for the energy, I've been doing this at work, since I currently don't
have anything else to do.  That is supposed to change next Tuesday.  I hope
it does, I don't really want to get laid off at this point in time.

Something I haven't started on, but have been thinking about is that the
Allegro package has routines for making menu's.  This would provide a
slicker package, but I'm not sure how easy that would be while maintaining
the "driver" interface.  OTOH, since the interface is not really defined
yet, we can change it to make it 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"

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

Date: Sat, 27 May 2000 17:39:10 -0600
From: Phil McRevis <[e-mail]>
Subject: Re: Allegro package Xfractint

In article <000a01bfc77a$acc6a3e0$0100a8c0@bananasenior>,
    "Jonathan Osuch" <[e-mail]>  writes:

> The Allegro package has a djgpp implementation.  So, in theory, it should be
> set up for DOS once we get the Unix version running.  Can you give me a
> brief explanation on how to implement an event-based system?

If you are doing input in a polling style you find a convenient place
to periodically check for keyboard input and then abort your current
computation to go handle the keyboard input.  So you have code that is
roughly structured like this:

    done = false;
    while (!done) {
    do_something();
    key = getakey();
    if (key == ESC)
        break;
    do_something_else();
    if (finished())
        done = true;
    }
    if (!done) // ESC broke us out
    handle_esc();
    else
    final_stuff();

and so-on.  Basically the getakey() polls the input buffer to check to
see if there is anything.  If so, then the input is handled somehow.
Some places in fractint handle keys immediately and then continue with
the work, whereas others (like pressing ESC) cause the control flow to
be altered by aborting the current calculation, or going into a menu
display or something.

Basically the fictitious routines do_something(), do_something_else(),
finished() and final_stuff() I've written above are the "idle" loop
that is executed when you don't have any input waiting for you to
handle.  It is essentially a state machine (starts with done=false and
proceeds doing incremental batches of work until done=true) that is
interleaved with checking for input whenever a state transition could
be made.

The event-loop style of handling this is to separate the idle
processing state machine from the input handling like so:

    quit = false;
    while (!quit) {
    if (peek_event()) {
        event = get_event();
        handle_event(event);
    } else {
        do_idle_routine();
    }
    }

where the routines peek_event(), get_event(), and handle_event() do
the input processing.  When no events are available for processing,
the code executes the idle input state machine code.  Obviously the
routine do_idle_processing() shouldn't take a long time because the
program isn't going to respond to input while doing the idle
processing.  However, fractint is already structured this way because
of the frequent calls to getakey() which aborts or suspends any idle
processing based on the key pressed.

Eventually some piece of input (or completion of the idle processing
in batch mode) will signal that quit should be set to true, thus
causing the program to terminate.  The above is the structure of every
Win32 application, as well as every X Window System application.  They
process events until the program receives an event (or a condition is
triggered) that causes the program to terminate.

I certainly hope you don't get laid off!  I don't know if you're
willing to relocate, but if you know Windows programming (especially
COM), there are two full-time positions open where I work in Salt Lake
City.  Give me a hollar if you are interested in exploring that
possibility.

As for the allegro menu system, right now I would concentrate on just
getting a bare-bones interface to work using whatever is most
convenient.  For the "big picture", the differences between
Mac/Win32/X are small enough that the driver interface should be able
to handle them all.  We can always get fancier with the interface
later after we get something basic working, even if the basics are
initially ugly.
- --
<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"

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

Date: Tue, 30 May 2000 01:20:42 -0500
From: "Scott D. Boyd" <[e-mail]>
Subject: Xfractint dev. question

Hi all,

I know it's not in the source, but is fractint.cfg used for *any reason* by
Xfractint? Or is it a moot point (or moot file) since X takes care of the
graphics window?

Scott Boyd

- --
email:  [e-mail]
http://www.fastlane.net/~sdboyd/
"Make it idiot-proof, and someone will make a better idiot."


- --------------------------------------------------------------
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"

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

Date: Tue, 30 May 2000 19:56:13 -0500
From: "Jonathan Osuch" <[e-mail]>
Subject: Re: Xfractint dev. question

Scott,

> I know it's not in the source, but is fractint.cfg used for *any reason*
by
> Xfractint? Or is it a moot point (or moot file) since X takes care of the
> graphics window?

It is not used for anything and is one of many files that will be
disappearing.  There is a lot of legacy code that will need to be removed
once the integration of the Allegro graphics package is complete.

The status of the Allegro integration:  Basic graphics and text windows
work.  No zooming or text cursor.  The help screens and certain other text
screens crash.  The 8, 15, 16, 24, and 32 bpp graphics modes work.  There is
still lots to do.

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"

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

Date: Fri, 2 Jun 2000 22:40:18 -0500
From: "Scott D. Boyd" <[e-mail]>
Subject: Bug fix in Xfractint 20.0.11

I have found the bug that kept '#' and 'F3' from selecting 3D Overlay while
at the Main Menu in Xfractint. I removed lines 1294 - 1295 in unixscr.c.

This bug was present in both versions 20.0.7 and 20.0.11. '#' didn't work in
either xterm or KDE's konsole, and F3 didn't work in KDE's konsole. Now I have
'#' working from both xterm and konsole.

This fix has been tested and known to work in Xfractint 20.0.11 running in
xterm and KDE's konsole. (Well, that partly fixes the problem. At least the
key indicated in the Main Menu now works! So I guess you could call it a "quick
fix".)


- --
email:  [e-mail]
http://www.fastlane.net/~sdboyd/
"Make it idiot-proof, and someone will make a better idiot."


- --------------------------------------------------------------
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"

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

End of fractdev-digest V1 #31
*****************************