I have pretty much finished my DOS based ship creator. It is very crude in the
way of the user interface (I'm currently starting to work on a Windows
version) but I believe it is functional. I'm lloking for a few outside people
(ie other than me) to try it out and see if they can find any bugs I haven't
yet. If anyone is interested please private email me. The compressed file
containing the executables, readme, and some test designs is around 300K.
Any takers?
+++++++++++++++
+------------+ +----------------+
The FTSC website has moved to http://ftsc.congdonweb.net and will
hopefully be fully operational fairly soon. The site is now hosted by a fellow
FT player Chris Congdon at congdonweb, so thanks to him the program is once
again available for download.
I have being (rather sporadically) working on version 2 of the ship creator,
but progress is steady. I will try and get some screen shots on the new
website soon along with some more info on the program itself. There have been
big changes, but all for the better and it is a LOT easier to use.
Hello All,
First let me apologise for the lack of recent correspondence and updates. I
have being very busy lately, keeping stupidly long days (and nights) and
working my backside off on a University project. So just an update on a few
things:
1) The vicious Australian wildlife hasn't gotten the best of me yet, I've
being able to fend it off with what I've learn't of the Crocodile Hunter,
strewth, that show is useful! Thanks for the concern anyway.
2) The FTSC project is still running! It may not look that way but it is, its
just caught in stasis.
3) The website is currently sitting idle at http://ftsc.congdonweb.net
no updates have been posted for ages, but I intend to publicy release a very
early beta, which will probably be termed a prototype as I intend to start
from scratch doing it properly. (Now all I have to do is workout what I did
with the links and instructions).
4) What do I intend to do with the FTSC? Well I intend to start again doing
the following: a) Setting out what I will do properly from the start and
fixing it in a proper requirements specification, eliminating a lot of the
reasons for delays and problems in previous versions. b) Create a proper
software architecture, which will make the program far easier to produce (as
I've being learning in the last few weeks) c) Produce a detailed design
document which contributes to the quality of program and make implementation
far easier (i hope). d) Produce a test plan and do significantly more testing.
This, although time consuming, will greatly improve the program. I may require
help from some of you guys in this one. e) Use a better language, and make it
portable, supporting at least Windows and linux, and maybe Mac OS. (Mac OS X
and BSD will probably be fairly straight forward from linux). f) In other
words, I don't intend to go at it head strong with a bit of programming
knowledge like I started off. I intend to sit down and plan the project.
Hopefully I will be able to produce some progress in a few weeks time after
exams, but if what my uni project supervisors tell me is true, I won't be
getting much of a holiday.
Well I will hopefully post again in a few days with the beta or 'prototype' of
version 2, but no promises.
Cheers,
Andrew Ayres schrieb:
> 4) What do I intend to do with the FTSC? Well I intend to
Requirements specs? Proper architecture? Design document? Testing?
Where have I heard all this before ? ;-)
> From experience - they do help a lot. If used.
Good luck to you Karl Heinz