The Prerequisites menu also offers choices that allow you to validate your choice of prerequisites. At this stage of making DevelopChooser, you do not need to validate prerequisites. However, after you finish coding the application, and before you package it, you should verify that your application has the correct prerequisites using one or more of the following choices on the Prerequisites menu:
It also is advisable that you write down your application's current prerequisites if your application is complex or if it references classes using idioms which cannot be detected by static analysis, such as Smalltalk classAt: <class name> . Because the tools run by using the menu choices listed below cannot detect class names determined during runtime, use caution before deleting prerequisites based on the information returned by using these menu choices.
Thus, if your application uses visual parts, do not remove AbtViewApplication as a prerequisite. Using these menu choices might return information suggesting that AbtViewApplication is unnecessary because AbtViewApplication is not directly referenced in the application. AbtViewApplication is necessary to successfully package an application that uses visual parts.
As mentioned above, if your application uses visual parts, do not remove AbtViewApplication as a prerequisite.