I have difficulty tracking down the attachments to my original posts
, so I'm posting a series of attachments that cover most of what you guys are trying to find out.
Could these please go into the downloads section so that people can find them? Pretty please
Just a recap of some of the history:
First, there was NO documentation on the original AMOS Pro V2.0 sources. The zip archive is just a dump of the development environment from one of the developers. So it contains all sorts of sources that were (presumably) used in taking AMOS Pro from V1.xx to V2.0. The first task was to rationalise this lot and check the relevant sources against the binaries in the V2.0 distribution. That threw up a few little headaches but easily solved.
There were also a number of versions of the V2.0 binaries out there with some fixes in them. These were obviously assembled from the sources (rather than hacked in) but those sources were not available. No idea who the authors were but they obviously had access to the original sources. The early V2.10 release fixed all those and got rid of the slight differences in between the sources and the binaries. One I missed was the source for the Editor Config file (now also fixed and will be in the attachments in the following posts).
Some sources were completely missing. I've re-created them and they're also in the following posts. (I had to as I needed to add an extra menu item to the Editor
.)
As I said up front, it probably takes a while to track down the info in some of my posts. But I don't want to take any more time out of the work I'm doing to go through it all again
. And it looks like you've found most of it already. So I'll leave that for you to spend a couple of evenings reading through it...
On with the status... It's very hard to get a repository going for this code as currently I've got the Editor, AMOSPro. AMOSPro.Lib and most of the accessory programs all over the kitchen table at the moment. And I've found it difficult enough keeping versioning going successfully in an Amiga environment with my own code! What I would suggest is that you go ahead with your ideas calling it V2.10. I'll rebadge to V2.20. Any good ideas coming out of your work can be integrated later. My version diverges quite a bit from the original architecture:
- The Help System is radically different as AMOSPro checks for individual help files as it loads the libraries. This allows help files to be written for extensions and 'plugged in' simply by adding the *.txt and *.map files alongside the library files. It also uses sorted lists of the AMOS Tokens for the *.map files instead of text. So a quick tokenise and binary search is used instead of the slow text search. The Help file text is still being rewritten, which is a mammoth task in itself. I do a bit until I go crazy and then do something else for a while to get my sanity back .
- Just about all the screens now allow a wheel mouse to be used for scrolling. This change goes through anything using DBL code (which is most of AMOS! - learn DBL code!) and the Editor.
- The Editor allows the user to define Syntax Highlighting. This takes some free space in the Editor Config file and in the A5 offsets. I'll publish what I've 'reserved' so we don't clash.
- Quite a few of the Accessories also have bugs. So the fixes spread into *.AMOS sources as well as the *.s sources.
- I haven't looked at the compiler code much as it would just be another distraction at the moment. However one of my fixes cuts into the compiler code. So I'll rationalise that and publish the changes. More than anything else, the compiler is what needs looking into...
Enough blather. The first set of attachments is for the original sources and their dependencies. These are documentary only but you need to know where you're coming from. The source texts have been parsed through a database app I wrote. That allowed the columns to be aligned and a consistent EOL comment regime to be imposed when they were output. The originals also contained a lot of debugging conditional assembly which got confusing when tracing through the code. These have been left in place (you never know when you might need something similar) but commented out. The sources are easier to read if the syntax is highlighted but not everyone's got a suitable text editor that does that. So I've also included PDFs for anyone that can't do that themselves.
More to come today (and probably tomorrow as my back's now killing me and I've just realised I need to edit something out of a couple of the missing sources for the Editor Menus - my additions.)