Running Qtopia apps and services on X11 with enlightenment as window manager. This is done to benefit from the applications and working services but still allow integration with other toolkits and systems. The difficulty is to integrate Qtopia into the freedesktop.org world. This includes launching of apps, services, window management, installation, FHS obeyance...

Running Qtopia apps and services on X11 with enlightenment as window manager. This is done to benefit from the applications and working services but still allow integration with other toolkits and systems. The difficulty is to integrate Qtopia into the freedesktop.org world. This includes launching of apps, services, window management, installation, FHS obeyance...

Line 8:

Line 6:

The command to clone the tree is:

The command to clone the tree is:

−

git-clone git://git.openmoko.org/git/qtopia.git

+

git clone git://git.openmoko.org/git/qtopia.git

−

Then read the README.x11 and have fun.

+

Then read the README.x11 and have fun.

== Open issues ==

== Open issues ==

−

* better GTA02 integration

+

* Fixup packaging in OpenEmbedded (html help files).

−

* Screenlock, blanking, suspend handling, e.g. Qtopia wants to know when it is waking up, the blanking of the screen should be handled by e though.

+

* Sync/Fix races in the phone libraries and callscreen.

−

* Packaging in OpenEmbedded

+

* disable more stuff from Qtopia.

+

* Sometimes the soft menu does not get updated

+

* Playing the ringtone is "slow". Is this an issue with our QCOP implementation?

* asserts in the server and library code can degrade the user experience. E.g. I managed to hit !syncTime.isValid() in the PIM lib (they don't happen since we install timezone files)

* Make Qtopia parse the menu file and freedesktop.org desktop files

* Make Qtopia parse the menu file and freedesktop.org desktop files

Line 21:

Line 26:

* Launch an application on incoming phone calls, to inform the screen lock about it

* Launch an application on incoming phone calls, to inform the screen lock about it

* Interaction between screen lock and qpe e.g. with incoming phone calls while being suspended

* Interaction between screen lock and qpe e.g. with incoming phone calls while being suspended

−

* Placement of the softmenu and application

+

* Screenlock, blanking, suspend handling, e.g. Qtopia wants to know when it is waking up, the blanking of the screen should be handled by e though.

−

* NETWM_WORKAREA fixes, it should make it a supported WM_PROTOCOL as well :)

+

* modem state, airplane mode

+

+

+

+

== Need QA verification ==

== Discussion ==

== Discussion ==

Line 55:

Line 64:

=== Input methods ===

=== Input methods ===

