Tim, I've never seen the Winfract source code. Was it going to be on your archive CD? Jonathan
Jonathan Osuch wrote:
I've never seen the Winfract source code. Was it going to be on your archive CD?
Speaking of archives... I have the following versions of FractInt and am looking for all the ones not listed here: Fract386 2.10 Fract386 4.00 Fract386 5.10 FractInt 7.00 FractInt 8.10 FractInt 11.00 FractInt 12.00 FractInt 14.00 FractInt 15.10 FractInt 16.00 FractInt 16.11 FractInt 17.01 FractInt 17.10 FractInt 17.20 FractInt 18.00 FractInt 18.10 FractInt 18.20 FractInt 18.21 FractInt 19.00 FractInt 19.10 FractInt 19.20 FractInt 19.30 FractInt 19.40 FractInt 19.50 FractInt 19.60 FractInt 20.00 (and others from here on up) Does anybody here have them?? And if so, what will it take to get them?? Also have the WinFract source and exectuables at: http://www.Nahee.com/Software/ Later, P.N.L. ------------------------------------------------- http://home.att.net/~Paul.N.Lee/PNL_Fractals.html http://www.Nahee.com/Fractals/
Paul wrote:
Speaking of archives... I have the following versions of FractInt and am looking for all the ones not listed here:
I probably have most if not all of those. I'll post a list this weekend. I'll figure out a way to make them available. I can probably put them online at fractint.org. Damien doesn't seem to be worried about our bandwidth, which is very small compared to the artists who have a lot of images downloaded. If you have some I don't you could help round out my collection. Tim
Hi Tim, I have most versions of WINFRACT source and can make v18.2 available. All I need is someone to send it to where I don't blow the 40KB limit. 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 ---------------------------------------------------------- -----Original Message----- From: fractdev-bounces@mailman.xmission.com [mailto:fractdev-bounces@mailman.xmission.com]On Behalf Of Tim Wegner Sent: Tuesday, 21 October 2003 3:53 PM To: Fractint developer's list Subject: Re: [Fractdev] Winfract source
I've never seen the Winfract source code. Was it going to be on your archive CD?
I'm, sure I have it. Will check on the weekend. Tim _______________________________________________ Fractdev mailing list Fractdev@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractdev
I had a copy once upon a time, several computers ago. I still may have it in archive. I will check for it thi week. Ron Barnett -----Original Message----- From: fractdev-bounces@mailman.xmission.com [mailto:fractdev-bounces@mailman.xmission.com] On Behalf Of Tim Wegner Sent: Tuesday, October 21, 2003 12:53 AM To: Fractint developer's list Subject: Re: [Fractdev] Winfract source
I've never seen the Winfract source code. Was it going to be on your archive CD?
I'm, sure I have it. Will check on the weekend. Tim _______________________________________________ Fractdev mailing list Fractdev@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractdev
hi all. i'd like to discuss a way of shaping up an image: flooding it is done by iterating all the pixels consequently, coloring those that bailed out, but still precising what was left black.. (stripe after stripe appears: blue, green, cyan, red..) so there is no need for an iteration limit - infinity is ok, even without periodicity checking.. (but periodicity logic would speed it up, of course) it also may start after the guessing was completed, just checking whether the inside is really inside, up to a high maxiter or infinity.. you can see an example attached to this mail: faketint.jar (run something like: java -jar faketint.jar) (it's just fast built, slow acting, and i'm very new to java) it will probably need a lot of memory, so maybe there is no chance to fit that to the dos version of fractint.. but anyway, what do you think about it, is it worth of thinking about? charlie ____________________________________________________________ Nechybí Vám něco proti hackerům a virům? http://ad2.seznam.cz/redir.cgi?instance=63339%26url=http://www.contactel.cz/...
hi again. why not java as a future for fractint? it would be portable. there would be no gui problem. (speed? native executables.) did you talk about this already? something i missed? maybe there's a reason i can't see which makes the code not rewritable in java.. is there any? charlie /* tim, i still owe you that relaxed zoombox scrolling.. i didn't forget nor i gave up: got a little wolfdog puppy so i've been distracted for a few months growing it up.. now i'm quite back and will post that soon.. */ ____________________________________________________________ Řekněte sýr! MMS telefon SonyEricsson T610 s foťákem můžete mít už za 5577 Kč. A k tomu až 120 MMS zdarma! http://ad2.seznam.cz/redir.cgi?instance=62754%26url=http://www.oskarmobil.cz...
Jonathan asked:
I've never seen the Winfract source code. Was it going to be on your archive CD?
Spanky has it, at: http://spanky.triumf.ca/pub/fractals/programs/ibmpc/windows/wins1821.z ip However your question was a reminder to look at what I have, so I'll still do that this weekend. Tim
Tim,
Spanky has it, at:
http://spanky.triumf.ca/pub/fractals/programs/ibmpc/windows/wins1821.z ip
However your question was a reminder to look at what I have, so I'll still do that this weekend.
That's a good indication of why I haven't done any programming lately. Can I assume that rc is a revision control program, and I can fix up the winfract make file to not use it? Jonathan
Jonathan Osuch wrote:
Can I assume that rc is a revision control program, and I can fix up the winfract make file to not use it?
Under Visual C++, a file type with the extension of RC usually means it is a resource script file. A text file containing descriptions of resources from which the resource compiler creates a binary resource file. For Microsoft Windows applications, resource-definition files usually have a .RC filename extension. For Apple Macintosh applications, such files are typically named with a .R extension and written with the Apple Rez script language. Sincerely, P.N.L. ------------------------------------------------- http://home.att.net/~Paul.N.Lee/PNL_Fractals.html http://www.Nahee.com/Fractals/
On Friday 24 October 2003 01:13 am, Paul N. Lee wrote:
Under Visual C++, a file type with the extension of RC usually means it is a resource script file. A text file containing descriptions of resources from which the resource compiler creates a binary resource file. For Microsoft Windows applications, resource-definition files usually have a .RC filename extension. For Apple Macintosh applications, such files are typically named with a .R extension and written with the Apple Rez script language.
Okay, so what is the following (in the make file) doing for me? .rc.res: rc -r $*.rc winfract.hlp: winfract.rtf mathtool.rtf hc winfract winfract.res: winfract.rc mathtool.rc mathtool.h coord.dlg winfract.h \ dialog.h zoom.dlg rc -r winfract.rc Jonathan
On Friday 24 October 2003 07:40 pm, Tim Wegner wrote:
I can't answer, but I can say that the very same Microsoft compiler that we both use can compile winfract if the Windows SDK is installed. I have the Win sdk, though I have never used it.
I don't have the Windows SDK installed, and the disks are in Iowa. Jonathan
In article <200310241814.47542.osuchj@avalon.net>, Jonathan Osuch <osuchj@avalon.net> writes:
Okay, so what is the following (in the make file) doing for me?
rc.res: rc -r $*.rc
winfract.res: winfract.rc mathtool.rc mathtool.h coord.dlg winfract.h \ dialog.h zoom.dlg rc -r winfract.rc
rc is the resource compiler. A .rc file is a text file containing a resource script that defines Win32 resources. Visual Studio 6/7 contains a resource editor that lets you edit resources through a GUI. In Win32, 'resources' are stored in the executable file when your exe is linked. The idea of a resource file is to be able to edit the UI elements of your application, or localized elements of your application, without having to modify the code. (There are resource editors that work directly on the resources embedded in a binary, for instance.) Suppose you have an application that is localized into English, French and German. You can put a string table in the resource file that will hold the localized strings used in UI elements -- dialog box titles, button text, combo box labels, and so-on. You can refer to elements in the string table with a string name or integer ID in your code to obtain the necessary strings. If you put them in resources, then a translation company can translate your resources and your code will then be localized into the translated language. Other things commonly in resources are dialog box layouts (including child controls), version resources (what's shown for the EXE version tab in Windows Explorer), hotkey resources, cursors, bitmaps, and custom resource data. See <http://tinyurl.com/s9zo> for the MSDN documentation on resources.
winfract.hlp: winfract.rtf mathtool.rtf hc winfract
hc is the help compiler. It takes source files and a project file and builds a winhelp .hlp file. This is the 'old' style of help file that's been in windows forever. Nowadays, MS prefers people to make HTML help files (.chm) instead. The resource compiler is in the 'Platform SDK' -- I think this is what Tim referred to as the Windows SDK, but they call it the Platform SDK now. The Platform SDK is a free download and contains headers, libraries and ancilliary tools for Windows development. Generally, even if you have Visual Studio, you occasionally install the Platform SDK if you want to access features in Windows that are newer than your release of Visual Studio. This is similar to how you should install the DirectX SDK to get the right libraries and headers instead of relying on what shipped with your copy of Visual Studio. The help compiler is in the Help Workshop also freely available from MS. See <http://tinyurl.com/sa13>. The resource compiler is included in Visual Studio. I believe the help compiler is also included somewhere on the Visual Studio distribution media, but its a separate install and not installed with studio by default. -- "The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ: <http://www.xmission.com/~legalize/book/> Pilgrimage: Utah's annual demoparty <http://pilgrimage.scene.org>
On Friday 24 October 2003 08:00 pm, Rich wrote:
rc is the resource compiler. A .rc file is a text file containing a resource script that defines Win32 resources. Visual Studio 6/7 contains a resource editor that lets you edit resources through a GUI.
The resource compiler is in the 'Platform SDK' -- I think this is what Tim referred to as the Windows SDK, but they call it the Platform SDK now. The Platform SDK is a free download and contains headers, libraries and ancilliary tools for Windows development. Generally, even if you have Visual Studio, you occasionally install the Platform SDK if you want to access features in Windows that are newer than your release of Visual Studio. This is similar to how you should install the DirectX SDK to get the right libraries and headers instead of relying on what shipped with your copy of Visual Studio.
Thanks Rich. I found what I needed. Now I need to clean enough files off my hard drive to load it. Jonathan
Jonathan Osuch wrote:
Okay, so what is the following (in the make file) doing for me?
.rc.res: rc -r $*.rc
Compiling resource files using the Win32 SDK requires three separate tools: the first tool you use is the RC compiler, which turns your .RC file into a .RES file; you then use the CVTRES tool to convert the .RES file into an object file; and finally, you link the object file to the program executable using LINK32. The normal syntax is as follows: RC [options] _script-file_ The _script-file_ parameter specifies the name of the resource-definition file that contains the names, types, filenames, and descriptions of the resources to be compiled. The 'options' parameter can be one or more of the command-line options, such as: /? -- Displays a list of RC command-line options. /d -- Defines a symbol for the preprocessor that you can test with the #ifdef directive. /r -- Ignored. Provided for compatibility with existing makefiles. Options are not case sensitive, and a hyphen (-) can be used in place of a slash mark (/). You can combine single-letter options if they do not require any additional parameters.
winfract.hlp: winfract.rtf mathtool.rtf hc winfract
Help Compiler using the input Rich Text Files. I personally prefer the older Windows Help (.HLP) files over the newer Compiled Help (.CHM) files. They seem to be faster when accessed and use less resources. And they do not require Internet Explorer. Sincerely, P.N.L. ------------------------------------------------- http://home.att.net/~Paul.N.Lee/PNL_Fractals.html http://www.Nahee.com/Fractals/
participants (7)
-
Charlie Chernohorsky -
Jonathan Osuch -
Paul -
Paul N. Lee -
Rich -
Ron Barnett -
Tim Wegner