Keyboard layouts for Jolla's Sailfish OS - Page 21 - maemo.org

Active Topics

The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 5 hrs, 59 mins ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 18 hrs ago
more...

Page 21 of 40

Thread Tools

Penguin	2014-03-11 , 22:51
Posts: 144 \| Thanked: 242 times \| Joined on Nov 2007 @ Finland	#201

If you want to hack autocaps and preedit off in your custom keyboard that can be done easily with few lines in layout QML file:

Code:

KeyboardLayout {
    // enables possibility to use own InputHandler,
    // disables autocaps and text prediction
    type: "custom"  
    Component.onCompleted: {
        // disable autocaps
        keyboard.autocaps = false 
    }
...
}

Value of property type can be actually anything which does not match to supported types.

Updated: bug fix to this instruction. Property type alone disables both text prediction and autocaps and enables usage of custom input handler. Do not use it unless you want to change input handler from default.

Update ; Ouch! I tried to disable to word prediction by changing value of read only property...

Last edited by Penguin; 2014-03-14 at 21:10.

Quote & Reply |

The Following User Says Thank You to Penguin For This Useful Post:
Schturman

	Schturman	2014-03-11 , 23:22
	Posts: 5,339 \| Thanked: 4,133 times \| Joined on Jan 2010 @ Israel	#202

OK, I did one test...
1. Created folder custom-he inside: /usr/share/maliit/plugins/com/jolla
2. Copied all .qml, .js and qmldir files from /usr/share/maliit/plugins/com/jolla to my folder custom-he
3. In he.qml I changed this line: import ".." to this one: import "../custom-he"
4. created custom-he.conf
5. edited KeyboardLayout.qml inside my folder custom-he to fit landscape and portrait mode.
5. restart maliit server.

The vkb loads ok, all work good without touching the original files EXCEPT arrows buttons

they just not work for some reasons...
Here is a content of the one arrows (LeftArrowKey.qml):

Code:

import QtQuick 2.0
import Sailfish.Silica 1.0

FunctionKey {
    icon.source: "image://theme/icon-l-left" + (pressed ? ("?" + Theme.highlightColor) : "")
    repeat: true
    key: Qt.Key_Left
    width: 52
}

2-3 hours tried different variations to get it work, but without succsess

Don't know how to get it work, or which file I need to edit...

__________________
Lausanne & Lyon de descente...
----------------
Schturman's home page
Schturman's repo on openrepos
RPM packaging directly on your Jolla phone.
Root & User SSH access to Jolla via WinSCP.
Root and User SSH access to Jolla via Nautilus on Linux PC.

Quote & Reply |

Penguin	2014-03-12 , 10:29
Posts: 144 \| Thanked: 242 times \| Joined on Nov 2007 @ Finland	#203

Check this http://talk.maemo.org/showpost.php?p...&postcount=197 to get arrow keys working. Forget those LeftArrowKey.qml, RightArrowKey.qml, etc and use that one file for all four arrow key directions. It has internal input handler for arrow keys and it works.

Forget also that modified InputHandler.qml which you have and which adds support for arrow keys. You can't modify only that file to get custom input handler, you need more files from system and that wouldn't be feasible compared to solution I made in CustomArrowKey.qml

That and few other files also available in Github Gist: https://gist.github.com/JanneEdelman/9496850

Edit: Changing stock KeyboardLayout.qml is typically an indication that something is wrong with your layout, not in KeyboardLayout.qml file which is very flexible if your layout file has been properly defined. Let me know what is the problem with stock KeyboardLayout.qml, I think we can solve it.

Last edited by Penguin; 2014-03-12 at 10:34.

Quote & Reply |

andreas1	2014-03-12 , 11:02
Posts: 197 \| Thanked: 65 times \| Joined on Jul 2011	#204

Mr Penguin, would you care to make an finnisk kb rpm with side-arrows?

__________________
N900->Galaxy S->N9->Jolla/Lumia625

Quote & Reply |

Penguin	2014-03-12 , 11:27
Posts: 144 \| Thanked: 242 times \| Joined on Nov 2007 @ Finland	#205

I am working to get custom keyboard framework implemented which would contain as many layouts as possible, preferrably separately installable and configurability to all layouts for spacebar row whether you want

possible deadkey on left or right side
arrow keys (left-right) or (left-right-up-down)
possible other alternatives

