<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><blockquote type="cite"><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);">Dietmar Schwertberger, if </span></font>SailfishOS didnt give U a satisfaction, U can try this <a href="https://maruos.com/#/">https://maruos.com/#/</a></blockquote></div><div><p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><br></p></div><div><br>Dňa 6. 3. 2018 o 22:45 užívateľ <a href="mailto:devel-request@lists.sailfishos.org">devel-request@lists.sailfishos.org</a> napísal:<br><br></div><blockquote type="cite"><div><span>Send Devel mailing list submissions to</span><br><span> <a href="mailto:devel@lists.sailfishos.org">devel@lists.sailfishos.org</a></span><br><span></span><br><span>To subscribe or unsubscribe via the World Wide Web, visit</span><br><span> <a href="https://lists.sailfishos.org/cgi-bin/mailman/listinfo/devel">https://lists.sailfishos.org/cgi-bin/mailman/listinfo/devel</a></span><br><span>or, via email, send a message with subject or body 'help' to</span><br><span> <a href="mailto:devel-request@lists.sailfishos.org">devel-request@lists.sailfishos.org</a></span><br><span></span><br><span>You can reach the person managing the list at</span><br><span> <a href="mailto:devel-owner@lists.sailfishos.org">devel-owner@lists.sailfishos.org</a></span><br><span></span><br><span>When replying, please edit your Subject line so it is more specific</span><br><span>than "Re: Contents of Devel digest..."</span><br><span></span><br><span></span><br><span>Today's Topics:</span><br><span></span><br><span> 1. Re: Linux desktop software on Sailfish? (Pekka Vuorela)</span><br><span> 2. Re: hunspell (rinigus)</span><br><span> 3. Re: keyboard development (Leif-Jöran Olsson)</span><br><span> 4. Re: keyboard development (rinigus)</span><br><span> 5. Re: Linux desktop software on Sailfish? (Dietmar Schwertberger)</span><br><span></span><br><span></span><br><span>----------------------------------------------------------------------</span><br><span></span><br><span>Message: 1</span><br><span>Date: Tue, 06 Mar 2018 16:48:26 +0200</span><br><span>From: Pekka Vuorela <<a href="mailto:pekka.vuorela@jolla.com">pekka.vuorela@jolla.com</a>></span><br><span>To: Sailfish OS Developers <<a href="mailto:devel@lists.sailfishos.org">devel@lists.sailfishos.org</a>></span><br><span>Subject: Re: [SailfishDevel] Linux desktop software on Sailfish?</span><br><span>Message-ID: <<a href="mailto:1520347706.8019.32.camel@jolla.com">1520347706.8019.32.camel@jolla.com</a>></span><br><span>Content-Type: text/plain; charset="UTF-8"</span><br><span></span><br><span>On Thu, 2018-03-01 at 23:14 +0100, Dietmar Schwertberger wrote:</span><br><blockquote type="cite"><span>Hi!</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>In the last days Planet Computers started shipping the Gemini PDA</span><br></blockquote><blockquote type="cite"><span>which </span><br></blockquote><blockquote type="cite"><span>has Android installed by default but features a Linux dual boot</span><br></blockquote><blockquote type="cite"><span>option.</span><br></blockquote><blockquote type="cite"><span>There will be an option to install Sailfish OS as the Linux OS.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>For most buyers the motivation to buy the device is not just Android </span><br></blockquote><blockquote type="cite"><span>with a keyboard but the option to use it as a productivity device, </span><br></blockquote><blockquote type="cite"><span>including office applications and development software.</span><br></blockquote><blockquote type="cite"><span>Currently the only option for this usage scenario is Debian. Ubuntu </span><br></blockquote><blockquote type="cite"><span>should follow soon.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Is there a realistic option to have e.g. gtk and a Linux desktop on </span><br></blockquote><blockquote type="cite"><span>Sailfish OS?</span><br></blockquote><blockquote type="cite"><span>A Sailfish OS with Android compatibility and Linux productivity </span><br></blockquote><blockquote type="cite"><span>applications would be the perfect OS for the Gemini PDA.</span><br></blockquote><span></span><br><span>Linux desktop and Sailfish OS are kind of mutually exclusive things in</span><br><span>the sense the Sailfish provides a home screen, i.e. "desktop".</span><br><span></span><br><span>Gkt+ applications could perhaps be possible, but not necessarily an API</span><br><span>that is going to get official support. Also desktop applications and</span><br><span>widget sets don't likely work nicely on a small mobile device as they</span><br><span>have not been commonly developed with finger usability in mind.</span><br><span></span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Message: 2</span><br><span>Date: Tue, 6 Mar 2018 17:09:28 +0200</span><br><span>From: rinigus <<a href="mailto:rinigus.git@gmail.com">rinigus.git@gmail.com</a>></span><br><span>To: Sailfish OS Developers <<a href="mailto:devel@lists.sailfishos.org">devel@lists.sailfishos.org</a>></span><br><span>Subject: Re: [SailfishDevel] hunspell</span><br><span>Message-ID:</span><br><span> <<a href="mailto:CA+4hNMGh_w-2ysG2WZ0XajftRyuctz=sTcb-UHHWM+5gAXtGTA@mail.gmail.com">CA+4hNMGh_w-2ysG2WZ0XajftRyuctz=sTcb-UHHWM+5gAXtGTA@mail.gmail.com</a>></span><br><span>Content-Type: text/plain; charset="utf-8"</span><br><span></span><br><span>Yes, I did and I followed the new standard by using git submodules.</span><br><span>Packaging is somewhat different from the previous version in a sense that</span><br><span>it adds static library in devel package. This would allow developers to</span><br><span>choose whether to link statically or dynamically in response to the current</span><br><span>Harbour rules.</span><br><span></span><br><span>Rinigus</span><br><span></span><br><span>On Tue, Mar 6, 2018 at 3:41 PM, Pekka Vuorela <<a href="mailto:pekka.vuorela@jolla.com">pekka.vuorela@jolla.com</a>></span><br><span>wrote:</span><br><span></span><br><blockquote type="cite"><span>On Tue, 2018-02-27 at 15:35 +0200, rinigus wrote:</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>For those who are interested in up-to-date hunspell, I have packaged</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>it under <a href="https://github.com/rinigus/pkg-hunspell">https://github.com/rinigus/pkg-hunspell</a> with the builds</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>available at <a href="https://build.merproject.org/package/show/home:rinigus:k">https://build.merproject.org/package/show/home:rinigus:k</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>eyboard/hunspell .</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Packaging script is based on <a href="https://git.merproject.org/mer-core/huns">https://git.merproject.org/mer-core/huns</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>pell with the further split of development and tools packages for</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>hunspell. That allows to get hunspell as a static library and build</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>against it.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I wonder whether anyone has packaged more recent version of</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>hunspell than the one available at <a href="https://git.merproject.org/mer-c">https://git.merproject.org/mer-c</a></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>ore/hunspell and on our devices?</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Also, it looks like mer repo contains source dump of hunspell. If I</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>remember other repos correctly, it seems to be the way for other</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>packages as well. Any reasons for preferring such model instead of</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>git submodules? Looks to be more difficult to update it to the</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>current version.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Looks like you made a PR for the update. Nice, we'll look into that.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>For the record, some older packages are having source code dumps. Those</span><br></blockquote><blockquote type="cite"><span>have been gradually migrated for git submodule setup for easier</span><br></blockquote><blockquote type="cite"><span>maintenance and usage.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span><a href="http://SailfishOS.org">SailfishOS.org</a> Devel mailing list</span><br></blockquote><blockquote type="cite"><span>To unsubscribe, please send a mail to devel-unsubscribe@lists.</span><br></blockquote><blockquote type="cite"><span><a href="http://sailfishos.org">sailfishos.org</a></span><br></blockquote><span>-------------- next part --------------</span><br><span>An HTML attachment was scrubbed...</span><br><span>URL: <<a href="https://lists.sailfishos.org/pipermail/devel/attachments/20180306/a1525553/attachment-0001.html">https://lists.sailfishos.org/pipermail/devel/attachments/20180306/a1525553/attachment-0001.html</a>></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Message: 3</span><br><span>Date: Tue, 6 Mar 2018 17:51:40 +0100</span><br><span>From: Leif-Jöran Olsson <<a href="mailto:ellefj@gmail.com">ellefj@gmail.com</a>></span><br><span>To: Sailfish OS Developers <<a href="mailto:devel@lists.sailfishos.org">devel@lists.sailfishos.org</a>>, Mike Sheldon</span><br><span> <<a href="mailto:mike@mikeasoft.com">mike@mikeasoft.com</a>></span><br><span>Subject: Re: [SailfishDevel] keyboard development</span><br><span>Message-ID: <<a href="mailto:c7d0e1b5-4d01-aeb4-15f8-9f11c86cce80@gmail.com">c7d0e1b5-4d01-aeb4-15f8-9f11c86cce80@gmail.com</a>></span><br><span>Content-Type: text/plain; charset=utf-8</span><br><span></span><br><span>-----BEGIN PGP SIGNED MESSAGE-----</span><br><span>Hash: SHA1</span><br><span></span><br><span>Den 2018-03-06 kl. 12:59, skrev Mike Sheldon:</span><br><blockquote type="cite"><span>Hi Rinigus,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On Mon, Mar 5, 2018 at 8:23 PM, rinigus <<a href="mailto:rinigus.git@gmail.com">rinigus.git@gmail.com</a></span><br></blockquote><blockquote type="cite"><span><<a href="mailto:rinigus.git@gmail.com">mailto:rinigus.git@gmail.com</a>>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> As I mentioned in the mail, we have extended Presage with the new</span><br></blockquote><blockquote type="cite"><span> language model that maybe of interest to your keyboard</span><br></blockquote><blockquote type="cite"><span> implementation as well. Speedup is of the order of 10x, maybe more</span><br></blockquote><blockquote type="cite"><span> in addition to the significant reduction on database size. We are</span><br></blockquote><blockquote type="cite"><span> discussing also Unicode support by Presage to properly support</span><br></blockquote><blockquote type="cite"><span> case-insensitive n-gram search, not via `tolower` as done now. It</span><br></blockquote><blockquote type="cite"><span> will probably change the database format to implement properly, bu</span><br></blockquote><span>t</span><br><blockquote type="cite"><span> then should stabilize. If there is anyone from UBPorts interested </span><br></blockquote><span>in</span><br><blockquote type="cite"><span> joining Presage development - we would be happy to get any help :)</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>That's interesting, you might also be interested in taking a look at m</span><br></blockquote><span>y</span><br><blockquote type="cite"><span>(unfinished) Skeyer branch: </span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span><a href="https://code.launchpad.net/~michael-sheldon/ubuntu-keyboard/skeyer-pro">https://code.launchpad.net/~michael-sheldon/ubuntu-keyboard/skeyer-pro</a></span><br></blockquote><span>totype</span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>That uses saidinesh's libskeyer to provide auto-correction (and</span><br></blockquote><blockquote type="cite"><span>eventually swipe style input), this provides spatially aware correctio</span><br></blockquote><span>ns</span><br><blockquote type="cite"><span>(i.e. it knows that 'b' is next to 'n' on an English keyboard so would</span><br></blockquote><blockquote type="cite"><span>suggest 'and' as a correction for 'abd' instead of Presage's predictio</span><br></blockquote><span>n</span><br><blockquote type="cite"><span>of 'abdicate'). I think the strongest approach would involve a</span><br></blockquote><blockquote type="cite"><span>combination of the two, using Skeyer for correction and Presage for</span><br></blockquote><blockquote type="cite"><span>prediction.</span><br></blockquote><span></span><br><span>Just a quick note that for presage the hunspell predictor provide</span><br><span>basically the correction functionality. But I see no problem adding</span><br><span>libskeyer as a predictor too in contrast to have them in another loose</span><br><span>combination of predictor and corrector.</span><br><span></span><br><span>ljo</span><br><span></span><br><blockquote type="cite"><span> Few general questions though:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> * If I want to test the keyboard, is there VirtualBox (or some oth</span><br></blockquote><span>er</span><br><blockquote type="cite"><span> similar) emulator for Ubuntu Touch / UBPorts? </span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>As far as I'm aware there isn't a working emulator image, however you</span><br></blockquote><blockquote type="cite"><span>can run the Ubuntu Keyboard on a standard desktop system as well; afte</span><br></blockquote><span>r</span><br><blockquote type="cite"><span>compiling and installing the plugin as normal and running maliit-serve</span><br></blockquote><span>r</span><br><blockquote type="cite"><span>you can start any QT app with the environment variable</span><br></blockquote><blockquote type="cite"><span>'QT_IM_MODULE=maliitphablet' to invoke the keyboard.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> * Do you have some mailing list or some other means where we could</span><br></blockquote><blockquote type="cite"><span> discuss joint projects with UBPorts developers?</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>There's a pretty active Telegram group here: <a href="https://t.me/ubports">https://t.me/ubports</a> (I'm</span><br></blockquote><blockquote type="cite"><span>on there, but not very involved) and the UBPorts forums</span><br></blockquote><blockquote type="cite"><span>here: <a href="https://forums.ubports.com/">https://forums.ubports.com/</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> * If we would like to port UBPorts keyboard, would it mainly requi</span><br></blockquote><span>re</span><br><blockquote type="cite"><span> changes</span><br></blockquote><blockquote type="cite"><span> in <a href="https://github.com/ubports/keyboard-component/tree/master/qml">https://github.com/ubports/keyboard-component/tree/master/qml</a></span><br></blockquote><blockquote type="cite"><span> <<a href="https://github.com/ubports/keyboard-component/tree/master/qml">https://github.com/ubports/keyboard-component/tree/master/qml</a>> ,</span><br></blockquote><blockquote type="cite"><span> icons and schema. Or would you expect some other parts require</span><br></blockquote><blockquote type="cite"><span> adaptation? Just an estimate would be fine at this stage.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>From memory there shouldn't be too much that needs changing; most of t</span><br></blockquote><span>he</span><br><blockquote type="cite"><span>QML is standard QtQuick, there should only be a few things using the</span><br></blockquote><blockquote type="cite"><span>Ubuntu Components that'll need replacing, e.g. the language menu and</span><br></blockquote><blockquote type="cite"><span>anywhere that's using Ubuntu's grid units for sizing.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> I would expect that the keyboard performs its own tokenization to</span><br></blockquote><blockquote type="cite"><span> split between the text on the left and the last word that needs</span><br></blockquote><blockquote type="cite"><span> prediction. Later, when Presage is called, strings are put back</span><br></blockquote><blockquote type="cite"><span> together and Presage is splitting it to words again. Which, in</span><br></blockquote><blockquote type="cite"><span> addition to double effort, can be source of confusion if the split</span><br></blockquote><blockquote type="cite"><span> to words doesn't match. From the brief look into the code with the</span><br></blockquote><blockquote type="cite"><span> help of grep, it looks like tokens are split by spaces and few oth</span><br></blockquote><span>er</span><br><blockquote type="cite"><span> similar chars (\n) with the exception of plugins/ko. Do you happen</span><br></blockquote><blockquote type="cite"><span> to have some API that could be used to plugin different tokenizati</span><br></blockquote><span>on</span><br><blockquote type="cite"><span> library, same Presage for example?</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>As far as I recall our tokenization was pretty simple, we basically ju</span><br></blockquote><span>st</span><br><blockquote type="cite"><span>allowed each plugin to define a list of characters to tokenize on (so</span><br></blockquote><blockquote type="cite"><span>for example Chinese could tokenize on different characters from</span><br></blockquote><blockquote type="cite"><span>English), it probably wouldn't be difficult to replace that with</span><br></blockquote><blockquote type="cite"><span>tokenization performed by another library.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Hope that helps :)</span><br></blockquote><blockquote type="cite"><span> Mike</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> But before going into major porting of the keyboard, would be good</span><br></blockquote><blockquote type="cite"><span> to know what Jolla's plans are regarding their keyboard. They shou</span><br></blockquote><span>ld</span><br><blockquote type="cite"><span> be back in the office now after a great time in Spain, hopefully w</span><br></blockquote><span>e</span><br><blockquote type="cite"><span> can hear back. </span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> Best wishes,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> Rinigus</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> On Mon, Mar 5, 2018 at 4:18 PM, Mike Sheldon <<a href="mailto:mike@mikeasoft.com">mike@mikeasoft.com</a></span><br></blockquote><blockquote type="cite"><span> <<a href="mailto:mike@mikeasoft.com">mailto:mike@mikeasoft.com</a>>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> Hey Rinigus,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> I've been out of the Jolla ecosystem for a while (since my pho</span><br></blockquote><span>ne</span><br><blockquote type="cite"><span> was lost a couple of years ago), so can't say anything much</span><br></blockquote><blockquote type="cite"><span> about the Jolla keyboard; but I was the lead developer on the</span><br></blockquote><blockquote type="cite"><span> Ubuntu Keyboard at Canonical so am happy to answer any specifi</span><br></blockquote><span>c</span><br><blockquote type="cite"><span> questions you have about that.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> Cheers,</span><br></blockquote><blockquote type="cite"><span> Mike</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> On Wed, Feb 28, 2018 at 7:14 PM, rinigus <<a href="mailto:rinigus.git@gmail.co">rinigus.git@gmail.co</a></span><br></blockquote><span>m</span><br><blockquote type="cite"><span> <<a href="mailto:rinigus.git@gmail.com">mailto:rinigus.git@gmail.com</a>>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> Hi,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> I have a question regarding the longer term plans for</span><br></blockquote><blockquote type="cite"><span> keyboard development in SFOS. Namely, @martonmiklos has</span><br></blockquote><blockquote type="cite"><span> brought over Presage predictor to SFOS and already publish</span><br></blockquote><span>ed</span><br><blockquote type="cite"><span> keyboard using this library. I think its a great developme</span><br></blockquote><span>nt</span><br><blockquote type="cite"><span> and together with @ljo we have been helping @martonmiklos </span><br></blockquote><span>to</span><br><blockquote type="cite"><span> make this plugin better. Please note that below, I speak f</span><br></blockquote><span>or</span><br><blockquote type="cite"><span> myself and I haven't checked whether these questions even</span><br></blockquote><blockquote type="cite"><span> make sense with others.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> At present, the released plugin has been enhanced by makin</span><br></blockquote><span>g</span><br><blockquote type="cite"><span> it fast through using different language model storage/que</span><br></blockquote><span>ry</span><br><blockquote type="cite"><span> mechanism, using relatively small size of n-gram database</span><br></blockquote><blockquote type="cite"><span> (English 5MB, Estonian 10MB), made asynchronous to ensure</span><br></blockquote><blockquote type="cite"><span> that the user's input is not lagging behind, and just</span><br></blockquote><blockquote type="cite"><span> extended with Hunspell speller as an additional "predictor</span><br></blockquote><span>".</span><br><blockquote type="cite"><span> All is in the testing / bugfixing stage. In longer</span><br></blockquote><blockquote type="cite"><span> term, with the right effort, we could get very well workin</span><br></blockquote><span>g</span><br><blockquote type="cite"><span> open-source predictive engine and keyboard.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> I am trying to understand how the pieces fall together and</span><br></blockquote><span> I</span><br><blockquote type="cite"><span> am not sure 100% whether I do. I can see that SFOS uses</span><br></blockquote><blockquote type="cite"><span> proprietary jolla-keyboard and the developed Presage input</span><br></blockquote><blockquote type="cite"><span> handler extends it. Which is fine, but maybe we could go</span><br></blockquote><blockquote type="cite"><span> deeper and do better.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> From looking around, Maliit has adopted keyboard developed</span><br></blockquote><blockquote type="cite"><span> by Ubuntu Touch as a reference, corresponding Maliit</span><br></blockquote><blockquote type="cite"><span> repo <a href="https://github.com/maliit/keyboard">https://github.com/maliit/keyboard</a></span><br></blockquote><blockquote type="cite"><span> <<a href="https://github.com/maliit/keyboard">https://github.com/maliit/keyboard</a>> . In addition to</span><br></blockquote><blockquote type="cite"><span> UBPorts, the same keyboard is used by LuneOS. This design</span><br></blockquote><blockquote type="cite"><span> already supports Presage and Hunspell, also done in</span><br></blockquote><blockquote type="cite"><span> asynchronous manner as we are testing for SFOS now. It has</span><br></blockquote><blockquote type="cite"><span> support for quite a few number of languages, pinyin, and</span><br></blockquote><blockquote type="cite"><span> emoji. I do not know how this design compares to the</span><br></blockquote><blockquote type="cite"><span> internals of jolla-keyboard and maybe someone can share</span><br></blockquote><blockquote type="cite"><span> their knowledge regarding it. I would expect that it was</span><br></blockquote><blockquote type="cite"><span> developed on the top of Maliit available at the time of J1</span><br></blockquote><blockquote type="cite"><span> and kept as it is after that.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> Now, I do wonder what is the long term plan with the</span><br></blockquote><blockquote type="cite"><span> keyboard development? From the outside of Jolla, it seems </span><br></blockquote><span>to</span><br><blockquote type="cite"><span> me that it would be wise to join forces with the others an</span><br></blockquote><span>d</span><br><blockquote type="cite"><span> develop this component together. Each OS in question has</span><br></blockquote><blockquote type="cite"><span> their own styling, but that seems to be possible to apply </span><br></blockquote><span>on</span><br><blockquote type="cite"><span> top. </span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> Its not trivial to compile the latest Maliit on SFOS (they</span><br></blockquote><blockquote type="cite"><span> switched to CMake based builds and few cmake configs are</span><br></blockquote><blockquote type="cite"><span> missing in SFOS right now), but I expect that its possible</span><br></blockquote><blockquote type="cite"><span> with some effort. Just don't want to spend too much time i</span><br></blockquote><span>f</span><br><blockquote type="cite"><span> it's gonna be without any use.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> So, to summarize, I would like to hear what's an opinion o</span><br></blockquote><span>n</span><br><blockquote type="cite"><span> the raised issues by those who know. Would be great to kno</span><br></blockquote><span>w</span><br><blockquote type="cite"><span> plans and comparison of jolla-keyboard with the current</span><br></blockquote><blockquote type="cite"><span> Maliit UBPorts/LuneOS versions. </span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> Best wishes,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span> Rinigus</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><span></span><br><span></span><br><span>-----BEGIN PGP SIGNATURE-----</span><br><span></span><br><span>iF0EARECAB0WIQTZ3t2nVJPW4yk01pSFwiflpVc48gUCWp7HHAAKCRCFwiflpVc4</span><br><span>8jkYAJ9vp+SABobvEOEXNTGEVZHM5hqjYQCgrkUEOzr+krwBhjUX2W5Ym4WchWM=</span><br><span>=Fi9e</span><br><span>-----END PGP SIGNATURE-----</span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Message: 4</span><br><span>Date: Tue, 6 Mar 2018 22:41:05 +0200</span><br><span>From: rinigus <<a href="mailto:rinigus.git@gmail.com">rinigus.git@gmail.com</a>></span><br><span>To: Sailfish OS Developers <<a href="mailto:devel@lists.sailfishos.org">devel@lists.sailfishos.org</a>>, Mike Sheldon</span><br><span> <<a href="mailto:mike@mikeasoft.com">mike@mikeasoft.com</a>></span><br><span>Subject: Re: [SailfishDevel] keyboard development</span><br><span>Message-ID:</span><br><span> <<a href="mailto:CA+4hNMEKGjyomjkQtSohDe=XMa26W9V8DC_4GJqxgs6=MwoyfA@mail.gmail.com">CA+4hNMEKGjyomjkQtSohDe=XMa26W9V8DC_4GJqxgs6=MwoyfA@mail.gmail.com</a>></span><br><span>Content-Type: text/plain; charset="utf-8"</span><br><span></span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>That's interesting, you might also be interested in taking a look at my</span><br></blockquote><blockquote type="cite"><span>(unfinished) Skeyer branch:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span><a href="https://code.launchpad.net/~michael-sheldon/ubuntu-keyboard/">https://code.launchpad.net/~michael-sheldon/ubuntu-keyboard/</a></span><br></blockquote><blockquote type="cite"><span>skeyer-prototype</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>That uses saidinesh's libskeyer to provide auto-correction (and eventually</span><br></blockquote><blockquote type="cite"><span>swipe style input), this provides spatially aware corrections (i.e. it</span><br></blockquote><blockquote type="cite"><span>knows that 'b' is next to 'n' on an English keyboard so would suggest 'and'</span><br></blockquote><blockquote type="cite"><span>as a correction for 'abd' instead of Presage's prediction of 'abdicate'). I</span><br></blockquote><blockquote type="cite"><span>think the strongest approach would involve a combination of the two, using</span><br></blockquote><blockquote type="cite"><span>Skeyer for correction and Presage for prediction.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><span></span><br><span>Interesting, we'll surely think about it. On SFOS, we have OKboard that has</span><br><span>implementation of swipe style input, but its probably good to think about</span><br><span>using keyboard-aware correction. However, as @ljo described, we don't have</span><br><span>such issue with `abd` in the presage version that has hunspell added as a</span><br><span>dictionary predictor. It would depend on corpora used for training, but in</span><br><span>our case we get "bad", "and", "abd" as the three first suggestions.</span><br><span></span><br><span>Mike, thanks for the tips regarding the keyboard internals, they are very</span><br><span>helpful. I'll register at UBPorts forums to get into some discussions (not</span><br><span>using telegram).</span><br><span></span><br><span>Cheers,</span><br><span></span><br><span>Rinigus</span><br><span>-------------- next part --------------</span><br><span>An HTML attachment was scrubbed...</span><br><span>URL: <<a href="https://lists.sailfishos.org/pipermail/devel/attachments/20180306/d28c2815/attachment-0001.html">https://lists.sailfishos.org/pipermail/devel/attachments/20180306/d28c2815/attachment-0001.html</a>></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Message: 5</span><br><span>Date: Tue, 6 Mar 2018 22:43:16 +0100</span><br><span>From: Dietmar Schwertberger <<a href="mailto:maillist@schwertberger.de">maillist@schwertberger.de</a>></span><br><span>To: <a href="mailto:devel@lists.sailfishos.org">devel@lists.sailfishos.org</a></span><br><span>Subject: Re: [SailfishDevel] Linux desktop software on Sailfish?</span><br><span>Message-ID: <<a href="mailto:993fd2fc-0d3f-b3d6-f249-7f6681d11eeb@schwertberger.de">993fd2fc-0d3f-b3d6-f249-7f6681d11eeb@schwertberger.de</a>></span><br><span>Content-Type: text/plain; charset=utf-8; format=flowed</span><br><span></span><br><span>On 3/6/2018 3:48 PM, Pekka Vuorela wrote:</span><br><blockquote type="cite"><span>Linux desktop and Sailfish OS are kind of mutually exclusive things in</span><br></blockquote><blockquote type="cite"><span>the sense the Sailfish provides a home screen, i.e. "desktop".</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Gkt+ applications could perhaps be possible, but not necessarily an API</span><br></blockquote><blockquote type="cite"><span>that is going to get official support. Also desktop applications and</span><br></blockquote><blockquote type="cite"><span>widget sets don't likely work nicely on a small mobile device as they</span><br></blockquote><blockquote type="cite"><span>have not been commonly developed with finger usability in mind.</span><br></blockquote><span></span><br><span>Sure, but with a device like the Gemini PDA that is not really an issue </span><br><span>as it has a keyboard and also a mouse can be connected. So, keyboard </span><br><span>control can be used for most things, the screen size is not reduced by a </span><br><span>on-screen keyboard and for some applications where one really needs fine </span><br><span>control, a mouse can be connected. Also, external monitor and keyboard </span><br><span>may be connnected, so usage scenarios like Windows Continuum, Ubuntu </span><br><span>Convergence or Samsung DeX would be possible without additional effort.</span><br><span>On Maemo, the standard Qt widgets were perfectly integrated. With </span><br><span>Sailfish OS this is not gonna happen. That's clear, but not an issue </span><br><span>here as it would require adaption per application.</span><br><span>It would be sufficient to be able to build e.g. gtk applications and </span><br><span>start them full-screen. Things like drag&drop between windows would </span><br><span>obviously not work. The perfect solution would be a desktop running as </span><br><span>another full-screen showing all applications that are not full-screen.</span><br><span></span><br><span>Maemo had some application like word processor or spreadsheet. With </span><br><span>keyboard and stylus they were really usable. The keyboard contributed to </span><br><span>the usability more than the stylus. Without keyboard and stylus there's </span><br><span>no useful scenario...</span><br><span></span><br><span>Regards,</span><br><span></span><br><span>Dietmar</span><br><span></span><br><span></span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Subject: Digest Footer</span><br><span></span><br><span>_______________________________________________</span><br><span>Devel mailing list</span><br><span><a href="mailto:Devel@lists.sailfishos.org">Devel@lists.sailfishos.org</a></span><br><span><a href="https://lists.sailfishos.org/cgi-bin/mailman/listinfo/devel">https://lists.sailfishos.org/cgi-bin/mailman/listinfo/devel</a></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>End of Devel Digest, Vol 47, Issue 6</span><br><span>************************************</span><br></div></blockquote></body></html>