title: Java Swing: separating UI component from logic behaviour - how do you approach this?
body: <p>What I do, in NetBeans for example:</p>
  
  <ul>
  <li>create a UI component class, suffixed with Swing component type, e.g. JPanel, e.g. MyUIWidgetJPanel</li>
  <li>create a logic/behaviour class to handle the behaviour/logic, i.e. what happens when the UI component is used, e.g. buttons within it pressed etc., MyUIWidgetLogic</li>
  </ul>
  
  <p>I may also link components/logic together using references, if the behaviour/outcome of one component influences/impacts another, e.g. some options displayed are no longer relevant, or to give context sensitive options.</p>
  
  <p>What do you think of this? Good? Bad?</p>
  
  <p>What do you do?</p>