Replace Floofchat with ArmoredChat

[Armored-Dragon]

Replace Floofchat with a smaller application using written in QML.

Compatibility

This version of Armored Chat is not compatible with Floofchat. Armored Chat is still compatible with notificationCore.js.

Linked issues and pulls

Merge with https://github.com/overte-org/community-apps/pull/79. Part of #886. Closes #898 as complete. Closes #778 as irrelevant. Closes #922 as irrelevant. Closes #975 as irrelevant.

Todo:

• [x] Embedding
  • Handle link embeds
  • (Potentially) handle special embeds like YouTube and GitHub
• Selective auto-scroll
  • Prevent scrolling to newest chat message if the view is not near the bottom.
• [x] Settings
  • Clear history
  • Set maximum amount of saved messages
  • Toggle external window
  • [x] Docs
  • [x] Quick-Message bar (related #975)

[Armored-Dragon]

Interesting note: When testing this application I ran into seemingly random variations in the way dates are displayed. The intended way for dates to be displayed, as an example, is [ HH:MM:SS - Month Day, Year] or for today [ 13:10:25 - May 22, 2024]. This is the outcome of the date when executing the application though Steam. I use Steam as a launcher by adding the .appimage as a non Steam game.

After you submit a new message, the date will display as a different format.

When executing the very same executable in a terminal, the dates come out differently. This is the result of sending a new message.

I am not certian on the cause of this yet, but the code for creating the dates are idendical. If nothing else, please keep this in mind when reviewing this pull request.

[Armored-Dragon]

Despite my best efforts I have not found a reliable way to impliment "Selective auto-scroll".

For reviewers:

• Please test link opening in external window. I am unable to test this myself due to #500.
• Ensure dates formats are consistant. See: https://github.com/overte-org/overte/pull/961#issuecomment-2124047419
• Are defaults acceptable?
• Qt RichText is being used. If there is a tag that could negativly impacts the user experiance, please report.
• Are there any missing features that should be included?
• Are the linked issues correct?

[Armored-Dragon]

I just remembered about the floating chat bar in referenced in #975. An alternative is not currently implimented. I will create an equivelent when I start working on this again.

[Armored-Dragon]

Here is a list of tasks to do gathered from QA testing: ~Store messages in private settings to prevent eavesdropping.

• https://github.com/overte-org/overte/issues/1009~
  • [x] VR Keyboard does not show up.
  • [x] Scrolling to the bottom goes too far sometimes.

[ksuprynowicz]

VR keyboard does not show up

[ksuprynowicz]

It also looks like the messages from Floof Chat are not being received. We could drop Floof Chat compatibility later, but having no compatibility in initial version will cause problems since some people will be running stable version and some will be running development builds. Version of Armored Chat from Community Apps is compatible with Floof Chat.

[Armored-Dragon]

I've restored compatibility with floofchat in 192d80a, I'm hoping the the future we can toss the compatibility. Maybe after the next release?

[ksuprynowicz]

Maybe after the next release?

Sure! That's a very good idea

[Armored-Dragon]

After some testing I believe it is not directly possible to invoke the VR Keyboard on overlays made using solely QML. I have gone so far as to force display the VR keyboard using Keyboard.raised by setting the value to true (related wiki). This method also did not work. Based on what I have seen the keyboard only (properly) displays on webengine based windows. If anyone has any more ideas I am open to suggestions.

In the mean time this should not be merged until the VR keyboard can get properly invoked.

[ksuprynowicz]

I will try to look at VR keyboard issue this weekend