Re: [Fractdev] Fractint and Win XP
Hi Guys,
I have an old Microsoft Visual C/C++ compiler (version 4.0 or 5.0) so I could follow along. But I'm not personally interested in learning Windows programming.
Leave the windows coding to me. All I want is to be able to get the FRACTINT source code to compile into 32 bit object modules which I can link into the appropriate WIN32 shell. I can base much of the user interface on WINFRACT. Thanks for your interest guys. Regards, Paul. ---------------------------------------------------------- Paul de Leeuw Computers Central Coast Australia Email: pdeleeuw@deleeuw.com.au www: <http://www.deleeuw.com.au> ABN 72 360 822 562 ----------------------------------------------------------
(Note: Paul's posts were delayed because I had to approve them manually - we'll get this straightened out, but until we do, Paul's posts may not show up right away.) Paul wrote:
Leave the windows coding to me. All I want is to be able to get the FRACTINT source code to compile into 32 bit object modules which I can link into the appropriate WIN32 shell. I can base much of the user interface on WINFRACT.
Consider that Xfractint already uses a 32 bit compiler, and shares source with fractint via defines. So basically you have to create a new define for your version, and search for every instance of the XFRACT define. In most cases you can use the same logic that XFRACT uses. Next, you will have to look at the Xfract-only code. Some of this you can use as-is, but obviously code that interfaces with Xwindows will have to be different. The rules of the game are to NOT disturb the ability of the shared code to be compiled with the old medium model compiler or the ability of the XFRACT version to compiler. The reason for this is that if the code forks, suddenly we have multiple versions of forked code to maintain, and we don't have the people. On the other hand, if multiple versions share code, they can be maintained forever. Ken Shirriff disappeared many years ago, but we have been able to maintain his code because he took this approach. Tim
participants (2)
-
pdeleeuw -
Tim Wegner