<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
<div class="moz-cite-prefix">On 2014-04-12 22:53, Andrey Kozhevnikov
wrote:<br>
</div>
<blockquote cite="mid:5349A7B4.6050106@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Silica version not finished because of some design and
implementation problems.<br>
Sailfish contains meego components ported to qt5, you may notice
2.0 version (instead of 1.0/1.1 in harmattan), its okay and means
nothing except backward compability.</blockquote>
<br>
Yes, as Andrey said, the Silica version isn't finished, and there
are some bugs. The version of Fingerterm that is shipped with
Sailfish OS as the Terminal application in developer mode is built
directly from the master branch sources (the tags correspond to the
RPM package versions, see [1]).<br>
<br>
The Qt Components usage is just historic, and in case of Fingerterm
it mostly provides a rotating window only (the rest of Fingerterm is
done using pure Qt Quick 2.0 components and a custom component for
rendering the terminal itself).<br>
<br>
The "silica" branch replaces Qt Components usage with Sailfish
Silica, uses libsailfishapp for startup boosting, uses theme colors
for some parts (notably the virtual keyboard keys) and uses Silica
pages for the menu.<br>
<br>
Eventually the "silica" branch will be used on Sailfish OS once the
remaining bugs (see issues on Github) have been fixed, and once it
has feature parity with the "old" one, but the master branch / Qt
Components will probably not go away, as Nemo Mobile does not have
Silica. But maybe there will be some special Glacier UI port of
Fingerterm, in which case the Qt Components branch will probably
eventually go unmaintained once the new UI-specific ports have
picked up.<br>
<br>
In that case, we should probably split the terminal emulator parts
into its own library as in [2], which will make the code a bit
cleaner and allow for different experimental terminal emulator apps
to be written (or even terminal emulators to be integrated into
other QML apps). With that said, a very good Terminal Emulator
library for QML exists called yat [3], but yat lacks a custom
virtual keyboard, which can be seen as an advantage (using the
native input method instead) or disadvantage (the fingerterm
keyboard has some keys [Tab, Ctrl, Cursor keys...] that are useful
for terminals, but not so useful everywhere else). Maybe we can just
theme the vkb in fingerterm's "silica" branch so that it looks like
Maliit (the native VKB used on Sailfish OS)? Or maybe Maliit is
extensible enough to still get rid of the custom VKB in fingerterm
but "inject" tab, ctrl, cursor keys, etc.. into the native VKB?<br>
<br>
<br>
HTH :)<br>
Thomas<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="https://wiki.merproject.org/wiki/Nemo/Development#With_tar_git_service">https://wiki.merproject.org/wiki/Nemo/Development#With_tar_git_service</a><br>
[2] <a class="moz-txt-link-freetext" href="https://github.com/nemomobile/fingerterm/issues/29">https://github.com/nemomobile/fingerterm/issues/29</a><br>
[3] <a class="moz-txt-link-freetext" href="https://github.com/jorgen/yat">https://github.com/jorgen/yat</a><br>
</body>
</html>