Quote & Reply |

The Following User Says Thank You to Penguin For This Useful Post:
Jordi

Penguin	2014-03-12 , 11:28
Posts: 144 \| Thanked: 242 times \| Joined on Nov 2007 @ Finland	#206

Originally Posted by RbN

French "ergonomic" layout fr-bépo : https://pad.lqdn.fr/p/sailfish-bepo

I got following feedback regarding this layout:

Thank you for this mapping;

But you are missing [W] key, so this mapping is not usable…
[W] key is next to [Z] (in place of []] on qwerty keyboard).

If there is not enough place on the first row, [W] should at least be accessible with a long press on [Z].
Another option could be to remove [È], which is already accessible with a long-press on [E].
You already did the same for [À] and [Ç]…

Edit: actually W was there behind V and now as own key too. Let's see how crowded users will feel this layout now. I kept previous version available just as backup option.

Last edited by Penguin; 2014-03-13 at 00:53.

Quote & Reply |

	Schturman	2014-03-13 , 10:46
	Posts: 5,339 \| Thanked: 4,133 times \| Joined on Jan 2010 @ Israel	#207

Originally Posted by Penguin

Check this http://talk.maemo.org/showpost.php?p...&postcount=197 to get arrow keys working. Forget those LeftArrowKey.qml, RightArrowKey.qml, etc and use that one file for all four arrow key directions. It has internal input handler for arrow keys and it works.

Forget also that modified InputHandler.qml which you have and which adds support for arrow keys. You can't modify only that file to get custom input handler, you need more files from system and that wouldn't be feasible compared to solution I made in CustomArrowKey.qml

That and few other files also available in Github Gist: https://gist.github.com/JanneEdelman/9496850

Edit: Changing stock KeyboardLayout.qml is typically an indication that something is wrong with your layout, not in KeyboardLayout.qml file which is very flexible if your layout file has been properly defined. Let me know what is the problem with stock KeyboardLayout.qml, I think we can solve it.

Ok, got it work with your arrowkey file

Thanks

P.S. But if user don't want to see all languages and want to see only 2-3, he still need replace layouts.conf file...

Quote & Reply |

rob_kouw	2014-03-14 , 11:40
Posts: 301 \| Thanked: 531 times \| Joined on Aug 2010 @ The Netherlands	#208

Normally I use an English keyboard, and I compiled an extended English keyboard with a few changes.
- For a Dutchman not all extended characters are necessary, so I skipped most of them.
- I added numbers 1 to 0 at the upper row. It requires some counting ("Now where is the 7 again?"), but it should be doable.
- I added characters ;\([{ to the comma and !?:/)]} to the dot.
- Some other useful characters were added to the L. I thought that would be the easiest to remember. These characters are -#%*_

The keyboard is in the zip under enx.qml. There is an extra enx.conf file with it, all normal English settings are being used.

Both to be copied as instructed earlier as root to

Code:

/usr/share/maliit/plugins/com/jolla/layouts

Followed by restarting the Maliit engine

Code:

killall maliit-server

And to be selected from the spacebar as EnglishX.

Thanks to Penguin for helping me along the way.

Attached Images

Attached Files

enx.zip (1,022 Bytes, 66 views)

__________________
Palm Treo -> N900 -> N9 -> Jolla -> SailfishX -> XA2
Developer mode novice, and enjoying it

Last edited by rob_kouw; 2014-03-14 at 11:45.

Quote & Reply |

The Following User Says Thank You to rob_kouw For This Useful Post:
Bundyo

Penguin	2014-03-14 , 18:02
Posts: 144 \| Thanked: 242 times \| Joined on Nov 2007 @ Finland	#209

Very nice ideas for custom keyboards. I like!

Quote & Reply |

Penguin	2014-03-14 , 18:21
Posts: 144 \| Thanked: 242 times \| Joined on Nov 2007 @ Finland	#210

Originally Posted by Schturman

But if user don't want to see all languages and want to see only 2-3, he still need replace layouts.conf file...

Actually only once. We can also customize language selector, may be even layout vector storing all layouts, although that will require custom version of all stock languages wanted too, but thats what you have done now anyway.

Unless someone else will deepdive into this I will look this matter after next Sailfish update (or may be this night, who knows what mad scientist will do