Appendix E About The Author And Development The original GenTree v1.0 was developed by myself over an 9 month period. The bulk of the coding was completed in 6 months with cleanup and documentation taking another 3 months. GenTree was completed on free time: nights and weekends. The original GenTree v1.0 was developed with CanDo 2.0 running on an Amiga 2000HD with 13 Megs of RAM and GVP's 33MHz 68030. Since then, the development system hasn't changed, but Inovatronics (the developers of CanDo) has been busy up- dating CanDo. This program would never have been developed if it wasn't for CanDo. CanDo is a marvelous development tool, and it has only gotten better in each incarna- tion. I cannot recommend it highly enough. GenTree v1.0 had a few quirks in it be- cause of CanDo 2.0. Generally, Inovatronics have gotten rid of the limitations of 2.0 (If I was developing GenTree from scratch today, I would do it much differently). However, CanDo still has a few limitations. Just in case a CanDo developer reads this, I am going to list the features I'd like to see (ignore this if you don't have CanDo): · You cannot change the text of a menu item. For example, I wanted to change the Undo menu to be context-sensitive; "Undo typing", "Undo Paste", etc. · You cannot add menu items later. All menu items must be completely defined at development time. I had wanted to be able to have users define macros, and as each macro was defined, add it to a macro menu. · No access to the clipboard. I would love to be able to cut to and paste from the clipboard device. · Printer management of graphics is terrible. CanDo should allow graphic operations' output to be written to a postscript file which could later be sent to a postscript printer. · No access to system preferences. · Speed. This is not one of my biggest gripes. Currently, CanDo achieves ad- equate performance on a 68020 or above. However, it would be nice to be able to truly compile the project. · Variable window coordinates and size. CanDo currently works by opening your window and sizing it based on constants you define in development. You cannot move or resize your window until it has been opened. I would like to be able to change the size and position of the window in the before attachment script so that the window doesn't flash open and then move to where I want it.