Kateryna Kostiuk authored 3 years ago and Andreas Traczyk committed 3 years ago

- add sparkle submodule
- add an option to enable sparkle
- modify entitlements
- cleanup Info.plist

Gitlab: #578
Change-Id: I7f562112a72a33e008ab316479fbaa68dc0e07f1

Kateryna Kostiuk authored 3 years ago and Kateryna Kostiuk committed 3 years ago

We do not need to verify if an app instance already running
on macOS, because it is done by default. Moreover, it causes a crash
on the macOS app with enabled hardened runtime.

Gitlab: #578
Change-Id: Ic8aa6a136d394372890ed4010f4a3c7ffa8e9233

+ Refactors some window management logic in LayoutManagar.qml.
+ Refactors app start to support both a minimized start and a start
  URI. The start URI should force visibility.
+ StartMinimized now starts the application in a closed-to-tray
  state, instead of a minimized state.
+ The close-to-tray feature now saves the previous windowed state.
+ InstanceManager handles URI transfer to secondary instances.

This commit does not implement URI handling. The original
implementation supported only calls via a user infohash as the URI
parameter. A new and flexible protocol should be defined to support
multiple Jami features.

Gitlab: #655
Change-Id: I2c47028930e4e9d7ccca94d9362545df14b98160

Add some registry keys and values for the URL protocol via the WiX
installer.

Gitlab: #655
Change-Id: Ibc857cfea2db4ff5a20ca3e71e057990527a4054

To coordinate the MSI installer with Jami's close-to-tray feature,
a custom action was used to kill QtWebEngineProcess and Jami, prior
to the file installation step. The close-to-tray feature makes it
so the only way to terminate the app is via the systray context
menu.

This patch harnesses the IPC mechanism used by the run-guard, and
adds a command-line option('--term') used to signal the secondary
process and provoke graceful termination.

The benefits are:
- the app can save data before closing
- system tray icons aren't left dangling after updates
- QtWebEngineProcess is guaranteed to be terminated during install

Gitlab: #654
Gitlab: #543
Change-Id: I79421eeab49c9ec0826010af99a364471bb81d1a

Andreas Traczyk authored 3 years ago and Sébastien Blin committed 3 years ago

Connect after initializing the settings manager pointer and
remove a slot by relaying the retranslate signal.

jami-project#1342
Change-Id: I446cfb15500929850a434280dada6785107f9e78

Components.onCompleted is not called after engine_->retranslate(),
causing the menu to not change. Doing a model for 4 buttons is
overkill, so just do the menu.

jami-project#1342

Change-Id: I412230cc2152948666e37fe11824ee347bf55644

Change-Id: Iac105da82fa010fbf19775bebee23b04480ba47f
GitLab: #546

Kateryna Kostiuk authored 3 years ago and Kateryna Kostiuk committed 3 years ago

Gitlab: #578
Change-Id: Iac2d6878600f56fda0b671a5f6317b3dd56065aa

Move installTranslator into the settings manager and add a settings
in the SystemSettings to be able to dynamically change the language
of jami-qt.

jami-project#1342

Change-Id: I4f720fa50d5e313356dbdf1b8acb4e98d74401e4

Change-Id: I65d2a3f3216421e7da780465d5f36232fad1aaad

+ Reduce listview caching' size by 50%
+ use sourceSize to compress images and speedup loading
+ use autoTransform: true to rotate images when needed

Change-Id: Idf1babdc73f43aa6a79b89428c25c5d06856c0ef
GitLab: #649

Andreas Traczyk authored 3 years ago and Sébastien Blin committed 3 years ago

The running instance may be ephemeral and end up discarded after being
checked by InstanceManager. In this case, we shouldn't initialize large
components.

Gitlab: #654
Change-Id: I30c7dcdba6a56ab3a1a84a9efd3424e266b6f6ce

Change-Id: I7b952fdb2cc0a35f089e75a24b11582c45b135f3

This reverts commit 0c1b1cd4.

Reason for revert: #658 (comment 33744)

Change-Id: I5bdacea0bd414fe270697566d08db20f279e9349

Change-Id: I00e3d5a29854ef52b6d5e7275ada40e99e496a1e

Andreas Traczyk authored 3 years ago and Sébastien Blin committed 3 years ago

Qt6 allows us to set the RHI backend, however QQuickWidget is only
supported when using OpenGL. QWebEngineView instantiation uses
QQuickWidget and isn't required as we wish to use the previewengine
in a headless mode. So it can just be based on QWebEnginePage.

Change-Id: If05ca5c89272704b54c29318803c8773984b087c

