Currently templates for standalone form types (e.g. JFrame) include a main-method to test them with, so the user can execute and debug without writing additional code; other form types (e.g. JPanel)
 do not.

It would be rather easy to write an executor (installed by the Form Editor module and placed on templates) that would just handle the boilerplate to start up some form object and display it. So it wou
ld create an instance of the form class, add it to a Window of the appropriate type if it was not one already, attach the window listener, and show it. This way, even forms like JPanel`s could be test
ed by default; and e.g. user JFrame`s would not need to have testing code in them to be tested inside the IDE. Applets already work this way, so other form types could too.

Of course, some frames are supposed to be the entire application. So there should also be templates with external executor and a main method, called e.g. AWTForms/Frame_Application or SwingForms/JFram
e_Application (which could also have a menu bar by default?).

Anyone who did not have a default constructor for their form class would just write their own main-method (they could look at the JFrame_Application template for an idea of what to write if needed).