View source for Qtopia on X11
From Openmoko
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to Qtopia on X11.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to Qtopia on X11.
Qtopia on X11
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...
There is a gitweb for browsing the code and in the future the rsync branches will be merged instead of rebased.
The command to clone the tree is:
git-clone git://git.openmoko.org/git/qtopia.git
Then read the README.x11 and have fun.
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?
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.
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.