Connectivity Kit Editor enhancements

[Bob Frazee]

Quote:Tim Wessman wrote:
There are still a ton of people trying to use "programs" in the same way as they work on the 48 series. We really envisioned each program file to contain a collection of routines, data, and so on rather then a single function or two. I agree that some improvement around organization might be helpful, but I am not certain what form this should take at all...

My concern about the above statement, is that the connectivity kit editor opens the whole file for editing. If the file is large and contains numerous routines, data and so on..., then there is a chance to inadvertently change something some where in that file. Now I have the whole file to look through to find the error, rather than a small routine.

Well, back in the mid 80's, Microsoft had a DOS programming language called QuickBasic 4.5(qb45). QuickBasic is the one I mention here, because it is the one I have some experience with. With that editor, you could have one large file with a collection of routines in it (the way you envisioned programming on the Prime), and that editor allowed you to open the routines individually for editing. If something got inadvertently messed up, you knew where the problem was.

This editor would also allow you to have individual program, subroutine, and function files, similar to the way you typically program on the 48 series. Now this "ton of people trying to use "programs" in the same way as they work on the 48 series", would be able to do so. Typically you would have this collection of files in a folder or library (hint, hint, Prime memory organization).

So..., my suggestion would be to change the way the connectivity kit editor operates, change the way the memory manager operates(to handle folders or library's properly), and leave the programming language alone.

Thanks for reading.
rcf