Re: [SailfishDevel] keyboard development

2018-03-18 Thread eetu

Hi Rinigus,

I just wanted to bring to your attention the Nemo Mobile maliit-plugin 
keyboard (https://github.com/nemomobile-ux/plugins). It is fully 
open-source and it can run on SailfishOS devices.


Only thing that we are lacking is the prediction support and some small 
features. We are considering about moving to new maliit keyboard(based 
on ubuntu maliit) or then 
qtvirtuakeyboard(https://github.com/qt/qtvirtualkeyboard).


I am really interested in your keyboard project and would like to 
contribute to it so that Nemo would also have updated keyboard!



BR,

-eekkelund :)



On 03/07/18 12:11, rinigus wrote:

Hi Pekka

Thank you very much for the reply. I have inserted my replies below.

Short recap on history. Original Maliit reference plugin was developed
for Nokia N9, I was the lead developer for that. On Jolla I wanted to
do more QML centric one, based on lessons learned on original Maliit
keyboard and another virtual keyboard at Nokia. Ubuntu keyboard went
another way and continued from the old code base, think it was also
made public after Jolla keyboard had proceeded a lot.


OK, so we now where the development diverged and the branch between 
Jolla and Ubuntu (now Maliit default).


> Now, I do wonder what is the long term plan with the keyboard
> development? From the outside of Jolla, it seems to me that it would
> be wise to join forces with the others and develop this component
> together. Each OS in question has their own styling, but that seems
> to be possible to apply on top.

Not sure if it would be worth much redoing Jolla UI on top of another
plugin. Would make the base more complex by requiring extendability of
different things.


It will surely require time and, in ideal world, is a needless 
duplication of an effort in a small OS which has many other components 
that would need more attention. I agree with that aspect.


What matters more is ability to reuse different input method
engines on
 different keyboards. While not being too familiar with the current
state of maliit-keyboard project, I'd expect it to be somewhat easy
anyway. Qml can reuse list model regardless of api elsewhere. For
integrating input to jolla-keyboard it's mostly just implementing
handler functions for key press/release/click. For general western
input that is currently little over 100 lines, some more for updating
layout geometry to the prediction engine.


Indeed, we have now the input method that links presage to 
jolla-keyboard written by @martonmiklos. We could probably go a long 
way by expanding Presage with correct handling of Unicode string, 
implementing tokenization in Presage to support more languages and 
exposing this functionality to the plugin. This work can be reused 
then by any keyboard, not even limited to Maliit.


> Its not trivial to compile the latest Maliit on SFOS (they switched
> to CMake based builds and few cmake configs are missing in SFOS
right
> now), but I expect that its possible with some effort. Just don't
> want to spend too much time if it's gonna be without any use.

Guess it depends on what you're up to. If CMake modules make sense on
other projects then PRs welcome (some already packaged). If for
keyboard you want to have ability to tinker and use a different one
then just go ahead :) Maliit framework supports also having multiple
plugins, but on Sailfish we've relied on just using the single one
that
is found, multiple ones might trigger code that hasn't been much
tested
 for a while.


Indeed, it depends on the priorities. Personally, I am interested in 
developing open-source prediction/correction engine since I am using a 
ported device and want to have good and working solution without Xt9. 
Throw in the fact that Estonian probably doesn't have Xt9 support and 
you have my main interest formulated. However, in the background, I 
also like our approach since we rely on open-source libraries and this 
is transparent to the users community as well as gives us an ability 
to reuse the components elsewhere.


When talking about one of the main user-interacting component in the 
OS, such as keyboard, the transparency does become an important part 
of the discussion. Large fraction of jolla-keyboard code is in QML and 
we can see what QML is doing, if we wish. However, there is a library 
blob which I have no way of knowing what's going on there. All I can 
see is that its linked to all kinds of other libraries through its 
dependencies, including network libraries as well. So, its essentially 
comes down to the trust that the version that I have installed on my 
device doesn't call somewhere with something. The trust that I do have 
at this moment. But I do find the situation far from ideal and would 
prefer to have open stack for myself and all other end users in the 
core components of the OS. In particular, the p

[SailfishDevel] The 1st Maemo Developer Regatta - The starting line

2016-10-31 Thread Eetu Kahelin
The Maemo Community e.V. proudly presents

The 1st Maemo Developer Regatta - The starting line

sponsored by Jolla



The wait is over!

The first Maemo Coding Competition for all Maemo derived systems, including but 
not limited to Maemo and SailfishOS.

This year's competition has the following three categories: Something new, 
Fixing/Updating and Beginner. Whether you are an experienced developer, porter, 
hacker or just a beginner on your very first hacks/codes, we have a category 
that suits you and your coding skills! If you are new to programming or want to 
learn, here's the excuse to finally make something. Anything. Entries for Maemo 
& Mer-based devices are eligible.

The timetable for the competition is the following: The competition begins on 
Tuesday, 1st of November, and will be running for 3 months until Tuesday 31st 
of January 2017. You can enroll into the competition at any time, however, all 
the entries for the competition must be submitted no later than by 23:59 on 
Tuesday, 31st of January(UTC time). Testing/reviewing will take two weeks, from 
01.02.2017 to 15.02.2017 and voting will run from 16th of February until 28th 
of February 2017, 23:59 UTC.

Follow the links to the 
wiki below for more 
information.

Devices & 
Platforms
Categories
How to Submit an 
Entry
Prizes
Participants
Rules
Voting
Developer 
Resources

If you would like to have an App, a Port, a Fix, a Hack or etc. but you can't 
code it yourself, don't worry, just write your ideas in 
here! Many 
developers would be happy to get a new idea input.

We are relying on your donations towards the Community Prize 
Fund.

The entry is free of charge.

Thanks for your interest in taking part, we can't wait to see what you will 
develop! :)

You still have questions? Contact us!
- council<*at*>maemo<*dot*>org
- talk.maemo.org thread
- together.jolla.com 
thread

Regards
Maemo Community e.V.

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org