MeeGo Qt Components for Android
Kate Alhola
I have made couple of experimental ports, running on simulator, Archos
101 and Acer Iconia A100
The actual components, components gallery app and my own apps based on
these components run fine
but there is some issues i like to discuss
1- Components with all theme files contains hundreds of files, it is
no sense to integrate them on application
but rather share between apps. Any idea to make them as ministro
module ? MeeGo, Symbian and desktop
components can all co-exist on same system and it is even possible
to make applications dynamically selectable UI
2- Components takes advantage of OpenGL-ES 2 shader effects, they work
fine on Iconia but on Simulator i get error of unsopported GL-ES clls
even both should be same API level. It is possible to make non
OpenGL-ES2 version but it needs some hacking. My first version for
Archos
was non-OpenGL
U nder simulator
D/Qt (20268): QAndroidEglFSScreen::createWindowSurface 0x186600
E/libEGL (20268): called unimplemented OpenGL ES API
3- Components need to be build with command line ndk but building
needs still some hand work to set all NDK related environment
variables and qmake parameters
4- Required patches are minimal, mostly theme path, screen resolution
etc . I use same theme set and basic
patches that I made for Open Source MeeGo version
5-Currtently i installed it under ministro import directory
/data/data/org.kde.necessitas.ministro/files/qt/imports
but that needs rooted device
Currently i have couple of my demo-apps , QmlComponentGallery and them
my AR-Drone app running on iconia
Kate
Koying
Do you have the sources available somewhere?
Kate Alhola
> Nice. I've done the same thing starting from the Symbian components ;)
>
> Do you have the sources available somewhere?
I have kathys-qt-components in gitorious but i have not yet pushed
code because it is work in progress and
useless to anyone else but one already knows what to do. It is not out
of the box, follow instructions and build and install
quality yet. If you or someone else feels WIP version useful, I can
push to gitorious.
Have you got work done for either compilation scripts with NDK or
ministro packaging ?
As my personal opinion, both Symbian and MeeGo components should be
ministro packages
that are automatically installed.
Kate
Koying
They compile fine into necessitas / Qt Creator for Android, but I don't use OpenGL. I also push directly into /data/data/org.kde.necessitas.
ministro/files/qt/imports
IMHO, there should be Android components based upon Symbian / Meego and with (as mush as possible) an Android look.
BogDan Vatra
Sorry for slow replay.
IMHO the most important part of a successful port is to make it look
and fell "native". Because I want to support also current widgets
we'll start working on an android style plugin. I've took a look to
symbian and meego QML components and none of them don't seems to use
QStyle to render the controls, but QML Desktop components use it, so,
before go further we should discuss how to render the controls. AFAIK
Nokia is trying to standardize all the component projects through the
common API (check
https://bugreports.qt.nokia.com//browse/QTCOMPONENTS-200 ) which
doesn't seems to be finished.
Anyway please join necessitas-devel [1] mailing list to continue this
discussion.
Cheers,
BogDan.
[1] https://mail.kde.org/mailman/listinfo/necessitas-devel
2011/12/8 Koying <cb...@semperpax.com>: