Well, I uploaded the install to
ftp://fcomm.sourceforge.net/pub/fcomm/aifcgp~1.zip (1.78 Mb)
It includes all files from the 0.361 download on the main page.
I also uploaded the ISX compile script (setup.iss, 20 Kb). In order to open the scipt, you need to download ISX at: http://www.wintax.nl/isx/1.3.18/Isxsetup.exe (1.1 Mb)
This is very close to the releasable install. I just need you guys to say which files are to be excluded (ie: there are some unused wav files and bmp files), and what to say in the license (or if its good as it is). maybe you want new images in the installer?
Please be carefull, and don't install without making a backup of your current fcclone directory, there is an error with the PNG graphic files. i have notified the author of Inno Setup to look into this (possible) bug. It is probably a problem with the compression method in Inno Setup. Maybe NilsArne could convert to GIF or JPG ?
Err... I have probably forgotten something... Well, go ahead, DWL :)
Aha, I do not know how to delete files in the /pub/fcomm directory (I didn't bother to check), so if anyone could delete all files but aifcgp~1.zip and setup.iss, that would be great (is the space limited?). Or should all files be kept?
When did you donwload the .png? I found a error in them myself just recently, but it is fixed by now.
Here is the log from the update...
revision 1.2
date: 2000/08/17 19:36:24; author: nilsarne; state: Exp; lines: +3 -1
changed to binaries
I'm going to check the install to see if you've got the borken pictures...
/Nils-Arne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hmm not much has changed since 0.361 so I don't think a release is necessary this weekend.
Can be left till midweek.
But each time the files in the release change the script will need to be updated.
It would be convenient if it was in CVS so that whoever is doing the release can update it.
How do we solve the problem of the user selecting which processor they have?
Simplest: Only distribute the i386 exes - will execute on everyones computer and the difference is small except at Maximum Speed. (I don't know what the exact difference is but especially for 586+ it should be faster.)
Even if it was easy to add a page where you could select the processor, a lot of users won't know which processor to choose. (Remember that as a tool to help people learn programming Fcomm should be accessible to computer novices.) Although someone who is determined can keep trying, a lot of people would be put off and there is the risk that an inappropriate exe might work a bit - so we get lots of spurious bug reports.
I spose ideally we would auto-detect the processor and give the user a suggestion (a suggestion because the auto-detect might not work on every processor!). Is it possible to run a program and get its result somehow in a script? Actually the program could display a message box "Processor is a Pentium II, choose the 686 install.".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can see the list of sound files actually required in sound.cpp
(in the source directory for the distributions - path will change in the future.)
This is a new file I don't know if it's actually included in the last distribution so here is the list:
static const char *Soundfiles[]=
{
"\\fcclone\\sounds\\Start.wav",
"\\fcclone\\sounds\\Applause2.wav",
"\\fcclone\\sounds\\Kick.wav",
"\\fcclone\\sounds\\Part.wav",
"\\fcclone\\sounds\\notify.wav",
"\\fcclone\\sounds\\Ban.wav",
"\\fcclone\\sounds\\ping.wav",
"\\fcclone\\sounds\\fail.wav",
"\\fcclone\\sounds\\fail.wav",
};
These can be renamed to something more sensible now :)
There will be more sounds in the future.
OT BTW The reason for the names is that they're sounds I used to use for my irc client :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, in the next install, I will narrow the wav files down to the ones in sound.cpp. Also, I didn't include any .flt files in the install, except rfcmine and jedi, because they are really not needed, are they?
And theres another thing, the manual resides both in \manual and \source\something, is this neccessary? I could just have the latex file in the source dir, and the rest in the manual folder.
Also, is the \ref directory needed? All the files in there are also in the main dir. Most of the files in \resources are not needed either, are they?
Did the install look good, did it work on your computer, does the license need any changes, etc... ?
oh dear, me bad. Can anyone think of a clearer explanation? oh should be "f8" "f9" not just "8" "9".
There could be a comment at the end - ported to 32bits and for GCC compiler.
We need a way for multiple people to work on the setup script. Vidar see if you can get CVS working
perhaps have a setup\windows\ subdirectory the commands are (once you've got cvs working)
cvs add setup
cd setup
cvs add windows
cd windows
cvs add script.iss //whatever the script file is called
Zipping hardly reduces the size so I don't think it's necessary.
Maybe every install should include docs (at least the manual) as long as they're fairly small?
We should have a fleets directory where all the fleets are stored which has a shortcut so its easy to find.
hmm the uninstaller deletes everthing even if one of the fc files changed that's bad. But it doesn't remove new files which is good hmm.
A problem with including the HTML manual is that the graphics files clutter up the directory.
Nils-Arne please make it so those are in a subdirectory.
I managed to download innosetup hmm I have Delphi I could mess around with it but doesn't seem necessary.
It can compile conveniently via the command line. I will still make a tar.gz download for people who
don't want/can't use the setup program.
oh BTW Java comments seem to be the same as C++.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, I uploaded the install to
ftp://fcomm.sourceforge.net/pub/fcomm/aifcgp~1.zip (1.78 Mb)
It includes all files from the 0.361 download on the main page.
I also uploaded the ISX compile script (setup.iss, 20 Kb). In order to open the scipt, you need to download ISX at:
http://www.wintax.nl/isx/1.3.18/Isxsetup.exe (1.1 Mb)
This is very close to the releasable install. I just need you guys to say which files are to be excluded (ie: there are some unused wav files and bmp files), and what to say in the license (or if its good as it is). maybe you want new images in the installer?
Please be carefull, and don't install without making a backup of your current fcclone directory, there is an error with the PNG graphic files. i have notified the author of Inno Setup to look into this (possible) bug. It is probably a problem with the compression method in Inno Setup. Maybe NilsArne could convert to GIF or JPG ?
Err... I have probably forgotten something... Well, go ahead, DWL :)
Aha, I do not know how to delete files in the /pub/fcomm directory (I didn't bother to check), so if anyone could delete all files but aifcgp~1.zip and setup.iss, that would be great (is the space limited?). Or should all files be kept?
Vidar Braut Haarr
AmigoSoft Productions
folk@popmail.com
When did you donwload the .png? I found a error in them myself just recently, but it is fixed by now.
Here is the log from the update...
revision 1.2
date: 2000/08/17 19:36:24; author: nilsarne; state: Exp; lines: +3 -1
changed to binaries
I'm going to check the install to see if you've got the borken pictures...
/Nils-Arne
I just checked the files. You got the old .png-files. They are, to say the least, corrupt...
New ones ought to be in the CVS.
/Nils-Arne
Thanks, I will probably upload a new install on tuesday.
Vidar Braut Haarr
AmigoSoft Productions
folk@popmail.com
hmm not much has changed since 0.361 so I don't think a release is necessary this weekend.
Can be left till midweek.
But each time the files in the release change the script will need to be updated.
It would be convenient if it was in CVS so that whoever is doing the release can update it.
How do we solve the problem of the user selecting which processor they have?
Simplest: Only distribute the i386 exes - will execute on everyones computer and the difference is small except at Maximum Speed. (I don't know what the exact difference is but especially for 586+ it should be faster.)
Even if it was easy to add a page where you could select the processor, a lot of users won't know which processor to choose. (Remember that as a tool to help people learn programming Fcomm should be accessible to computer novices.) Although someone who is determined can keep trying, a lot of people would be put off and there is the risk that an inappropriate exe might work a bit - so we get lots of spurious bug reports.
I spose ideally we would auto-detect the processor and give the user a suggestion (a suggestion because the auto-detect might not work on every processor!). Is it possible to run a program and get its result somehow in a script? Actually the program could display a message box "Processor is a Pentium II, choose the 686 install.".
You can see the list of sound files actually required in sound.cpp
(in the source directory for the distributions - path will change in the future.)
This is a new file I don't know if it's actually included in the last distribution so here is the list:
static const char *Soundfiles[]=
{
"\\fcclone\\sounds\\Start.wav",
"\\fcclone\\sounds\\Applause2.wav",
"\\fcclone\\sounds\\Kick.wav",
"\\fcclone\\sounds\\Part.wav",
"\\fcclone\\sounds\\notify.wav",
"\\fcclone\\sounds\\Ban.wav",
"\\fcclone\\sounds\\ping.wav",
"\\fcclone\\sounds\\fail.wav",
"\\fcclone\\sounds\\fail.wav",
};
These can be renamed to something more sensible now :)
There will be more sounds in the future.
OT BTW The reason for the names is that they're sounds I used to use for my irc client :)
OK, in the next install, I will narrow the wav files down to the ones in sound.cpp. Also, I didn't include any .flt files in the install, except rfcmine and jedi, because they are really not needed, are they?
And theres another thing, the manual resides both in \manual and \source\something, is this neccessary? I could just have the latex file in the source dir, and the rest in the manual folder.
Also, is the \ref directory needed? All the files in there are also in the main dir. Most of the files in \resources are not needed either, are they?
Did the install look good, did it work on your computer, does the license need any changes, etc... ?
Vidar Braut Haarr
AmigoSoft Productions
folk@popmail.com
Yes it's practically there.
I'll try doing a release with the script this weekend but I need to edit it...
> If you would like to contribute to AIFC GPL, please visit
> http://fcomm.sourceforge.net
Put a slash on the end of urls
http://fcomm.sourceforge.net/
> We are currently in need of people with skills in C and/or
> graphics design, and a sound engineer.
C++
Add something like "There are jobs available for a range of skills and abilities most people can contribute."
What's New?
> Release now includes docs in html and pdf format.
hmmm didnt seem to be in this archive! HTML format is a bit scrappy but the PDF is nice.
>Version 0.31:
> * Tons of bugfixes and optimizations.
> * Fixed the palette problem.
The palette problem is not fixed! Remember some of these entries (in readme.txt) are a bit optimistic!
> - New debug/function keys:
> 9 - Increase framerate (Min=3).
> 8 - Decrease framerate (Max=24576).
oh dear, me bad. Can anyone think of a clearer explanation? oh should be "f8" "f9" not just "8" "9".
There could be a comment at the end - ported to 32bits and for GCC compiler.
We need a way for multiple people to work on the setup script. Vidar see if you can get CVS working
perhaps have a setup\windows\ subdirectory the commands are (once you've got cvs working)
cvs add setup
cd setup
cvs add windows
cd windows
cvs add script.iss //whatever the script file is called
Zipping hardly reduces the size so I don't think it's necessary.
Maybe every install should include docs (at least the manual) as long as they're fairly small?
We should have a fleets directory where all the fleets are stored which has a shortcut so its easy to find.
hmm the uninstaller deletes everthing even if one of the fc files changed that's bad. But it doesn't remove new files which is good hmm.
A problem with including the HTML manual is that the graphics files clutter up the directory.
Nils-Arne please make it so those are in a subdirectory.
I managed to download innosetup hmm I have Delphi I could mess around with it but doesn't seem necessary.
It can compile conveniently via the command line. I will still make a tar.gz download for people who
don't want/can't use the setup program.
oh BTW Java comments seem to be the same as C++.