I think it never did work, I posted a complaint early in this thread IIRC

I am curious whether you could narrow down the issues you have with the XML layout files?

The thing is, it will be tough at this point to fix any bugs in MeeGo Keyboard itself (well, you already knew this, but this is for extra clarity).

However, those same XML layout files that you have been modding away on *are* used by the fully open Maliit Keyboard (open meaning: not only do you get to see the code but we will also accept your patches). So we *can* fix just about everything regarding the layout files, if we use Maliit Keyboard as a baseline.

And with a bit of extra effort, we could backport your patches so that Maliit Keyboard *would* actually run on the N9.

Now, the Maliit Keyboard still hasnt got the same quality and polish as the MeeGo Keyboard, it also doesn't look as good (but hey, perhaps we can re-use the MeeGo graphic assets on the N9). So it will require some effort, and I cannot realistically do all of it.

But also I want to point out that, if you help with the Maliit Keyboard, then that's also your chance to finally get Xt9 working on the N9</teaser>

understand, it was not a bug. in PR1.1 it wa sall working perfectly fine from our point. our ALPHANUMERIC keyboard were working perfectly fine. but we do not know what exactly was changed in PR1.2 to not alow "extended labels" on "cycleset" buttons, and also that symbols page has different number of buttons in row.

so you think this will be resolved with using maliit as base for our XMLs?

XT9 is already integrated in N9, just nobody can use it for alphanumeric.

Xt9 + alphanumeric VKB was working in PR 1.1 (meaning, both together)? Hm, that would be interesting news to me, I must have missed something important then.

no, was not working. i just know XT9 is in system, just not usable with alphanumeric.

Alright, I am starting to understand the issues. On why cycle keys + extended labels broke in PR 1.2: cycle keys was a "hidden" feature, which was never used by any official VKB layout. Extended labels, OTOH, were heavily used in almost all layout files. To my knowledge, there was no test case at all that would have covered the cycle keys feature … so it probably broke when we fixed some issues with the extended labels attribute. Sorry for that :-/

The more I think about, I think we (as in: the text input method team in Harmattan) did a huge mistake by not distributing the MeeGo Keyboard through the Nokia store. I mean, it made perfect sense to have the input method framework being handled as a system component (meaning: you cannot update it in any other way but through a system update), but the actual keyboard plugin should have been updated through Nokia store … and then it would actually have paid off that the MeeGo Keyboard source code is publicly available. Gah, hindsight 20/20 …

Mikhas, can this be changed maybe for PR1.3 (or, i know it is already testing), or next update? or why not to make update just only for that one thing...

or even, can we somehow find out how to bring back support for extended labels on CYCLESET? understand, it does not have to be official solution just for community, with root right, inception or all we have here we can take care of distributuin of solution. thanks.

Regarding CSS and styling: I simplified it *a lot* for the Maliit Keyboard (never been happy with the way MeeGo Keyboard styling turned out in the end, even though I was responsible for most of its complexity …), take a look at: https://gitorious.org/maliit/maliit-...s/nokia-n9.ini or https://gitorious.org/maliit/maliit-...ended-keys.ini

I heavily doubt that anything VKB-related will be fixed in any future OS update :-(

Well, how to put it best …
MeeGo Keyboard = dead
Maliit Keyboard = possibly bright future

I cannot tell too much at this point, because nothing is confirmed yet. But the great thing about Maliit Keyboard: It will not only be available for Harmattan, but also other platforms, perhaps even come pre-installed! That's why I have a huge interest to move any feature development towards Maliit Keyboard and let MeeGo Keyboard die. Also, there is that fully open bugtracker, no corporate nonsense there, promised:
https://bugs.maliit.org/buglist.cgi?...--&list_id=480

And it'll be more fun for you guys too, because the Maliit Keyboard codebase is a lot smaller than MeeGo Keyboard (by a factor of 10 or so), and Maliit Keyboard will work with Qt 5, too (no Harmattan dependencies, either).

OMG, this must be the longest title on any forum in the world