Databases
StackOverflow2013
Postsdbo
POJava - best practice for event handling and reflect results back
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJava - best practice for event handling and reflect results back
    primarykey
    data
    text
    <p>Since I start to programming in Java, every time when I want to create a GUI and a more complex business logic every time I encounter the same problem.</p> <ol> <li>How can you entirely separate the GUI part from the logic part? Edited: Maybe is slightly wrong said "GUI part from the logic part". Rather, more correctly is "GUI part from the listeners part" because we don't want files with a huge amount of lines like when we wrote anonymous functions or inner classes.</li> </ol> <p>A result can be that:</p> <pre><code>public class MainFrame extends JFrame{ private final Handler handler = new Handler(); public MainFrame(){ //some code... final JButton b = new JButton("Click Me!"); b.putClientProperty("command", "some command or a static variable from a some commands class"); b.addActionListener(this.handler); } } // another class in another file public class Handler implements ActionListener{ @Override public void actionPerformed(ActionEvent e){ if(e.getSource() instanceof JButton){ final JButton source = (JButton)e.getSource(); if(source.getClientProperty("command").equals("some command or a static variable from a some commands class")){ //do something } } } } </code></pre> <p>If some of you know a better way to do that please tell to me.</p> <ol> <li><p>How to make the GUI respond with a refresh when an action is taken from? Because in the above example we wrote:</p> <pre><code>b.addActionListener(this.handler); </code></pre></li> </ol> <p>so only button b knows when the action was performed.</p> <p>In case that my solution for the first problem is not reliable for the second one please provide a complete solution for this post.</p> <p>I hope that will be helpful for more people.</p> <p>Thanks.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmKorbel
    1. USCiobanu Andrei
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POJava - best practice for event handling and reflect results back
      1. USlinski
      1. VTFavorite
    2. VO
      singulars
      1. POJava - best practice for event handling and reflect results back
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYour handler doesn't show any GUI changes. What do you want to happen in the handler?
      singulars
      1. POJava - best practice for event handling and reflect results back
      1. USBetaRide
    2. CO@BetaRide : in my vision, the Handler class from above is more like an dispatcher: he treat the source and send actions to controller/model/etc.
      singulars
      1. POJava - best practice for event handling and reflect results back
      1. USCiobanu Andrei
    3. CO@Ciobanu Andrei: It’s perfect if the handler dispatches to controller/model/etc. And there should be classes implementing Swing’s model interfaces and thus sending events if the action(s) modified model state. Then the GUI will update itself automatically as Swing components register themselves (sometimes indirectly) as listeners to the specified data model(s).
      singulars
      1. POJava - best practice for event handling and reflect results back
      1. USHolger
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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