Issue: Since most of the screens are going to be Dialogs, and the Dialogs I'll use are all modal (they block input from their parent window), they will have to be created each time they are called.  The way around this is to create a Panel with the necessary components, keep a copy of it, then when a Dialog is needed, create the Dialog and place the existing panel onto the Dialog.  Then just pack and show the Dialog.  There are going to be several types of Panels.  There will be picker or selection panels, sub panels, edit panels, and even some custom panels.  Here are those types explained more throughly with lists of where they will be used.

Discussion: The most common type will be the edit panel.  Most of the various Ticable classes has an edit panel of some sort.  Essentially, on an edit panel, there are input components which accept or display information about each Tic in the Ticable.  These panels are top level, that is they are placed on the Dialog, along with the header panel and the ButtonCommands panel.  There are several Ticable edit panels which are not top level.  That is they occur inside another panel or Dialog.  These are:

Another panel type is the sub panel.  This panel is an edit panel which is an input component on another edit panel.  That's why I call it a sub panel.  All but three are read only.  Here are the sub panels needed:

The final panel type is the picker, or selection panel. These are actually two slightly different panels, so I will show them separately.  The selection panel is used to display a list and the user is to pick one item from the list.  There is no need for a ListSelectionListener on the list.  Typically, these are a single list on a Dialog, so when the user makes a selection, the item is stored in a static field and the Dialog is disposed.  The Dialog which called up the selection Dialog then retrieves the selection and does something with it.  Here are the selection panels needed:

The picker panel is where a ListSelectionListener is needed because each time a new item is selected, another panel, and possibly other elements, must react by displaying information related to the item selected.  Here are the picker panels needed:

There are also a few custom Dialogs, and therefore custom panels to be created. &mnsp;The first is the Season selection panel.  Since there is no season Ticable, only a list of folder names, this must be custom.  The various Address Dialogs may need custom panels because of the complexity and interaction with the PostalCode Dialog.  The select Award Earned screen has several sort criteria options on it, so it will probably be custom.  Another is the Add Contest(s) Dialog used to allow the user to quickly fill in a list of contest dates.  It is complex with radio buttons and checkboxes.