1. 03 Dec, 2018 6 commits
    • Florian Müllner's avatar
      application: Avoid duplicated ::prepare-shutdown emissions · 725a41a5
      Florian Müllner authored
      Since commit 00ab02ca added the ability to run in the background,
      the ::prepare-shutdown signal is emitted either when the main window
      is closed (and the app shouldn't keep running), or when explicitly
      quitting the app. But as the quit action also closes all windows, it
      is possible for the signal to be emitted twice, resulting in a warning
      when the telepathy client releases an additional app reference (it
      doesn't hold).
      
      Avoid this by making sure the signal handler which emits the signal
      when closing the main window is disconnected from the quit action.
      
      !79
      725a41a5
    • Florian Müllner's avatar
      mainWindow: Don't destroy notification queues with window · 53939f8f
      Florian Müllner authored
      Both queues are owned by the application, which may outlive the main
      window. It probably makes sense to rethink the ownership in the future,
      but for now avoid warnings from follow-up main windows by not destroying
      them with the previous window.
      
      !79
      53939f8f
    • Florian Müllner's avatar
      mainWindow: Disconnect roomManager signals on destroy · a99b5f5d
      Florian Müllner authored
      The room mananager is a singleton whose lifecycle is tied to the
      application, while any widget's lifecycle is tied to the window.
      App- and window lifecycle are different when Polari is set up to
      keep running in the background, so disconnect the signals to avoid
      warnings.
      
      !79
      a99b5f5d
    • Florian Müllner's avatar
      roomStack: Disconnect roomManager signals on destroy · bf7d2366
      Florian Müllner authored
      The room mananager is a singleton whose lifecycle is tied to the
      application, while any widget's lifecycle is tied to the window.
      App- and window lifecycle are different when Polari is set up to
      keep running in the background, so disconnect the signals to avoid
      warnings.
      
      !79
      bf7d2366
    • Florian Müllner's avatar
      chatView: Fix warning on shutdown · 1605f61a
      Florian Müllner authored
      One reason for a nick status change is that we disconnect the account.
      If we also close the corresponding room at the same time (for example
      on shutdown), there's a good chance that the room's channel property
      is unset after we send the request to ack all pending messages, but
      before the operation's callback is called. Avoid accessing an undefined
      property in that case by using the callback parameter, which will still
      be alive under all circumstances at that point.
      
      !79
      1605f61a
    • Florian Müllner's avatar
      chatView: Remove left-over code · 0743025d
      Florian Müllner authored
      The "early" return became pointless when commit d557dfef removed all
      the code that followed it.
      
      !79
      0743025d
  2. 10 Nov, 2018 2 commits
  3. 01 Nov, 2018 1 commit
  4. 28 Oct, 2018 1 commit
  5. 27 Oct, 2018 1 commit
  6. 26 Oct, 2018 1 commit
  7. 24 Oct, 2018 1 commit
  8. 22 Oct, 2018 1 commit
  9. 15 Oct, 2018 3 commits
  10. 14 Oct, 2018 1 commit
  11. 06 Oct, 2018 3 commits
  12. 04 Oct, 2018 1 commit
  13. 03 Oct, 2018 2 commits
  14. 26 Sep, 2018 1 commit
  15. 23 Sep, 2018 2 commits
    • Oscar Shrimpton's avatar
      networks: Add charset field to RusNet servers · 79d61e4e
      Oscar Shrimpton authored
      This fixes garbled characters when connecting to RusNet.
      
      #43
      79d61e4e
    • Oscar Shrimpton's avatar
      networks: Add optional charset field to servers · 28855f95
      Oscar Shrimpton authored
      Not all networks use UTF-8, so any input and output requires conversion
      to avoid garbled characters. Telepathy-idle handles that transparently,
      provided the correct 'charset' account property is specified.
      
      For predefined networks, we can simply pass on the option if the network
      data specifies it. We'll have to see whether it is worth exposing this
      also in the UI and thus supporting custom networks as well.
      
      #43
      28855f95
  16. 11 Sep, 2018 2 commits
    • Florian Müllner's avatar
      build: Only look for js60 for syntax checks · 009234e7
      Florian Müllner authored
      We have a hard dependency on a gjs version that is based on mozjs60,
      so checking for mozjs52's shell isn't really useful.
      
      #76
      009234e7
    • Florian Müllner's avatar
      build: Require current gjs · 27b691a0
      Florian Müllner authored
      There have been several changes this cycle that require the last stable
      gjs release - debugger support, using Uint8Array for raw data - which
      means we neither compile nor run with older releases.
      
      Make this explicit by requesting an appropriate gjs version.
      
      #76
      27b691a0
  17. 09 Sep, 2018 1 commit
  18. 04 Sep, 2018 4 commits
    • Florian Müllner's avatar
      app: Handle initially incorrect NetworkMonitor state · f7583cba
      Florian Müllner authored
      The portal implementation now fetches the initial state asynchronously,
      which means that "offline" can now either mean "offline" or a newly
      initialized singleton that hasn't fetched its state yet.
      
      Address this by tracking whether the state is valid, and wait for a
      ::network-changed signal otherwise. In particular this fixes cutting
      off existing connections on startup due to an incorrect offline state.
      
      !68
      f7583cba
    • Florian Müllner's avatar
      flatpak: Drop workarounds · 9c3e431e
      Florian Müllner authored
      The first issue was fixed in gjs and is no longer needed.
      
      The second issue has been partially addressed in that the portal
      will now fetch the initial state, albeit asynchronously and thus
      with a small delay. This is unfortunately going to stay with us,
      so we'll need to properly address this in master instead of adding
      a partial workaround in the flatpak.
      
      !68
      9c3e431e
    • Florian Müllner's avatar
      Bump version to 3.30.0 · 272912ac
      Florian Müllner authored
      Update NEWS.
      272912ac
    • Florian Müllner's avatar
      flatpak: Request write access to logs · be50eeec
      Florian Müllner authored
      We only need read access if the telepathy-logger service is running
      in the host session, but as we nowadays run our own bunlded version
      if necessary, it's possible that we need write access as well.
      be50eeec
  19. 03 Sep, 2018 1 commit
  20. 02 Sep, 2018 2 commits
  21. 01 Sep, 2018 2 commits
  22. 31 Aug, 2018 1 commit