Topic Publishing and Layout

We have two new locations for Keyman technical support:

The Tavultesoft Forums are now read only.


# Publishing and Layout   2016-10-16 18:34:52.010
Ray Dai
Hi,

Two questions:
1) I seem to remember there is a publishing function in Keyman Developer before which I am not seeing anymore. I also have submitted two keyboards via this website in April but they were not published. I understand you have been going through a lot of transition so it might got overlooked.

So is Github (per http://help.keyman.com/developer/keyboards/) the correct way to submit keyboards so they can be merged into the official list and installed directly by users?

2) In the developer Doc it was recommended that a single keyboard to be made for all platforms. For my keyboards, the desktop layout uses punctuation keys heavily which are on a separate screen for phones so would you still recommend one keyboard with the keys moved or two keyboards, one optimized for desktop, one for mobile?

Thank you!
Ray
# RE: Publishing and Layout   2016-10-27 01:29:55.510
Marc Durdin
Tavultesoft Staff
Thanks for the questions.

1) Yes, the link you provide, and Github, is now the preferred way to submit keyboards for publication. I've just published the keyboard you submitted recently, at http://keymankeyboards.com/705 but it'll be good to get the updated version online via the Github process as well.

2) You are correct: it is not a great solution to overload punctuation keys on touch layouts, because touch layouts have better ways of solving the problem. With Keyman, it is possible to use the platform features of the Keyman Keyboard language (http://help.keyman.com/developer/language/reference/platform) to modify the behaviour of the keyboard to solve this. This is my recommended approach. I can send you a sample version of the EuroLatin2 keyboard which does precisely this (I have not yet had a chance to publish Eurolatin2 on our git repository).

The advantage of a single keyboard is that for end users, they only need to refer to one place for the keyboard, and for maintenance in the future, it becomes less of a chore.
# RE: Publishing and Layout   2016-10-27 17:52:18.973
Ray Dai
Thanks for the reply.

I see, using the platform function we can essentially bundle the two layouts in one, or programmatically chose which key to send. That sounds nice, I would love to get the keyboard you mentioned. Thanks!
# RE: Publishing and Layout   2016-10-31 22:32:42.967
Marc Durdin
Tavultesoft Staff
Ray,

I've emailed you the keyboard source -- it will take a bit of work to get it into the keyboard repository, so the email version will have to do for now.