Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. COI'm unsure if that is the case. I'd say my GUIs & main are mutually consuming each-other (?). --- The main thread should firstly create a GUI for NTLM authentication (username, password, proxy, workstation and domain), then wait for the user to input that data, and then, consume it by authenticating it's webclient (a "headless browser" that will be used to webscrap whats nessessary). Then, the main thread will start webscraping, and (create) a "status-feedback" GUI will (consuming main's data) keep the user aware of the progress...Similar main<->GUI interactions happen throwout the program.
      singulars
    2. COThen you just need a GUI showing several panels or frames one after another, and a SwingWorker to do all the authentication, webscraping tasks in the background. Or you do as I described, and invoke `SwingUtilities.invokeLater()` from the main thread to update the GUI from the main thread.
      singulars
    3. COSorry, but I'm not understanding how I'd implement either of those methodologies in this case. --- The input GUIs are to gather the minimum the program needs for proceeding and can't get by itself. In this case, that is an NTLM-Auth. needed to do webscraping, and what further refinement to do with the scraped data after it has been gathered. Meaning: I "don't need" background-processing for my input GUIs, they are replaced by an output (status) GUI during processing times. --- Anyways, thanks to `invokeAndWait()` I think I've found the trick. See Q. update; I'll be glad if you can confirm it.
      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