Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-29653

Re-running an afw.display getDisplay() does not re-display the URL for a Firefly display

    XMLWordPrintable

Details

    Description

      (Reported by mfisherlevine, who regularly uses Firefly in a "traditional" Jupyter notebook run on a development server.)

      When afw.display's getDisplay() is run, with a 'firefly' backend, in a non-Nublado notebook environment, the cell produces a line of HTML-formatted output that contains a clickable link to the appropriate display, so that it's easy to open in a new browser.

      (NB: in this mode the JupyterLab extension / tab is by definition not available)

      When the cell is re-executed with the same kernel, the line of formatted output disappears and is not re-displayed. This makes it difficult to find the correct URL to use.

      Attachments

        Issue Links

          Activity

            It's also worth noting here that I routinely use Firefly in a Jupyter Lab session opening in a separate tab by choice (i.e. when the extension tab is available), because I want it in a separate window as a head's up display on a different monitor.

            mfisherlevine Merlin Fisher-Levine added a comment - It's also worth noting here that I routinely use Firefly in a Jupyter Lab session opening in a separate tab by choice ( i.e. when the extension tab is available), because I want it in a separate window as a head's up display on a different monitor.

            Verified that the lower-level function that is invoked, FireflyClient.display_url(), does not have this problem. It uses a possibly outdated piece of IPython-specific code to display rendered HTML, depending on whether it thinks it's in an IPython environment, but that's not the source of the problem.

            It's one layer up in display_firefly, where it decides what to display based on whether or not it thinks a browser has been launched successfully. It looks easily fixable.

            gpdf Gregory Dubois-Felsmann added a comment - Verified that the lower-level function that is invoked, FireflyClient.display_url() , does not have this problem. It uses a possibly outdated piece of IPython-specific code to display rendered HTML, depending on whether it thinks it's in an IPython environment, but that's not the source of the problem. It's one layer up in display_firefly , where it decides what to display based on whether or not it thinks a browser has been launched successfully. It looks easily fixable.

            People

              gpdf Gregory Dubois-Felsmann
              gpdf Gregory Dubois-Felsmann
              Gregory Dubois-Felsmann, Merlin Fisher-Levine, Trey Roby
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Jenkins

                  No builds found.