Examples of SwingWorker

KFM.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it.
com.bbn.openmap.util.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it.
com.salas.bb.utils.swingworker.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html"> How to Use Threads for more details):
- Time-consuming tasks should not be run on the Event Dispatch Thread. Otherwise the application becomes unresponsive.
- Swing components should be accessed on the Event Dispatch Thread only.
These constraints mean that a GUI application with time intensive computing needs at least two threads: 1) a thread to perform the lengthy task and 2) the Event Dispatch Thread (EDT) for all GUI-related activities. This involves inter-thread communication which can be tricky to implement.

{@code SwingWorker} is designed for situations where you need to have a long running task run in a background threadand provide updates to the UI either when done, or while processing. Subclasses of {@code SwingWorker} must implementthe {@link #doInBackground} method to perform the background computation.

Workflow
There are three threads involved in the life cycle of a {@code SwingWorker} :
- Current thread: The {@link #execute} method is called on this thread. It schedules {@code SwingWorker} for theexecution on a worker thread and returns immediately. One can wait for the {@code SwingWorker} to completeusing the {@link #get get} methods.
- Worker thread: The {@link #doInBackground} method is called on this thread. This is where all backgroundactivities should happen. To notify {@code PropertyChangeListeners} about bound properties changes use the {@link #firePropertyChange firePropertyChange} and {@link #getPropertyChangeSupport} methods. By default there are two boundproperties available: {@code state} and {@code progress}.
- Event Dispatch Thread: All Swing related activities occur on this thread. {@code SwingWorker} invokes the{@link #process process} and {@link #done} methods and notifies any {@code PropertyChangeListeners} on this thread.
Often, the Current thread is the Event Dispatch Thread.

Before the {@code doInBackground} method is invoked on a worker thread, {@code SwingWorker} notifies any{@code PropertyChangeListeners} about the {@code state} property change to {@code StateValue.STARTED}. After the {@code doInBackground} method is finished the {@code done} method is executed. Then {@code SwingWorker} notifies any{@code PropertyChangeListeners} about the {@code state} property change to {@code StateValue.DONE}.

{@code SwingWorker} is only designed to be executed once. Executing a {@code SwingWorker} more than once will notresult in invoking the {@code doInBackground} method twice.

Sample Usage
The following example illustrates the simplest use case. Some processing is done in the background and when done you update a Swing component.

Say we want to find the "Meaning of Life" and display the result in a {@code JLabel}.
```
 final JLabel label; class MeaningOfLifeFinder extends SwingWorker<String, Object> { {@code @Override}public String doInBackground() { return findTheMeaningOfLife(); }  {@code @Override}protected void done() { try { label.setText(get()); } catch (Exception ignore) { } } } 
 (new MeaningOfLifeFinder()).execute(); 
```
The next example is useful in situations where you wish to process data as it is ready on the Event Dispatch Thread.

Now we want to find the first N prime numbers and display the results in a {@code JTextArea}. While this is computing, we want to update our progress in a {@code JProgressBar}. Finally, we also want to print the prime numbers to {@code System.out}.
```
 class PrimeNumbersTask extends SwingWorker<List<Integer>, Integer> { PrimeNumbersTask(JTextArea textArea, int numbersToFind) { //initialize }  {@code @Override}public List<Integer> doInBackground() { while (! enough && ! isCancelled()) { number = nextPrimeNumber(); publish(number); setProgress(100 * numbers.size() / numbersToFind); } } return numbers; } 
 {@code @Override}protected void process(Integer... chunks) { for (int number : chunks) { textArea.append(number + "\n"); } } } 
 JTextArea textArea = new JTextArea(); final JProgressBar progressBar = new JProgressBar(0, 100); PrimeNumbersTask task = new PrimeNumbersTask(textArea, N); task.addPropertyChangeListener( new PropertyChangeListener() { public  void propertyChange(PropertyChangeEvent evt) { if ("progress".equals(evt.getPropertyName())) { progressBar.setValue((Integer)evt.getNewValue()); } } }); 
 task.execute(); System.out.println(task.get()); //prints all prime numbers we have got 
```
Because {@code SwingWorker} implements {@code Runnable}, a {@code SwingWorker} can be submitted to an {@link java.util.concurrent.Executor} for execution. @param < T> the result type returned by this {@code SwingWorker's} {@code doInBackground} and {@code get} methods @param < V> the type used for carrying out intermediate results by this {@code SwingWorker's} {@code publish} and{@code process} methods
Note: This is a backport from java 1.6
com.visitrend.ndvis.deprecated.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() pm the SwingWorker after creating it.
com.vividsolutions.jtstest.testbuilder.ui.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it.
edu.stanford.genetics.treeview.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it.
fr.soleil.utils.swingworker.SwingWorker
javax.swing.SwingWorker
oracle.com/javase/tutorial/uiswing/concurrency/index.html"> Concurrency in Swing for more details):
- Time-consuming tasks should not be run on the Event Dispatch Thread. Otherwise the application becomes unresponsive.
- Swing components should be accessed on the Event Dispatch Thread only.
These constraints mean that a GUI application with time intensive computing needs at least two threads: 1) a thread to perform the lengthy task and 2) the Event Dispatch Thread (EDT) for all GUI-related activities. This involves inter-thread communication which can be tricky to implement.
{@code SwingWorker} is designed for situations where you need to have a longrunning task run in a background thread and provide updates to the UI either when done, or while processing. Subclasses of {@code SwingWorker} must implementthe {@link #doInBackground} method to perform the background computation.
Workflow
There are three threads involved in the life cycle of a {@code SwingWorker} :
- Current thread: The {@link #execute} method iscalled on this thread. It schedules {@code SwingWorker} for the execution on aworker thread and returns immediately. One can wait for the {@code SwingWorker} tocomplete using the {@link #get get} methods.
- Worker thread: The {@link #doInBackground}method is called on this thread. This is where all background activities should happen. To notify {@code PropertyChangeListeners} about bound properties changes use the{@link #firePropertyChange firePropertyChange} and{@link #getPropertyChangeSupport} methods. By default there are two boundproperties available: {@code state} and {@code progress}.
- Event Dispatch Thread: All Swing related activities occur on this thread. {@code SwingWorker} invokes the{@link #process process} and {@link #done} methods and notifiesany {@code PropertyChangeListeners} on this thread.
Often, the Current thread is the Event Dispatch Thread.
Before the {@code doInBackground} method is invoked on a worker thread,{@code SwingWorker} notifies any {@code PropertyChangeListeners} about the{@code state} property change to {@code StateValue.STARTED}. After the {@code doInBackground} method is finished the {@code done} method isexecuted. Then {@code SwingWorker} notifies any {@code PropertyChangeListeners}about the {@code state} property change to {@code StateValue.DONE}.
{@code SwingWorker} is only designed to be executed once. Executing a{@code SwingWorker} more than once will not result in invoking the{@code doInBackground} method twice.
Sample Usage
The following example illustrates the simplest use case. Some processing is done in the background and when done you update a Swing component.
Say we want to find the "Meaning of Life" and display the result in a {@code JLabel}.
```
 final JLabel label; class MeaningOfLifeFinder extends SwingWorker<String, Object> { {@code @Override}public String doInBackground() { return findTheMeaningOfLife(); } {@code @Override}protected void done() { try { label.setText(get()); } catch (Exception ignore) { } } } (new MeaningOfLifeFinder()).execute(); 
```
The next example is useful in situations where you wish to process data as it is ready on the Event Dispatch Thread.
Now we want to find the first N prime numbers and display the results in a {@code JTextArea}. While this is computing, we want to update our progress in a {@code JProgressBar}. Finally, we also want to print the prime numbers to {@code System.out}.
```
 class PrimeNumbersTask extends SwingWorker<List<Integer>, Integer> { PrimeNumbersTask(JTextArea textArea, int numbersToFind) { //initialize } {@code @Override}public List<Integer> doInBackground() { while (! enough && ! isCancelled()) { number = nextPrimeNumber(); publish(number); setProgress(100 * numbers.size() / numbersToFind); } } return numbers; } {@code @Override}protected void process(List<Integer> chunks) { for (int number : chunks) { textArea.append(number + "\n"); } } } JTextArea textArea = new JTextArea(); final JProgressBar progressBar = new JProgressBar(0, 100); PrimeNumbersTask task = new PrimeNumbersTask(textArea, N); task.addPropertyChangeListener( new PropertyChangeListener() { public  void propertyChange(PropertyChangeEvent evt) { if ("progress".equals(evt.getPropertyName())) { progressBar.setValue((Integer)evt.getNewValue()); } } }); task.execute(); System.out.println(task.get()); //prints all prime numbers we have got 
```
Because {@code SwingWorker} implements {@code Runnable}, a {@code SwingWorker} can be submitted to an{@link java.util.concurrent.Executor} for execution. @author Igor Kushnirskiy @param < T> the result type returned by this {@code SwingWorker's}{@code doInBackground} and {@code get} methods @param < V> the type used for carrying out intermediate results by this{@code SwingWorker's} {@code publish} and {@code process} methods @since 1.6
jsky.util.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it.
net.java.sip.communicator.plugin.desktoputil.SwingWorker
Utility class based on the javax.swing.SwingWorker. SwingWorker is an abstract class that you subclass to perform GUI-related work in a dedicated thread. In addition to the original SwingWorker this class takes care of exceptions occurring during the execution of the separate thread. It will call a catchException() method in the Swing thread if an exception occurs. @author Yana Stamcheva @author Lyubomir Marinov
net.java.sip.communicator.util.swing.SwingWorker
Utility class based on the javax.swing.SwingWorker. SwingWorker is an abstract class that you subclass to perform GUI-related work in a dedicated thread. In addition to the original SwingWorker this class takes care of exceptions occured during the execution of the separate thread. It would call a catchException() method in the Swing thread if an exception occurs. @author Yana Stamcheva
net.xoetrope.xui.helper.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it. $Revision: 2.2 $
nu.fw.jeti.util.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it.
org.analyse.core.util.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it.
org.apache.uima.tools.util.gui.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it.
org.fcrepo.client.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it.
org.jdesktop.swingworker.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html"> How to Use Threads for more details):
- Time-consuming tasks should not be run on the Event Dispatch Thread. Otherwise the application becomes unresponsive.
- Swing components should be accessed on the Event Dispatch Thread only.
These constraints mean that a GUI application with time intensive computing needs at least two threads: 1) a thread to perform the lengthy task and 2) the Event Dispatch Thread (EDT) for all GUI-related activities. This involves inter-thread communication which can be tricky to implement.
{@code SwingWorker} is designed for situations where you need to have a long running task run in a background thread and provide updates to the UI either when done, or while processing. Subclasses of {@code SwingWorker} must implement the {@see #doInBackground} method to perform the background computation.
Workflow
There are three threads involved in the life cycle of a {@code SwingWorker} :
- Current thread: The {@link #execute} method iscalled on this thread. It schedules {@code SwingWorker} for the execution on aworker thread and returns immediately. One can wait for the {@code SwingWorker} tocomplete using the {@link #get get} methods.
- Worker thread: The {@link #doInBackground} method is called on this thread. This is where all background activities should happen. To notify {@code PropertyChangeListeners} about bound properties changes use the{@link #firePropertyChange firePropertyChange} and{@link #getPropertyChangeSupport} methods. By default there are two boundproperties available: {@code state} and {@code progress}.
- Event Dispatch Thread: All Swing related activities occur on this thread. {@code SwingWorker} invokes the{@link #process process} and {@link #done} methods and notifiesany {@code PropertyChangeListeners} on this thread.
Often, the Current thread is the Event Dispatch Thread.
Before the {@code doInBackground} method is invoked on a worker thread,{@code SwingWorker} notifies any {@code PropertyChangeListeners} about the{@code state} property change to {@code StateValue.STARTED}. After the {@code doInBackground} method is finished the {@code done} method isexecuted. Then {@code SwingWorker} notifies any {@code PropertyChangeListeners}about the {@code state} property change to {@code StateValue.DONE}.
{@code SwingWorker} is only designed to be executed once. Executing a{@code SwingWorker} more than once will not result in invoking the{@code doInBackground} method twice.
Sample Usage
The following example illustrates the simplest use case. Some processing is done in the background and when done you update a Swing component.
Say we want to find the "Meaning of Life" and display the result in a {@code JLabel}.
```
 final JLabel label; class MeaningOfLifeFinder extends SwingWorker<String, Object> { {@code @Override}public String doInBackground() { return findTheMeaningOfLife(); } {@code @Override}protected void done() { try {  label.setText(get()); } catch (Exception ignore) { } } } (new MeaningOfLifeFinder()).execute(); 
```
The next example is useful in situations where you wish to process data as it is ready on the Event Dispatch Thread.
Now we want to find the first N prime numbers and display the results in a {@code JTextArea}. While this is computing, we want to update our progress in a {@code JProgressBar}. Finally, we also want to print the prime numbers to {@code System.out}.
```
 class PrimeNumbersTask extends  SwingWorker<List<Integer>, Integer> { PrimeNumbersTask(JTextArea textArea, int numbersToFind) {  //initialize  } {@code @Override}public List<Integer> doInBackground() { while (! enough && ! isCancelled()) { number = nextPrimeNumber(); publish(number); setProgress(100 * numbers.size() / numbersToFind); } } return numbers; } {@code @Override}protected void process(List<Integer> chunks) {  for (int number : chunks) { textArea.append(number + "\n"); } } } JTextArea textArea = new JTextArea(); final JProgressBar progressBar = new JProgressBar(0, 100); PrimeNumbersTask task = new PrimeNumbersTask(textArea, N); task.addPropertyChangeListener( new PropertyChangeListener() { public  void propertyChange(PropertyChangeEvent evt) { if ("progress".equals(evt.getPropertyName())) { progressBar.setValue((Integer)evt.getNewValue()); } } }); task.execute(); System.out.println(task.get()); //prints all prime numbers we have got 
```
Because {@code SwingWorker} implements {@code Runnable}, a {@code SwingWorker} can be submitted to an{@link java.util.concurrent.Executor} for execution. @author Igor Kushnirskiy @version $Revision: 1.6 $ $Date: 2008/07/25 19:32:29 $ @param < T> the result type returned by this {@code SwingWorker's}{@code doInBackground} and {@code get} methods @param < V> the type used for carrying out intermediate results by this{@code SwingWorker's} {@code publish} and {@code process} methods
org.jpedal.utils.SwingWorker
org.openquark.util.ui.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it.
org.owasp.webscarab.util.swing.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it.
org.rioproject.tools.ui.util.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html
Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it.
viewer.common.SwingWorker
sun.com/docs/books/tutorial/uiswing/misc/threads.html Note that the API changed slightly in the 3rd version: You must now invoke start() on the SwingWorker after creating it.

Examples of KFM.SwingWorker

                Rectangle tR2 = tDialog.getBounds();
                tDialog.setLocation(tRect.x + (tRect.width - tR2.width) / 2,
                                    tRect.y + (tRect.height - tR2.height) / 2);
                */


                SwingWorker tWorker;
                mRS = aRS;
                if(mUseTableModel) { // build table model
                    tWorker = new SwingWorker() {
                        public Object construct() {
                            try {
                                mModel = new TsqlTableModel(mRS);
                            } catch(SQLException e) {
                                System.err.println("new TableModel: " + e);
                            }
                            TsqlProgressDialog.getInstance().hide();
                            return null;
                        }
                    };
                    tWorker.start();
                    tDialog.show();


                    mAbortedQuery = tDialog.isAborted();
                } else {
                    mModel = null;
                }


                tWorker = new SwingWorker() {
                    public Object construct() {
                        try {
                            printResultSet(mModel, mRS);
                        } catch(Exception e) {
                            System.err.println("printResultSet: " + e);
                        }
                        TsqlProgressDialog.getInstance().hide();
                        return null;
                    }
                };


                tDialog.setTitle("Printing Resultset");
                tWorker.start();
                tDialog.show();
            } finally {
                // enable output textarea
                mInQuery = false;
                _outputGui(mInQuerySB.toString());

View Full Code Here

Examples of com.bbn.openmap.util.SwingWorker

     * LinkListener from a new thread.
     */
    public void startUp() {
        // Have to use a swing worker so that the calling thread
        // doesn't get hung up on launching the runnable.
        SwingWorker sw = new SwingWorker() {
            public Object construct() {
                if (Debug.debugging("link")) {
                    Debug.output("LinkListener self-starting...");
                }
                getListener().start();
                return null;
            }
        };
        sw.execute();
    }

View Full Code Here

Examples of com.salas.bb.utils.swingworker.SwingWorker

            }
        };
        itemsList.addActionListener(listener);


        // Start populating
        SwingWorker scanner = model.scan();
        scanner.addPropertyChangeListener(new ScannerListener());
        scanner.execute();
    }

View Full Code Here

Examples of com.visitrend.ndvis.deprecated.SwingWorker

   * This is pretty much already built for you, you would put your task code
   * in the doSomething method which you would override. However, you can also
   * override this method if you like.
   */
  public void go() {
    final SwingWorker worker = new SwingWorker() {
      public Object construct() {
        progress = 0;
        done = false;
        canceled = false;
        statMessage = null;
        return doSomething();
      }


      public void finished() {
        complete();
      }
    };
    worker.start();
  }

View Full Code Here

Examples of com.vividsolutions.jtstest.testbuilder.ui.SwingWorker

  
  private SwingWorker worker = null;
  
  private void runFunctionWorker()
  {
    worker = new SwingWorker() {
      Stopwatch timer;
      
      public Object construct()
      {
        return computeResult();

View Full Code Here

Examples of edu.stanford.genetics.treeview.SwingWorker

    * Called to start the task. I don't know why we bother with the ActualTask class, so don't ask.
    */
    void go(DataModel tvmodel) {
      final DataModel model = tvmodel;
      setCurrent(0);
      final SwingWorker worker = new SwingWorker() {
        public Object construct() {
          return new ActualTask(model);
        }
      };
      worker.start();
    }

View Full Code Here

Examples of edu.stanford.genetics.treeview.SwingWorker

    /**
    * Called to start the task. I don't know why we bother with the ActualTask class, so don't ask.
    */
    void go() {
      setCurrent(0);
      final SwingWorker worker = new SwingWorker() {
        public Object construct() {
          return new ActualTask();
        }
      };
      worker.start();
    }

View Full Code Here

Examples of edu.stanford.genetics.treeview.SwingWorker

  /**
   * @throws Exception
   */
  private void attemptRegistration() throws Exception {
    loadProgress = new LoadProgress("Registering Java Treeview...", null);
      final SwingWorker worker = new SwingWorker() {
        public Object construct() {
          run();
          return null;
        }
      };
      // start up the worker thread
      worker.start();
      loadTimer.start();


      // show a modal dialog, should block until loading done...
      loadProgress.setIndeterminate(true);
      loadProgress.pack();

View Full Code Here

Examples of edu.stanford.genetics.treeview.SwingWorker

  }
  
  public void loadInto() throws LoadException {
    loadProgress = new LoadProgress2(targetModel.getFileSet().getRoot(), parent);
    loadProgress.setPhases(phases);
    final SwingWorker worker = new SwingWorker() {
      public Object construct() {
        run();
        return null;
      }
    };
    // start up the worker thread
    worker.start();
    loadTimer = new javax.swing.Timer(200, new TimerListener());
    loadTimer.start();
    // show a modal dialog, should block until loading done...
    loadProgress.setIndeterminate(true);
    ((LoadProgress2) loadProgress).pack();
    loadProgress.setVisible(true);
    
    // but just in case it doesn't, we'll join on the worker
    try {
      worker.join();
    } catch (InterruptedException e) {
      // TODO Auto-generated catch block
      e.printStackTrace();
    }
    // System.out.println("loadNew 6, ex: " + fileLoader.getException());

View Full Code Here

Examples of fr.soleil.utils.swingworker.SwingWorker

        }
        else {
            System.out.println("Usage : [Counter] [Diffractometer]");
        }


        final SwingWorker worker = new SwingWorker() {
            Tumba application;


            public Object construct() {
                application = new Tumba();
                application.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
                application.setModel(model);
                application.getSplash().progress(3);
                application.getSplash().setVisible(false);
                application.setVisible(true);
                return application;
            }


            // Runs on the event-dispatching thread.
            public void finished() {
                application.setVisible(true);
            }
        };
        worker.start();
    }

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.