[Finished] keyboard Feature when editing text (1 Viewer)

[azzuro]

sorry @morpheus_xx
working on default skin, i mean this tamplate was generic for to be used inside all skin, without need to have each layout for each skins.

 

[morpheus_xx]

i mean this tamplate was generic for to be used inside all skin, without need to have each layout for each skins.

Could be worth to try removing the style from other skins and using the Default one. This could solve the missing feature and also could avoid the need to copy localized keyboards over to other skins.

Yes I understand, that's why I asket @ge2301 for checking if removing the copy styles would be an option to avoid this copy action.

 

[morpheus_xx]

@azzuro can you check this branch: GitHub - MediaPortal/MediaPortal-2 at REWORK_VirtualKeyboards
I have refactored all skins to use only the VirtualKeyboards from the SkinBase and have created a German layout.

It would be good if you could create the french version, but be careful when changing keys. I had following issues:

• Change "Content" attribute to new key
• Change "Command" attribute's parameter to new key
• Check all 4(!) keyboard styles: Normal, Shift, Alt Gr, Shift+Alt Gr (I only adjusted the first 3 ones for german though )

@ge2301 please check if the layouts and behavior in other skins is still as you intended.

All new keyboard layouts for other languages have to be only added to SkinBase plugin! Otherwise it would break the resource inheritance and localized keyboards are not available to other skins!

 

[azzuro]

@morpheus_xx i tried it, without sucess.
i'm not sure if providing keyboard for each language is the good solution.
what do you think for provide an extra button for switch between différent keyboard layout. like kodi.
http://www.xuum.com/blog/wp-content/uploads/2015/11/Screen-Shot-2015-11-16-at-11.06.32.png
i think it's more intuitive, and can be switched easily if missing characters on the default keyboard.

but the idea to keep one layout for all skin, very good solution.

Edit :
it work removed all files insides skinfolder.

PS : nobody know an software for copy/replace files from sources,and backup files present in targets but not exist in source folder ?

 

[morpheus_xx]

what do you think for provide an extra button for switch between différent keyboard layout. like kodi.

Hmm... if changes to the current approach are considered, I would do it more like the Android keyboards: the regular letters and numbers as default, the special characters on a 2nd/3rd table. The MP2 implementation is too much bound to physical keyboard (with the Shift, AltGr logic is too complicated for HTPC usage).

PS : nobody know an software for copy/replace files from sources,and backup files present in targets but not exist in source folder ?

You can use "robocopy" command for this. It has a switch "/MIR" (mirror) which also deletes extra files in target folder. Or just delete the "bin" folder once and do a solution rebuild, this is easier.

 

[azzuro]

You can use "robocopy" command for this. It has a switch "/MIR" (mirror) which also deletes extra files in target folder. Or just delete the "bin" folder once and do a solution rebuild, this is easier.

i found this
Directory Synchronize Pro (DirSync Pro)
it can backup files replaced ( can be useful for me, because i test on programfiles path. )

Now, i can say than your rework use the same layout on all skins.

 

[morpheus_xx]

@azzuro do you still work on french keyboard layout or did you completely dropped this idea? Anything I can support?

 

[azzuro]

@azzuro do you still work on french keyboard layout or did you completely dropped this idea? Anything I can support?

it's not dead, it's only than i need to understand the code of the layout. i'm a bit slow to integrate.
for now, i mapped to azerty the principal keyboard, need to understand, if i can move case position, for follow real hardware keyboard.

i will try to use this from kodi as base.
xbmc/french.xml at 8d4a5bba55638dfd0bdc5e7de34f3e5293f99933 · xbmc/xbmc · GitHub

 

[morpheus_xx]

xbmc/french.xml at 8d4a5bba55638dfd0bdc5e7de34f3e5293f99933 · xbmc/xbmc · GitHub

I like this kind of definition, simple and compact. If we would support such a schema, we need another control which then can dynamically create the keys.
So we might even just copy over the definitions and don't need to create all of them ourselves

 

[morpheus_xx]

Or a small converter tool that automates the manual efforts of key creation...