Besides using an optimized Trie with a mmapable representation (fast lookups even of huge dictionaries!) you can attach a input method hint to any QWidget.E.g. if you need to insert an IP address into a QLineEdit the input method could show a special mode to assist in this. [http://doc.trolltech.com/qtopia4.3/qtopiaapplication.html#setInputMethodHint Setting a hint] for the current widget, this can be an arbitrary string, the actual hint is then a file in the etc/im directory.

Besides using an optimized Trie with a mmapable representation (fast lookups even of huge dictionaries!) you can attach a input method hint to any QWidget.E.g. if you need to insert an IP address into a QLineEdit the input method could show a special mode to assist in this. [http://doc.trolltech.com/qtopia4.3/qtopiaapplication.html#setInputMethodHint Setting a hint] for the current widget, this can be an arbitrary string, the actual hint is then a file in the etc/im directory.

Running Qtopia apps and services on X11 with enlightenment as window manager. This is done to benefit from the applications and working services but still allow integration with other toolkits and systems. The difficulty is to integrate Qtopia into the freedesktop.org world. This includes launching of apps, services, window management, installation, FHS obeyance...

The homescreen can not be used, CBS can only be shown as Popup, need to update the CBS apps and tools to show them as popup. To indicate signal strength, requiring pin, registration, airplane mode we will create a D-Bus interface in QPE and emit signals for this status. A gadget in illume can pick this up and it is planned that it will pick it up. The D-Bus interface should be similar to the one mickeyl is supposed to come up with to ease migrating to this interface.

To assure single exec we run the execution through the QPE process. The downside is that we currently have two copies of .desktop files with two similar standards. Also this is creating an island, where 'services' are only available on QPE. The minimum for Qt would be to parse fd.org desktop files so that we can throw Qtopia's copy of them away.
Also launching should not be done by the qpe process in the future. Currently we invoke qcop and the Launcher to service and request to launch applications.

With Qtopia you can describe a service and give the user the choice to pick the preferred service. Read more about services here. Basicly you define a service Foo.servie and then have a directory Foo/ and providers of this service can put a file with their name into this directory.

Content is abstracted from a file hierachy to be type based. To continue with this thought and to make it scale RDF, tree views, indexing comes into mind. Is there something we can learn from here besides making it scale?

Besides using an optimized Trie with a mmapable representation (fast lookups even of huge dictionaries!) you can attach a input method hint to any QWidget.E.g. if you need to insert an IP address into a QLineEdit the input method could show a special mode to assist in this. Setting a hint for the current widget, this can be an arbitrary string, the actual hint is then a file in the etc/im directory.

Views

Personal tools

What

Running Qtopia apps and services on X11 with enlightenment as window manager. This is done to benefit from the applications and working services but still allow integration with other toolkits and systems. The difficulty is to integrate Qtopia into the freedesktop.org world. This includes launching of apps, services, window management, installation, FHS obeyance...

Getting the code

There is a gitweb for browsing the code and in the future the rsync branches will be merged instead of rebased.

Open issues

Screenlock, blanking, suspend handling, e.g. Qtopia wants to know when it is waking up, the blanking of the screen should be handled by e though.

Packaging in OpenEmbedded

Make Qtopia parse the menu file and freedesktop.org desktop files

Needs e work

Launch an application on incoming phone calls, to inform the screen lock about it

Interaction between screen lock and qpe e.g. with incoming phone calls while being suspended

Placement of the softmenu and application

NETWM_WORKAREA fixes, it should make it a supported WM_PROTOCOL as well :)

Discussion

Homescreen, CBS and Airplane mode

The homescreen can not be used, CBS can only be shown as Popup, need to update the CBS apps and tools to show them as popup. To indicate signal strength, requiring pin, registration, airplane mode we will create a D-Bus interface in QPE and emit signals for this status. A gadget in illume can pick this up and it is planned that it will pick it up. The D-Bus interface should be similar to the one mickeyl is supposed to come up with to ease migrating to this interface.

Integration with Desktop

Write proper freedesktop.org files

How to generalize the Service concept

How to generalize the Softmenu

How to approach dbus (besides defining QTOPIA_DBUS_IPC

Brining power of Input methods to freedesktop.org

Midterm/Longterm

Better PIN Handling (SIM PIM, etc..) in EFL, more appealing UI

Launching of applications

To assure single exec we run the execution through the QPE process. The downside is that we currently have two copies of .desktop files with two similar standards. Also this is creating an island, where 'services' are only available on QPE. The minimum for Qt would be to parse fd.org desktop files so that we can throw Qtopia's copy of them away.
Also launching should not be done by the qpe process in the future. Currently we invoke qcop and the Launcher to service and request to launch applications.

What to learn from it

Service defintions and Service Providers

With Qtopia you can describe a service and give the user the choice to pick the preferred service. Read more about services here. Basicly you define a service Foo.servie and then have a directory Foo/ and providers of this service can put a file with their name into this directory.

Content management

Content is abstracted from a file hierachy to be type based. To continue with this thought and to make it scale RDF, tree views, indexing comes into mind. Is there something we can learn from here besides making it scale?

Value Space

What is a value space? It looks like it is a cross process way to define a tree of values. You can query state, features and similar things with it. The entry to the documentation can be found here.

Input methods

Besides using an optimized Trie with a mmapable representation (fast lookups even of huge dictionaries!) you can attach a input method hint to any QWidget.E.g. if you need to insert an IP address into a QLineEdit the input method could show a special mode to assist in this. Setting a hint for the current widget, this can be an arbitrary string, the actual hint is then a file in the etc/im directory.