Then, it should suggest how the dependency should be written in the source - as an import, or qualified ident. A separate Proposal is available. Should have features 1.2.1. The Wizard should anticipate plugging of panels from other modules - one possible solution is to utilize xml layered filesystem for it. Last, but not least, the Wizard should thoroughly analyze template contents and block off the user from editing some areas, in Form templates, for example, the user should not be allowed to change supertype of the class being designed.
Details are yet to be documented.
Although simple, this feature depends on implementation of UI's Icon Badging Proposal . May have features 1.3.1. The code synchronization is a tricky feature because it attempts to change a code that may be already customized by the user. The current UI is not providing enough information about what exactly is about to be done. To be documented.