title: Alternative solution to null layout manager when absolute positioning is needed
body: <p>Few months ago i read this Swing tutorial <a href="http://zetcode.com/tutorials/javaswingtutorial/resizablecomponent/" rel="nofollow">http://zetcode.com/tutorials/javaswingtutorial/resizablecomponent/</a> for understanding how implementing resizable components inside Swing.</p>
  
  <p>The tutorial tells about using a null LayoutManager in order to have the possibility of absolute positioning child components.</p>
  
  <p>In a discussion relative to another subject @Andrew Thompson pointed out that using null layout is a bad idea. This article <a href="http://download.oracle.com/javase/tutorial/uiswing/layout/none.html" rel="nofollow">http://download.oracle.com/javase/tutorial/uiswing/layout/none.html</a> describe null layout manager as not desirable too, anyway it says that in certain situations the might be useful.</p>
  
  <p>In a situation where:</p>
  
  <ol>
  <li>i need absolute positioning for a JPanel's child components</li>
  <li>i need to implement my own bounding box conditions for child components (in order to establish possible overlapping situations )</li>
  <li>i need JPanel's child component be resizable</li>
  </ol>
  
  <p>Is correct in the described situation use a null layout manager?</p>
  
  <p>Or there are other better solutions to achieve that goals using a layout manager for my JPanel container component?</p>
  
  <p>thanks in advance</p>