Hi Guys, I've seen a lot of valuable discussion and think that ther most valuable way forward is to keep as much of the system independent code as 'standard C' like a jpeg or png library. Then each of us can add GUI, screen and i/o independantly. The think that makes this difficult is the monmolithic modules and the over use of globals (needed in early versions for speed). In ManpWIN, I have tried to separate out the modules such as guess(), boundary() etc to simplify the process. I still believe that converting all of fractint is an arduous task and have chosen to do a fractint shell and add the WINDOWS specific stuff to that. The main contribution I can make is WINDOWS 32 bit, true colour palette design and true colour processing. Is there a way we can 'simply' generate a 'standard c' library for the platform independant components with a mnimal use of globals? This would help us all. ---------------------------------------------------------- Paul de Leeuw Computers Central Coast Australia Email: pdeleeuw@deleeuw.com.au www: <http://www.deleeuw.com.au> ABN 72 360 822 562 ---------------------------------------------------------- -----Original Message----- From: fractdev-bounces@mailman.xmission.com [mailto:fractdev-bounces@mailman.xmission.com]On Behalf Of Rich Sent: Wednesday, 12 November 2003 4:07 AM To: Fractint developer's list Subject: Re: [Fractdev] Re: WinFract, parallel development, etc
It seems that every few months someone proposes this grand re-organization of the fractint source code. It sounds great until they actually get into the code and then the sheer size of the task generally has them leaving without further comment.