Implementing a Prototype to Demo your Scenario

Before starting this assignment, each individual should work through the GUI building exercises here. Do the Netbeans exercise first then the Eclipse WindowBuilder one. Look at the code generated by the builders. Code commonly has to be adjusted manually for nontrivial applications. Swing already has things like FileChoosers, ColorChoosers and ways to make simple Dialogs.  Take an agile approach and don't try to pack in every feature you can think of. Focus on what will give the basic required features in the near term. We will be in the lab Wed. through Mon. (3/23-3/28) to allow for and check on progress.

Working in pairs (Groups A-C split into 2 subgroups, D may work as 1 group - this is a good chance to try out variations if you have been struggling with how to merge different design ideas.), construct a prototype based upon your group's design. (You don't have to stay with the design developed in the exercises.) You may use Netbeans, WindowBuilder, code by hand or any combination.


Since it is a prototype the numbers can be "hardwired". They are used to give a more realistic feel to the prototype even though the true conversion functionality need not be implemented. While the prototype does not have to directly allow the user to enter numbers, it should support a scenario for your design illustrating the interaction sequence described in a-e below (PolygonMaker Phase 2). Screen captures of your prototype should be suitable to create a storyboard to illustrate your scenario.

Required interaction sequence for scenario.

Prototypes will be demoed so each group can observe the variety of proposed solutions.

Netbeans has a Help Menu where you can learn more about the Netbeans GUI Builder.
Eclipse also
has a Help feature where you can learn more about WindowBuilder.
There are also many online sources of information about GUI building with WindowBuilder and also  with Netbeans and building Swing interfaces.