I just thought of a few more Wish List items:
1: With some tedious testing on your part, you could avoid tedious testing on the part of every plug-in developer by calculating the memory needed.
2: This would probably be just as tedious as #1. NovaBurst could calculate the time needed to load and put that into the plug-in so the developer wouldn't have to line up the load status bar manually.
3: In several of my never-published plug-ins that I never finished I used VisBits extensively. Unfortunately I had trouble distincting different versions of a system. A version column or a flowchart for each system would help me keep track of these. Since the version number method doesn't have field in the EVN resources, you could create another resource or use the data fork that the user wouldn't edit directly, but the editor could use to keep track of information EVN wouldn't see, but NovaBurst would need for automatically controlling what Nova would see or improving the interface.
4: The advantage of the flowchart or system versions of #3 wouldn't mean much with the way people use VisBits now. But Nova Control Bits give us enough flexibility to allow a system to have several possible futures easily. But if a developer wants several mission strings to change different aspects of a system, they have to create all the combinations manually. If NovaBurst would find out what aspect needed to be changed for the mission string and took care of the combinations automatically the developer would have more time for more, longer plug-ins.
5: Finer control over the AI ship's custom enhancements than the resource shows is possible. NovaBurst simply creates an identical ship resource behind the scenes and makes the actual link in the file to this other ship resource. When the main ship resource is edited, the custom one is also edited except in the aspects that it has been customized. NovaBurst would try to condense as many custom ships as possible automatically. With any that were slightly different, the program could suggest that the user make them identical.
7: You didn't seem to understand what 21st Century Digital Boy meant when he suggested the feature that innovations that may be hard to implement be suggested by the editor to newbies. An example of this might be that the size of the power/fuel status bar represent how much power can be held. This wouldn't be mandatory, but some people might like it and never think of it, have time to create enough ďntf resources, or the know-how.
8: Nova test expressions act unpredictably when the developer doesn't force the order with parentheses. The solution to this is for NovaBurst to have preferences that will fix it in different ways or ask the user on a case by case basis.
9: The checkboxes for jump speed in the ship editor don't accurately represent what you can choose. Obviously a ship can only jump at one speed. Therefore a slider would be the best way to show this. There are other controls that could better be replaced with sliders or other types.
10: NovaBurst preferences might have the option to list resources numbers starting at 1 or 128.
------------------
Signed,
Brian Schack
"DOS Computers, manufactured by millions of companies, are by far the most popular, with about 70 million machines in use worldwide. Macintosh fans, on the other hand, may note that cockroaches are far more numerous than humans, and that numbers alone do not denote a higher life form."
--The New York Times, November 26, 1991 (also quoted in MacAddict 4)