Paul de Leeuw has been working for some time on a Windows API port of Fractint. At his request I have put the program and the source in http://www.fractint.org/ftp/experimental/MANPWIN.zip and http://www.fractint.org/ftp/experimental/ManpWinSrc.zip His version supports truecolor and can due color cycling. He'd love to have some help. I'm itching to get back into Fractint myself but haven't decided where to dive in yet. I have a full life, so until I actually do this it's just an idea :-) Paul, since your source, though based on Fractint, is yours, maybe the first thing to do is to put the code under an open source license. I'd suggest GPL (but this would be up to you). In fact maybe what I ought to take on is the mundane task of GPL'ing fractint. This would mean going through the code module by module, and changing the license of the files we have copyright to, and gaining permission or rewriting or removing the rest. Tim
On Tuesday 26 February 2002 19:45, Tim wrote:
I'm itching to get back into Fractint myself but haven't decided where to dive in yet. I have a full life, so until I actually do this it's just an idea :-)
In fact maybe what I ought to take on is the mundane task of GPL'ing fractint. This would mean going through the code module by module, and changing the license of the files we have copyright to, and gaining permission or rewriting or removing the rest.
That would be time consuming, but it needs to be done. Take a look at the video.c source in version 20.2.03 of Xfractint. It has been run through indent. Updating the float only sources is going to be a killer for this patch. That could take a week or two. Jonathan
Updating the float only sources is going to be a killer for this patch. That could take a week or two.
I have a modest proposal. Why not make the float only sources the main sources? I actually thought we would do that a long time ago. I don't think the integer math has any future, and every minute you spend on maintaining both versions, is a minute you are not spending bringing the assembler speedups to the 32 bit versions, which is the main obstacle to leaving the medium memory model behind. It's just a question of the best uses of a scarce commodity, developer time. But since you are doing the work, it's your call, not mine. :-) Tim
On Tuesday 26 February 2002 21:27, Tim wrote:
I have a modest proposal. Why not make the float only sources the main sources? I actually thought we would do that a long time ago. I don't think the integer math has any future, and every minute you spend on maintaining both versions, is a minute you are not spending bringing the assembler speedups to the 32 bit versions, which is the main obstacle to leaving the medium memory model behind.
It's just a question of the best uses of a scarce commodity, developer time.
But since you are doing the work, it's your call, not mine. :-)
Then what of Xfractint? It is based on the integer/float version of Fractint. I do have a float only version, but it has been mangled by attempting to get the Allegro graphics package to work. The X-Window interface is still broken in it as well. And, even with that, the code is still vastly different from the float-only version. I do have the Xfractint float-only base source files that I started from, but they are at version 20.0 patch 11. My intention was to get the Allegro version (float-only) of Xfractint working, then port it to djgpp to get back to the DOS/Windows environment. Jonathan Why didn't they call it PaneLess instead of Lindows? Then it could have been interpreted as Painless or Payin' less.
Jonathan asked:
Then what of Xfractint? It is based on the integer/float version of Fractint.
Of course Xfractint, which already doesn't use integer math, should be integrated with the float only version, but only when we are ready to declare the float-only version the main (or only) version.
I do have a float only version, but it has been mangled by attempting to get the Allegro graphics package to work. The X-Window interface is still broken in it as well. And, even with that, the code is still vastly different from the float-only version. I do have the Xfractint float-only base source files that I started from, but they are at version 20.0 patch 11.
My intention was to get the Allegro version (float-only) of Xfractint working, then port it to djgpp to get back to the DOS/Windows environment.
You need to decide if you want to resurrect the Allegro version or in some other way preserve that work. How about you merge your latest patch with the float-only version as you have planned, then I merge the float only version with Xfractint (I don't think this will be hard), and then we stop work on the integer versions, or at least make the "official" versions the float only versions. If anyone wants to continue to backport the further development to the integer version, they are welcome, but we would declare the main tree to be the float-only version. If you agree with that plan, then you would need to decide what to do with your allegro version. I never quite got that development environment to work, thouigh I can't say I tried too hard. I think the only way to keep the allegro work alive (for the time being) would be to get those changes merged with in the same way the Xfractint/Fractint versions are merged, by sharing the same source files. Once that merging was done, with the integer version behind us, we could go forward with a single set of patches. At some point we might actually using CVS :-) Tim
In article <3C7D5253.28860.503FCF@localhost>, Tim Wegner <twegner@swbell.net> writes:
At some point we might actually using CVS :-)
The sooner the better, IMO. The more the code diverges, the harder it will be to merge the longer you stay out of CVS. -- Ask me about my upcoming book on Direct3D from Addison-Wesley! Direct3D Book <http://www.xmission.com/~legalize/book/> Don't Support Spammers! Boycott Fractal Painter 7! <http://www.xmission.com/~legalize/spammers.html>
Rich wrote:
The sooner the better, IMO. The more the code diverges, the harder it will be to merge the longer you stay out of CVS.
Actually, we are talking about unifying the sources the way Fractint and xfractint are unified. They share identical files. But I am not iooposed to using CVS, it's just another thing to learn, and both Jonathan and I have gotten very good at using diff and patch. Manpwin, on the other hand, is a significant fork. I doubt it can be m aintained together with fractint/xfractint, but at some point changes can be merged in either direction. I am interested in what Paul has done with True Color. Tim
In article <3C7E7BB2.22420.7BD0D2@localhost>, Tim Wegner <twegner@swbell.net> writes:
and xfractint are unified. They share identical files. But I am not iooposed to using CVS, it's just another thing to learn, and both Jonathan and I have gotten very good at using diff and patch.
If you're proficient with diff and patch, then you already understand CVS. cvs diff -c produces a context diff that you could feed to patch. When you check in new revisions, a context diff is generated and appended to the version control file. When you do 'cvs update' after someone else has checked in a new version, it patches your local copy of the files.
Manpwin, on the other hand, is a significant fork. I doubt it can be m aintained together with fractint/xfractint, but at some point changes can be merged in either direction. I am interested in what Paul has done with True Color.
I imagine that there's still gobs of code that he hasn't changed. CVS can handle that fork as well. -- Ask me about my upcoming book on Direct3D from Addison-Wesley! Direct3D Book <http://www.xmission.com/~legalize/book/> Don't Support Spammers! Boycott Fractal Painter 7! <http://www.xmission.com/~legalize/spammers.html>
On Wednesday 27 February 2002 21:40, Tim wrote:
How about you merge your latest patch with the float-only version as you have planned, then I merge the float only version with Xfractint (I don't think this will be hard), and then we stop work on the integer versions, or at least make the "official" versions the float only versions. If anyone wants to continue to backport the further development to the integer version, they are welcome, but we would declare the main tree to be the float-only version.
I've already merged the float only version with Xfractint. It's at version 20.0 patch 11. There are some patches that will be difficult to incorporate, but bringing this source code up to the current version probably makes more sense than doing the work over again.
If you agree with that plan, then you would need to decide what to do with your allegro version. I never quite got that development environment to work, thouigh I can't say I tried too hard. I think the only way to keep the allegro work alive (for the time being) would be to get those changes merged with in the same way the Xfractint/Fractint versions are merged, by sharing the same source files. Once that merging was done, with the integer version behind us, we could go forward with a single set of patches.
Allegro is now at (or above) version 4.0, which came out late last year. The last time I updated their source code, the process went better than it had in the past. I haven't tried version 4 yet, although it is on my hard drive.
At some point we might actually using CVS :-)
Something else to learn. Yes, that would be good. I'd like to play with it from Iowa, but haven't gotten to it. Jonathan
Jonathan wrote:
I've already merged the float only version with Xfractint. It's at version 20.0 patch 11. There are some patches that will be difficult to incorporate, but bringing this source code up to the current version probably makes more sense than doing the work over again.
If you have a lot of versions of the float only version saved, including 20.0 patch 11, then making float-only diffs of the regular fractint float only version, and applying them to the float-only version of xfractint should be straight forward. If youi would like me to do this, let me know.
Allegro is now at (or above) version 4.0, which came out late last year. The last time I updated their source code, the process went better than it had in the past. I haven't tried version 4 yet, although it is on my hard drive.
Is the current Allegro Fractint the one on the web site? I'd like to try it.
At some point we might actually using CVS :-)
Something else to learn. Yes, that would be good. I'd like to play with it from Iowa, but haven't gotten to it.
When one is good at using diff and patch, it's hard to decide to use CVS. I'm in the same boat as you are. Tim
On Thursday 28 February 2002 18:49, Tim wrote:
Is the current Allegro Fractint the one on the web site? I'd like to try it.
I believe it is at version 20.2 patch 1. It looks like I put patch 2 into my source, but I haven't uploaded it. That was about the time I started playing with nasm. I've already updated the Fractint float-only files. It didn't take long, after all. Jonathan
On Thursday 28 February 2002 18:49, Tim wrote:
If you have a lot of versions of the float only version saved, including 20.0 patch 11, then making float-only diffs of the regular fractint float only version, and applying them to the float-only version of xfractint should be straight forward. If youi would like me to do this, let me know.
We have the Fractint float-only source files on the developer's web site starting with version 20.0 patch 9. Yes, I'd appreciate it if you could do this. I've put the float-only Xfractint in the fractint directory. One thing to remember is that some patches had Xfractint changes that won't be reflected in the Fractint float only source. Jonathan
Hi Tim, I don't know anything about licensing. I am just happy to progress the development of good fractal software. I feel that windows is the best way to go. Please assist in the GPL thing. Many thanks. Paul. ---------------------------------------------------------- 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: "Tim Wegner" <twegner@swbell.net> To: <fractdev@mailman.xmission.com> Sent: Wednesday, February 27, 2002 12:45 PM Subject: [Fractdev] manpwin
Paul de Leeuw has been working for some time on a Windows API port of Fractint. At his request I have put the program and the source in
http://www.fractint.org/ftp/experimental/MANPWIN.zip
and
http://www.fractint.org/ftp/experimental/ManpWinSrc.zip
His version supports truecolor and can due color cycling. He'd love to have some help.
I'm itching to get back into Fractint myself but haven't decided where to dive in yet. I have a full life, so until I actually do this it's just an idea :-)
Paul, since your source, though based on Fractint, is yours, maybe the first thing to do is to put the code under an open source license. I'd suggest GPL (but this would be up to you).
In fact maybe what I ought to take on is the mundane task of GPL'ing fractint. This would mean going through the code module by module, and changing the license of the files we have copyright to, and gaining permission or rewriting or removing the rest.
Tim
_______________________________________________ Fractdev mailing list Fractdev@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractdev
Hi Tim, I have been looking at FRACTINT vers 20.0.14 and it still has all my old details. The new ones are: Paul de Leeuw 16 Sunset Street Wyomimg NSW 2250 Australia Work +61-2-8293-3055 Home +61-2-4329-0870 Thanks, Paul.
Thanks! ----- Original Message ----- From: "Jonathan Osuch" <osuchj@avalon.net> To: <fractdev@mailman.xmission.com> Sent: Saturday, March 02, 2002 1:04 PM Subject: Re: [Fractdev] manpwin On Thursday 28 February 2002 05:29, Paul wrote:
I have been looking at FRACTINT vers 20.0.14 and it still has all my old details.
The new ones are: ...
Thanks. The changes will be in the next patch. Jonathan _______________________________________________ Fractdev mailing list Fractdev@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractdev
I got rsync working to update my local mirror from fractint.org. I had no idea rsync was so cool. All it needs is for rsync to exist on both ends and for a ssh server to exist on one end. Since we have ssh access to julia, and since rsync exists on julia, I can use rsync to update my mirror. I will update Xfractint float only to the latest version as I promised. I am making a quickie trip to Minnesota (Saturday through Monday) so I'll wave when I fly over Iowa. :-) I'll most likely finish this after the trip. I discovered what you probably already knew, that the termcap library has to be installed by hand on Mandrake 8.1 in order to compile Xfractint. It is supposedly obsolete, so we should figure out how to replace it with whatever is more current. I'll worry about that later. Tim
On Monday 04 March 2002 20:47, Tim wrote:
I will update Xfractint float only to the latest version as I promised. I am making a quickie trip to Minnesota (Saturday through Monday) so I'll wave when I fly over Iowa. :-) I'll most likely finish this after the trip.
You'll miss me. I'm in Illinois this next weekend. I'm trying to recover from having to change apartments. The one I was in was under enough water to make the carpet very squishy. Now I'm on the second floor.
I discovered what you probably already knew, that the termcap library has to be installed by hand on Mandrake 8.1 in order to compile Xfractint. It is supposedly obsolete, so we should figure out how to replace it with whatever is more current. I'll worry about that later.
I had noticed that with 8.0. I think I had to load the curses library also. Jonathan
On Monday 04 March 2002 20:47, Tim wrote:
I discovered what you probably already knew, that the termcap library has to be installed by hand on Mandrake 8.1 in order to compile Xfractint. It is supposedly obsolete, so we should figure out how to replace it with whatever is more current. I'll worry about that later.
Why are we including termcap? Xfractint appears to run fine without it. I couldn't find any instances of termcap.h, and running the source through gcc -Wall would have picked up any occurrences of missing header files. And, for that matter, what is m? Oh, never mind! That would be a math lib. Jonathan
participants (4)
-
Jonathan Osuch -
Paul de Leeuw -
Rich -
Tim Wegner