Hi there! Mark, after posting my last disk to you, I realised I`d spent days trying to get all the stuff that I wanted to do finished, that I`d hardly even looked at most of ACC8. After going through the disk and seeing your request for people to help, I decided to try and help in some way. Unfortunately, my coding experience is minimal, and most of that is really hardware specific! The only library calls I really use are Forbid, Permit, Open and Close Library! For this reason I don`t think I could really contributute source for the program, or even help debug your`s, but what I could do is help with testing and contribute ideas, for the assembler. I loaded up Devpac, and looked at what I thought was missing/could be improved. Most of these are very simple ideas which you have probably thought of yourself, but suggesting them won`t do any harm, so I may as well: 1. Help function. Apart from the block commands, the help function in Devpac doesn`t really do much. This could be improved considerably be adding little things like any special options for A68K or Blink. 2. Colour scheme. If you have the standard colour configuration (workbench) set up when you load Devpac, the colours are fine. But with a new colour scheme, some things become difficult to read, (yellow is not too clear when shown on white!) If the disk is to be distributed on PD disks, which are notorious for setting up garish colour schemes on their disks! Then you should allow the user to select/alter the colour combinations to increase readibilaty. 3. Are you going to have any sort of monitor with A68K? I read somewhere (Amiga Computing), that Amon is going to be upgraded to support symbol hunks (maybe!) You might want to have a choice of monitor, set in preferences which autoloads when you select the menu item, (a nice, fully integrated environment, eh?) As an idea, why not do a debugger after you`ve finsished this project! (Joke!) 4. You may like to include Steve Marshall`s ARP requestor patch, to stop programs ending in .bak, etc, appearing, or maybe to only show programs ending in .s? 5. Is there any way you can get the assembler to read a file crunched with Powerpacker? Is it possible to intercept the file selected with the ARP fileselector, and check if it needs decrunching, before passing it onto the editor? I don`t know how silly this idea is, as I`m not yet into this area of programming yet! All I can really do so far is hardware specific stuff, but I intend to learn all about using library routines, etc, very soon! 6. Only a little thing, but I noticed in most of your programs, you always put the `WANT TO QUIT` requester with the `CONT` button on the left hand side, and the `QUIT` one on the other side. This is the opposite of 99% of other PD programs, and every time I see a requester pop up after selecting quit, I instictively go to the left hand side! How about swapping them! (Jeez! He`s picky!) Well they`re just my initial ideas, I`ll have some others (Better ones!) soon I hope, after I`ve played around with it for a while! Good luck with the project! Neil. P.S. While we`re talking about ideas, I think Simon`s Squidkick would be really good if it would open a window and jump to the front when you press something like CTRL + ESCAPE! (Like POPCLI does!) It would be really handy to have to ASCII table appear in Devpac at the press of a button! (Or two!) Note: I just had a look at an older ACC disk, and noticed Simon asking somebody if they could help him see when somebody had pressed say `CTRL-ESC`. Is this why you wanted to know Simon? 13-02-91 21:36 P.P.S. One tiny critisim of the assembler is that it is becoming a little to Devpac`ish! Most of the menus are nearly the same (except the print one), and I`ve just looked at Steve`s assembler options mock-up, and it must be said that the options are almost exactly the same! I know it`s hard trying to produce a PD program to do the same job as a good commercial offering without copying ideas, but a little originality my stop people saying you`ve just done a straight PD conversion of the Devpac environment! I think you should ask what ACC readers think is missing from Devpac, no matter how small to (hopefully!) get some suggestions.