<freemangordon>
if you look at what it does, on n900 Russian is a kind of hack (according to my limited knowledge on how keymaps work)
<freemangordon>
but again, that's not related to gtk
<freemangordon>
for gtk3 we obviously need IM plugin
<bencoh>
I'm about to say something silly, but what about leveraging ibus?
<bencoh>
and add a (custom?) touch-friendly virtual keyboard to ibus?
<bencoh>
it would work pretty much everywhere, and allow changing the hw keyboard layout through ibus as well
<freemangordon>
how we will show it on edit field entered?
<bencoh>
hm?
<bencoh>
you're basically asking if ibus can make it pop upon clicking a text field?
<freemangordon>
mhm
<bencoh>
no idea
<freemangordon>
forgive my ignorance
<bencoh>
I dunno either
<bencoh>
:)
<freemangordon>
I don;t really know how all this is supposed to work
<freemangordon>
(ibus)
<Wizzup>
I think it would be better to improve him first
<Wizzup>
h-i-m that is
<freemangordon>
right :)
<bencoh>
I usually ibus on various computers, both for hw layout (latin and non-latin) and semi-virtual input (like japanese / anthy)
<bencoh>
and the anthy module has some kind of UI
<freemangordon>
bencoh: and you have a window with that kbd somewhere all the time, no?
<bencoh>
for japanese? no, basically you change the input mode, start typing, and it changes your input on-the-fly, and allow you to choose the correct input (hiragana/katakana/kanji, japanese stuff)
<freemangordon>
I was talking about vkb
<bencoh>
vkb I haven't tried with ibus, that's what I think we would have to add
<freemangordon>
which brings us back to my initial question - how does it know when to pop :)
<freemangordon>
brb
<Wizzup>
freemangordon: if I can help with the gtk3 im, lmk
<Wizzup>
I'd love to get that in place some time soon, it's a big thing for us
<bencoh>
(and re: vkb implemented with ibus, looks like it's not really a thing, quite the opposite, they kinda expect 3rd-party non-ibus vkb to be used if anything)
<bencoh>
(someone proposed adding a virtual vs physical keyboard hint to ibus)
<bencoh>
(so just ignore my first question :) )
xmn has joined #maemo-leste
uvos has joined #maemo-leste
<uvos>
raising vkb on field click in all toolkits is prosible via at-spi
norayr has left #maemo-leste [Error from remote client]
uvos has joined #maemo-leste
<uvos>
sphone dosent do video calls (and imo video calls should probubly be handed by a different application since the required ui is so different)
<uvos>
sphone dosent do multi party calls, atho it sorta dose, you can have any number of call objects at a time, and the ui will present a list of calls. really this is intended to support call holding, but nothing prevents a backend haveing multiple endpoints active this way in a conference style call
norayr has joined #maemo-leste
<bencoh>
uvos: "for instance clicking on a field will raise the vkb only once, after closing to vkb again you need to click somewhere else before you can raise it again on the same field" sounds good to me
<bencoh>
since one can always raise the vkb manually as well
<bencoh>
so user might want to select (copypaste) something from said field without vkb getting in the way
<uvos>
sure but that pr is still more of a proof of concept, there are a lot of things it still needs
<uvos>
atspi dose for instances allow you to get the content of an input field
<uvos>
and this would allow you to then edit in in him
<uvos>
but this is not supported
norayr has left #maemo-leste [Error from remote client]