Change-Id: Icb9eb9dba00f57afb32f7f38c5c135427d783d1c

GitLab: #601
Change-Id: Ic1ed7d2b724a04281973e974a787a680fbd26387

Andreas Traczyk authored 3 years ago and Sébastien Blin committed 3 years ago

Gitlab: #653
Change-Id: I79130e60c7f6632736b6d41773cde7a33eaa1107

GitLab: #160
GitLab: #571
Change-Id: Ifc1a4183c614f4754df5b617067a433d1227dcdf

Save virtual desktop geometry and window visibility state settings
and set them for the application window when loading.

Gitlab: #604
Change-Id: I053716d9c7b5d23e1bd7f33a1c41aedefb6cf9c8

It's more useful than the welcome view

GitLab: #645
Change-Id: Icf79aaff5c2cd1d9faf8481ba20f68e7b095d8c1

Also fix a typo causing the icon in the context menu to not update

Change-Id: I8886b45afcc55a3c724494afa10fc125d218d14e

GitLab: #427
Change-Id: I73818240946ab7c42eb238c50ca0f38061ff13d9

In 64720224, a no-sandbox flag was
added because QtWebEngine can't load fonts on recent glibc. Source:
https://bugreports.qt.io/browse/QTBUG-92969
https://bugs.chromium.org/p/chromium/issues/detail?id=1164975

Now, we use Qt 6.2, so this flag should not be necessary.
So, we can finally close #442 without any dirty workaround.

GitLab: #442
Change-Id: I52835e40d37d2397a891415fd2b1dd8dd4048b8b

Remove legacy cruft and streamline logic.

Change-Id: Ia9d0ef9a621e01aac17facb3e94efb11cdb38b0d

The comment was incorrect (it check the fingerprint, not the alias)
and the condition was duplicated

Change-Id: I2b3a21de64797dc90abaaa452645d7b0e6183ac1

Amin Bandali authored 3 years ago and Sébastien Blin committed 3 years ago

* src/main.cpp (main): unset QT_STYLE_OVERRIDE.  Some distros, like
Zorin OS, set QT_STYLE_OVERRIDE to force a particular Qt style.
This has been fine with Qt5 even when using our own Qt package
which may not have that style/theme available.  However, with Qt6,
attempting to override to a nonexistent style seems to result in the
main window simply not showing.  So here we unset this variable, also
because jami-qt currently has the Material style hard-coded anyway.
https://bugreports.qt.io/browse/QTBUG-99889

Change-Id: Ic261b46baf79cf36491578ff969b398b95363c94

Change-Id: Ifabe388e6aa8140ad4e7b0e4bb2fbcd1f0a1bfe4

Change-Id: I0b847303199c295d98d3b2bc687452012486110a

This prevents clicks
Also, add Accessible element

GitLab: #601
Change-Id: Ic08d35d6e27bbdf0ec3b3eccdb5a07b5f105a777

Logic for fullscreen/windowed mode switching is scattered within
the main ApplicationWindow and other components. Ideally,
components that need to transition to fullscreen, can make a dumb
request to module in charge of making the necessary checks and
carrying out the mode change.

This patch introduces the LayoutManager used to isolate this logic.

Change-Id: I0e5b932617d2b88eda1533f25a5d55fc1c66c438

Remove all references to appWindow.isFullScreen and uses visibility
Store latest state to keep previous states when passing the call
in fullscreen or a media player. Fix also fullscreen's transition
on media messages

Change-Id: I1b141fc052aa607561275faf231504f48b3c49b8

Change-Id: I8eb66c1c3cddb3bf73b6784a9876dd9dc9c12481

Superposing a MouseArea and a hover in a child
component may cause focus problems.
This replaces MouseArea for a HoverHandler
in the participant moderator menu.

Change-Id: Ic4eb763c79f04198d3a2a2f24636fb2a09dca172
GitLab: #601

Sébastien Blin authored 3 years ago and Aline Gondim Santos committed 3 years ago

Change-Id: Ifa610f3a110c050e22b6a83c79c0a94644ee82e1

remove useless isFullscreen (visibility already stores this and
it's not possible to go from fullscreen to minimized anyway).
Also --minimized was ignored

GitLab: #413
Change-Id: I610f17ce7ae5b2852aae5b40dc504174fa657c2d

Change-Id: I36fb96db8e1404aa6963c6af3ae62c8945653e69

The textarea is still white in dark mode, so the text must be black

Change-Id: I6d475cfb920fcd9f3b51e6df01eba4d30a0bc675