• Interface for membership cards
   
  • Create a form by using Swing interface components on GribagLayoyt manager.
    Form could be used to manage membership database for a small company.
     
  • The form should contain following fields:
     
    • Number: personal number for a member
    • Login: login for a member (initials,nickname,…)
    • First name(s)
    • Last name
    • Type: membership type, for example…
      F = full member, J = junior member, H = honourary member, etc.
    • Position: for example…
      P = president, S = secretary; T = treasurer, etc.
    • Phone number
    • Email address
       
  •  Layout for the form could be following:

    Number ________                                   Login __________
    
    Names:1^st _____________________ Last _________________________

    Type      ______[#]_____________________

    Position ______[#]_____________________

    Phone _____________________         Email _____________________
    
     

  • Furthermore, the form should also have buttons for adding,updating,saving,cancelling and removing members.
     
  • On member type and position row user can type values into first field, but not into second one.
    And field Number should be readonly.
     
  • Could it be possible to create additional functions, which could make it easier to place components to the form: less rows of code than using direct accessing with GridBagLayout and GridBagConstrains?
     
  • Hint: JTextField components becomes very narrow, when they are placed on GridBagLayout.
    These components can be restored back to their normal size using following command:
     
    • jtf.setMinimumSize(jtf.getPreferredSize());
       

<Top>
 

Functions of form

• Phase 1: states of buttons (active/inactive)
   
  • Only buttons "Add" and "Update" are active. Rest of buttons are inactive (grayed).
    When user press…
     
  • "Add" button:
    • all fields on the form are cleared
    • buttons "Add" and "Update" become inactive
    • buttons "Save" and "Cancel" become active
       
  "Update" button:

  all fields on the form are cleared

  button "Add" becomes inactive

  buttons "Save","Cancel" and "Remove" become active
  
  "Save","Cancel" or "Remove" button:

  buttons "Save","Cancel" and "Remove" become inactive

  buttons "Add" and "Update" become active
   
  • The functions/states of the buttons are best shown by using a chart, which includes..
    • states "View","Update" and "Add"
    • a variable which uses these states
    • one method/funtions which controls the state of buttons
      
  • The variable is updated in the routines for buttons after which a function to disable buttons is called.
    ( harmaannutaNappi() ~ 'gray-up button')
     
    • Chart of states for buttons:

  increase   -----------------------------------> ADD
        /\                                                             \/
  VIEW >---- modify -----> UPDATE >-------|
       /\                                                              \/
        \  -------- save,cancel,remove  --------- /

   

<Top>
 

• Phase 2: updating fields
   
  • When adding or updating records (state ADD or UPDATE), user can modify fields except field Number and comment fields of Type and Position. In VIEW state all fields are in readonly state.
     
• Phase 3: automation for Login
   
  If Login field is empty when user saves record, program applies member’s initials as login
  (for example: James Bond à JB).
   
• Phase 4: lookups for Type and Position
   
  Values for second field (in Member type and Position) are applied by program depending values given in first field. Values are applied either when user exits the first field or by lookup button. Program should give a warning if given value in the first field is not possible (wrong input or does not exist ). Empty value is allowed.
   
  When user press lookup buttons for Member type or Position, program shows list of options to choose from.

<Top>

• Back