05:55 <gnarface> if Guest224 comes back, tell them about my hypothesis that it probably works like debian since it's based on devuan. try checking out "dpkg-reconfigure keyboard-configuration" (i could be wrong about this, just a guess)

05:56 <gnarface> if it's handled like debian and devuan then i believe that whatever configuration file it's stored in is also touched by that command

08:26 <Guest224> gnarface: thanks for hints, that make me look again some commands and "setxkbmap -query" gave some answer to check.

08:30 <Guest224> by default Maemo Leste use PC105, US layout with Pinephone Keyboard. With rules: evdev

08:32 <Guest224> So that will be my starting point.

09:11 <Guest224> oh..I might gave up..it is impressive how complex linux is these days in simple things like keyboard.

09:59 <Guest224> maybe should merge some of her works about Pinephone Keyboard to Leste: https://codeberg.org/aLilyBit/ppkb-layouts

14:44 <arno11> sicelo: i've got sphone keypad working in landscape :)

15:29 <uvos__> arno11: its probubly more usefull to tag me instead of sicelo wrt sphone, since i am its author. wdym got the keypad working in landscape? the keypad is hidden on purpose when the horizontal size of the window is below a certain threshold, to avoid makeing the buttons to small to use

15:29 <uvos__> did you write some code to make the layout adaptive? ie move the keypad to the right next to the other buttons when the window size falls below the threshold

15:30 <uvos__> *...hidden on purpose when the vetiical size of the window...

15:33 <arno11> uvos: i made btns smaller, and replace keypad by backend_combo in horizontal size option in code

15:34 <uvos__> i think it would be better to move them to the right of the other buttons instead, but maybe send a screenshot of what you did

15:36 <arno11> yes maybe better

15:37 <arno11> i'll send a screenshot a bit later.

15:51 <sicelo> arno11, you mean the vkb? anyway i do feel, as you also alluded, that the backend and cancel buttons belong elsewhere. I've raised the idea before, but it was rejected

15:58 <sicelo> oh, you mean the T9 :-)

16:07 <arno11> uvos: https://ibb.co/D9sCkzZ

16:08 <arno11> this way the keypad is usable IMO

16:10 <arno11> sicelo: yes the t9

16:13 <arno11> just modifying 8 lines of code

16:13 <arno11> sorry 5

16:24 <Wizzup> top

16:25 <Wizzup> oops

16:57 <sicelo> cool

16:58 <sicelo> but yes, adding this as extra columns instead of rows would be more ideal, i think :-)

17:02 <arno11> agreed

17:02 <arno11> i'll try this evening i think

17:05 <sicelo> what did you do about Backend button?

17:06 <arno11> there is an option in code to hide keypad if height < 500px

17:07 <arno11> so i replaced keypad by backend_combo...

17:08 <arno11> this way combo is hidden and keypad shown instead

17:08 <sicelo> i think the backend button should go to settings ... but yeah, you need to discuss with uvos

17:08 <arno11> yes

17:08 <sicelo> mmm, maybe, if having it in settings is undesirable, it could go on the first row ... maybe to left of the number entry widget

17:09 <sicelo> the for the remainder, it could be 4 rows ...

17:10 <sicelo> column 1, from top to bottom, would have, Contacts, Recent, Call, Cancel

17:10 <sicelo> then T9 will be columns 2-4

17:10 <arno11> why not

17:10 <sicelo> why not ... what?

17:11 <arno11> lol i mean contact, recent, call , cancel

17:12 <sicelo> not sure i understand the question :-)

17:12 <arno11> it was not question, i just agree

17:12 <arno11> :)

17:12 <sicelo> but yeah, i think something like the above idea can help keep buttons somewhat big, for fat fingers :-p

17:13 <arno11> yes

17:14 <arno11> (back in 15min)

22:24 <uvos> the backend button should def not go into settings imo

22:24 <uvos> its maybe sligtly missnamed

22:25 <uvos> it really means potocoll, and the hope is that you will eventually be able to choose gsm/voip/skype/telegram/etc here to place your call

22:25 <uvos> settings is, imo, to to rigid for something that is expected to possibly vary with every call

22:27 <uvos> also there is sufficent room

22:27 <uvos> there is no need to get rid of anything

22:28 <uvos> so i would do this:

22:30 <uvos> ========== <

22:30 <uvos> ============= < | 1 | 2 | 3

22:30 <uvos> contacts | 4 | 5 | 6

22:30 <uvos> recent | 7 | 8 | 9

22:30 <uvos> call cancle | * | 0 | #

22:31 <uvos> or maybe flipped

22:31 <uvos> | 1 | 2 | 3 | ============= <

22:31 <uvos> | 4 | 5 | 6 | contacts

22:31 <uvos> | 7 | 8 | 9 | recent

22:31 <uvos> | * | 0 | # | call cancle

22:32 <uvos> since call and contacts are going to be the most used buttons, and should be closest to the thumb