Note that there are some explanatory texts on larger screens.

plurals
  1. USPeter Walser
    primarykey
    data
    text
    plurals
    1. COYes, very often the implementation classes will remain the same for the whole life cycle of a project, and usually there will be one implementation class per interface in the Factory. But nevertheless the point of a Factory is to keep it open and allow implementation classes to be exchanged in the future. Adding package restrictions to the factory would violate its intention and hinder refactoring (by exchanging the implementation) in the future. Even for projects where you're pretty sure that the implementation classes are never exchanged, it's better to keep this point open.
      singulars
    2. COMost watermarks are drawn OVER the content. If you want to do this, call super.paintComponent(g) first, and then draw your semitransparent watermark image (or text) over it. You can either chose to have a transparent image, or work with alpha composites to get the transparency effect. Also you may want to tile your watermark instead of just painting it on the upper left corner. I'd suggest you make a reusable Watermark container that paints the watermark over its content, so you are free to embed the JTextArea (watermarks scroll with the text) or JScrolledPane (watermark stays, text scrolls)
      singulars
    3. COIt's valid for a handler to be enabled but not 'handled'. The 'activeWhen' condition is optional, when not specified the handler will be active all the time. The problem is still that changes in the handler are not notified, and the specific handler for cut/copy/paste cannot be observed.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload