UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Signal UT: Signal-Desktop for Ubuntu Touch

    Scheduled Pinned Locked Moved App Development
    41 Posts 9 Posters 1.5k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • pparentP Offline
        pparent @klh
        last edited by pparent

        @klh said in Signal UT: Signal-Desktop for Ubuntu Touch:

        @pparent iirc my immodules hack won't work for Wayland, and you won't get an onscreen keyboard in Mir 1.8 because it's missing all the IME protocols.

        I haven't looked at what electron-only features the signal-desktop app uses, but you could look into packaging Node.js and running the back-end parts there with a shim in WebEngine to communicate with that. Not trivial, but would give you near-perfect integration with the OS.

        Yes I had thought about this option, but I in reality want to remain as close as possible from original client, and keep a small set of patches. For these reasons:

        • 1°) Because Signal-Desktop needs regular updates, as old versions get outdated fast and are not anymore compatible with the protocol. A version of Signal-Desktop is valid for 3 months. So I don't want heavy hacks that will not port easily from one version to another. I need to be able to recompile newer versions without headaches.

        • 2°) Because I want to minimize the risk of security breach coming from Signal-Desktop customization.

        • 3°) I want to avoid that Signal project may not be happy about our client because of messing too much with their protocol/client.

        So If nothing is possible while keeping the binaries as is, I will stay with X until Mir2.x release.

        Can you confirm, that the keyboard with Wayland should be better with Mir2.x?

        Ps: I'm currently debuging and trying to patch the code of maliit-inputcontext-gtk, to try and solve the bugs we currently have with the keyboard with X.

        1 Reply Last reply Reply Quote 1
        • First post
          Last post