Hi Team,
Just a progress report on the weekend WINFRACT 32bit/true colour
activities. All .c files including the 24 bit and WINFRACT files can
now be compiled with no errors or serious warnings. I only have 512
undefined modules / variables at link time. Hopefully I can fix most of
these in a week or so. Then comes the hard part, checking all the
functionality. Especially the difference between the WINFRACT GUI from
18.21 and that of 2FRACTINT v20.2.4.
Regards,
Paul.
----------------------------------------------------------
Paul de Leeuw Computers Central Coast Australia
Email: pdeleeuw(a)deleeuw.com.au
www: <http://www.deleeuw.com.au>
ABN 72 360 822 562
----------------------------------------------------------
----- Original Message -----
>From pdeleeuw <pdeleeuw(a)bigpond.com>
Date Tue, 09 Apr 2002 08:50:51 +1000
To fractdev(a)mailman.xmission.com
Subject Re: [Fractdev] Allegro port
Hi Tim,
We are getting close.
> One trick is to do what both Winfract and Xfractint
> did, and write windows versions of the screen writing and reading
> routines.
These routines already exist in MANPWin and just need a cleanup. I
think that using the #ifdef WIN32 we can fix most problems in the
header files. I have again attached the latest build report from
MSVC++v4 after defining XFRACT and modifyng 2 header files (also in
attached zip file).
> My original idea was to create a fRAc chunk that had subchunks for
> each data item. The iteration count could be in it's own chunk,
> or we could add some other similar items. In order to work on this we
> need to get PNG working in all the versions. This means getting
> out from under the DOS version which can never have PNG, as near as I
> can tell, due to memory limitations. I'll start looking into this.
I don't like the additional chunk as the PNG files size will be huge,
even if compressed. Another view is to use my algorithm for generating
true colour palettes and to surch for and remove duplicates and only
save the lookup table. We need only thensave a WORD or DWORD per max
iteration. This can be a processing overload for smaller machines.
Comments?
Regards,
Paul de.
----------------------------------------------------------
Paul de Leeuw Computers Central Coast Australia
Email: pdeleeuw(a)deleeuw.com.au
www: <http://www.deleeuw.com.au>
ABN 72 360 822 562
----------------------------------------------------------
Hi Jonathan,
Thanks for the non ASM port. Please supply the URL for the ftp site. I
have learned a lot over the last couple of days and will hit this hard
over the next few weeks to get a 32 bit true colour WINFRACT up and
running. Initially it will be a rebuild of WINFRACT 18.21 GUI with the
32 bit XFRACT source and the colour routines from MANPWIN. From there
we should be able to progress rather quickly (famous last words).
Regards,
PHD.
----------------------------------------------------------
Paul de Leeuw Computers Central Coast Australia
Email: pdeleeuw(a)deleeuw.com.au
www: <http://www.deleeuw.com.au>
ABN 72 360 822 562
----------------------------------------------------------
----- Original Message -----
From: Jonathan Osuch <osuchj(a)avalon.net>
Date: Tuesday, April 9, 2002 11:50 am
Subject: [Fractdev] Xfractint version 20.2 patch 4
> The diff and the Xfractint source for 20.2 patch 4 are now on the
> ftp site.
> All this patch does is address PHD's assembly language problem.
>
> Jonathan
>
> _______________________________________________
> Fractdev mailing list
> Fractdev(a)mailman.xmission.com
> http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractdev
>
Hi Tim,
We are getting close.
> One trick is to do what both Winfract and Xfractint
> did, and write windows versions of the screen writing and reading
> routines.
These routines already exist in MANPWin and just need a cleanup. I
think that using the #ifdef WIN32 we can fix most problems in the
header files. I have again attached the latest build report from
MSVC++v4 after defining XFRACT and modifyng 2 header files (also in
attached zip file).
> My original idea was to create a fRAc chunk that had subchunks for
> each data item. The iteration count could be in it's own chunk,
> or we could add some other similar items. In order to work on this we
> need to get PNG working in all the versions. This means getting
> out from under the DOS version which can never have PNG, as near as I
> can tell, due to memory limitations. I'll start looking into this.
I don't like the additional chunk as the PNG files size will be huge,
even if compressed. Another view is to use my algorithm for generating
true colour palettes and to surch for and remove duplicates and only
save the lookup table. We need only thensave a WORD or DWORD per max
iteration. This can be a processing overload for smaller machines.
Comments?
Regards,
Paul de.
----------------------------------------------------------
Paul de Leeuw Computers Central Coast Australia
Email: pdeleeuw(a)deleeuw.com.au
www: <http://www.deleeuw.com.au>
ABN 72 360 822 562
----------------------------------------------------------
Bum,
I forgot the attachment!!!
I also need to mention that MSVC++v4 doesn't have a copy of NASM and I
don't know how to compile ASM code.
Regards,
Paul de.
----------------------------------------------------------
Paul de Leeuw Computers Central Coast Australia
Email: pdeleeuw(a)deleeuw.com.au
www: <http://www.deleeuw.com.au>
ABN 72 360 822 562
----------------------------------------------------------
Tim,
The Allegro port is now up to the current patch level and uploaded to the
experimental ftp directory. I'll work at getting the X11 portion working.
Jonathan
Hi Tim,
> Question: I haven't looked closely, so you may already have done
> this, but do you have a way to compile our current Xfractint
> without
> using the asm code? I am really excited about your success with
> NASM.
> Problem is, we need to make a way to avoid using any assembly
> language for portability. If you haven't done this, I can look
> into.
> At this early stage it shouldn't be hard. We need to maintain the
> C
> equivalent to the ASM and have a way to compile the code either way.
I have been dogged by asm code myself and has slowed down my progress
for a 32 bit WINFRACT. Once we get the #defines and the header files
working, a couple of months and we will have 32 bit windows true colour
FRACTINT. The only other issue is the iteration -> RGB and back
translation for storing pixel data and iteration count in the PNG files.
Any ideas???
Regards,
Paul de.
----------------------------------------------------------
Paul de Leeuw Computers Central Coast Australia
Email: pdeleeuw(a)deleeuw.com.au
www: <http://www.deleeuw.com.au>
ABN 72 360 822 562
----------------------------------------------------------
Hi Guys,
My initials are PHD if you want to use that or Paul de is OK as well.
Regards,
Paul de.
----------------------------------------------------------
Paul de Leeuw Computers Central Coast Australia
Email: pdeleeuw(a)deleeuw.com.au
www: <http://www.deleeuw.com.au>
ABN 72 360 822 562
----------------------------------------------------------
----- Original Message -----
From: "Paul N. Lee" <Paul.N.Lee(a)Worldnet.att.net>
Date: Monday, April 8, 2002 7:44 pm
Subject: Re: [Fractdev] Allegro port
> Tim Wegner wrote:
> >
> > Paul D. (since Paul N.Lee. is active here,
> > we better avoid plain old "Paul" :-) )
>
> Using "PNL" is fine with me, and easy to type. :-)
>
> Later,
> P.N.L.
> --------------------------------------------------------------
> http://www.fractalus.com/cgi-bin/theway?ring=fractals&id=43&go
>
> _______________________________________________
> Fractdev mailing list
> Fractdev(a)mailman.xmission.com
> http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractdev
>
Hello.
Who knows how the FractNT project is getting on? I remember seeing the page
(http://athena.atr.net/) ages ago, but as yet there doesn't appear to have
been a release.
From,
Rupert
We have several Paul's here, but I'll refer to Paul DeLeeuw as Paul
until such a time as one of other Pauls enters into the conversation,
at which point we may have to resort to another naming convention
(apologies to Paul N. Lee) :-)
I have uploaded the file compiler error file Paul sent me here:
http://www.fractint.org/ftp/experimental/XFract_Errors_5April2002.zip
Paul, you can upload files yourself since Damien has created an
account for you. If you need help, email me privately.
Right off the bat, you need to follow Jonathan's advice and define
XFRACT. That will immediately clear up all the near, far, and segname
stuff. Of course you will still get some errors, because anything to
do with Xwindows won't be appropriate, but you will be way ahead of
the game.
Tim
