The last couple of years I have had a variety of Windows Mobile devices. They were always working for me, but not exactly 100% as I would have liked. With regards to the communication with Linux, I have tried [...]]]> A couple of weeks ago, I had the possibility of extending my current phone contract again.

The last couple of years I have had a variety of Windows Mobile devices. They were always working for me, but not exactly 100% as I would have liked. With regards to the communication with Linux, I have tried with the SynCE group to work on this.

One thing I never did was writing programs for the device itself, only for communicating with the device under Linux. I did not think that writing programs for windows mobile under linux was very easy, so I never went further with this.

Also, lately I have been getting fed up with the fact that for new websites/services there are excellent clients for iPhone / Blackberry / Android, but almost never for windows mobile. A good example of this is Facebook, which has a very crappy Windows Mobile client.

After seeing which devices were available, I decided to extend my contract and get the new Desire HD. It took me a bit of time to get used to the new kind of interface, but I have to say that I really like Android (with Sense). I am really happy that my current phone does not have Windows mobile anymore The major advantage for me is that finally I have the possibility to add two exchange server accounts to the device at the same time, both with Push syncing: I can have my phone connected to the exchange server at work and at the same time to my Zarafa server at home

Also, having android allows me to easily develop applications for the device under Linux. The only thing left for me now is to find a good idea for which no app has been written yet

Having this new phone will mean I will probably not actively develop new functionality for SynCE-KPM anymore. However, if bugs are found, I will try to see if I can solve them

Currently, the feature is only available in the SVN version of SynCE-KPM (which depends on the SVN version of librapi2). However, we are currently thinking about releasing the 0.15 version of SynCE, which would [...]]]> After some final coding last night, I finally finished the new feature for SynCE-KPM: viewing the registry of your device via SynCE-KPM.

Currently, the feature is only available in the SVN version of SynCE-KPM (which depends on the SVN version of librapi2). However, we are currently thinking about releasing the 0.15 version of SynCE, which would contain this new feature. As soon as more information about the new release is available, you will also see that on my website.

To show the new feature in this version, I decided to create another screencast. While the previous screencast did show a lot, it was relatively boring due to the fact that there was no sound at all. Therefore, I decided to add a voice over to this new screencast, explaining everything in a bit more detail. In the screencast I do not show all features related to the syncing part (via sync-engine) again, because this takes quite some time and this has already been shown in my previous screencast. In the current screencast, sync-engine is not running and only the device management capabilities of SynCE-KPM are shown.

The screencast:

Of course, you can still view the old screencast if you would like to see the display the status of an ongoing sync-process, or installing a CAB file onto your device. This old screencast is in the Lost screencast post on my website. Please note, that this old screencast is without any sound.

When you have the feature of viewing the contents of the registry, of course the next question is to be able to edit the contents of the registry. This is what I see as the next feature to implement in SynCE-KPM, though at the moment I don’t know when I will have time for this. As with this currently implemented new feature, whenever I have time, I will start working on it

If you have any questions, suggestions, etc, please leave a post or send me an email.

I noticed that on my windows computer, Windows Mobile Device Center was able to show a picture of my device. I was always wondering where this information [...]]]> Even though I was not feeling well today (spent day sick at home, having cold shivers all the time…), I did look into one small new feature for SynCE-KPM.

I noticed that on my windows computer, Windows Mobile Device Center was able to show a picture of my device. I was always wondering where this information was taken from. Turns out that this picture is actually taken from the device itself. I guess it must be something prescribed by ActiveSync or Windows Mobile Device Center to have the image /windows/sync.ico present.

After the device is connected, SynCE-KPM will now look if that file exists, and if it does, obtain it and show it to the user in the main window.

Example screen with two different phones I have:

SynCE-KPM now shows device (example 1)

SynCE-KPM now shows device (example 2, my HTC HD2)

I still have the major new feature left: implementing the remote registry editor. This is still on my TODO list, but unfortunately I don’t have as much spare time as I would like to have to work on this.

Another thing that I need to work on with SynCE-KPM is the usage of layout managers instead of not being able to resize as with the current implementation. Will take me some time also. Will get there though, slowly

However, as you [...]]]> After the previous post I started working on integrating the stand-alone prototype within SynCE-KPM. As mentioned, at the moment I only have a view on the keys, not yet the values. Furthermore, at the moment there is no error checking, switching a device will not work, and some other minor things

However, as you can see from the screencast

it is already possible to view all the registry keys that are present in the registry. Also, from the screencast you can see the Fetching… node that is shown to the user whenever the actual data is being queried for the first time. It can also be clearly seen that the fetching is done in a separate thread, not related to the GUI thread, because even while fetching, the GUI still is responsive. Any further requests for fetching the user does, are just queued to the dataserver, which will retrieve them in the order they were requested.

I have already thought about how to incorporate the values and I have come up with a solution that uses the current registry and registry key objects, but with a different model. This means I will have to custom models, both subclasses of QAbstractItemModel, using the same underlying data, but only the parts they need.

One thhings I still need to do is determining what to do with updates (i.e. when to refetch keys, when being clicked on, or have the user explicitly request refetch). Also some GUI things need to be changed. At the moment it appears that the current window width of synce-kpm is not enough for a registry editor, might have to make the application a little bit wider. All in all, plenty of things to be done (and sooooo little time… )

I would like to include this as a new feature within SynCE-KPM, and because this is written in PyQt4, the addition needed to be in PyQt4 also. This meant investigating the MVC concept within [...]]]> The last couple of weeks I have been working on the basics for a remote registry under linux for windows mobile devices.

I would like to include this as a new feature within SynCE-KPM, and because this is written in PyQt4, the addition needed to be in PyQt4 also. This meant investigating the MVC concept within Qt4, with the QAbstractItemModel, QModelIndex, and QTreeView (at least for the hierarchical folder structure on the left part of the remote registry editor).

After lots and lots of fighting with the QAbstractItemModel and QModelIndex, I think I have finally understood howto succesfully use them together in order to show a nice treeview structure in the QTreeView widget.

One part that caused me a lot of headaches is what the exact role of the QModelIndex is and how exactly to use these. The problem is that you are not allowed to save them in some dictionary, because they are considered to be volatile. Eventually, with some reading of the Qt website I found out how, given a particular registry key within my own backend registry storage classes (that gets its data eventually from the device), I can create the correct QModelIndex that can be used by the model.

In the end the QModelIndex turned out to be not that difficult, because it basically is only a small holding object, that contains a reference to the actual underlying data that I can access via the internalPointer() method. Another way is to use the internalId() method, but that would require me to keep my own dictionary from internalId to the actual data objects. My first thought, that this QModelIndex needs to contain all information about parents etc, turned out to be false: the QModelIndex just queries the model again for parent information.

Most of the times, when looking back after lots and lots of investigating and frustration, the concept and howto actually use it turn out to be relatively simple

The prototype I have at the moment is not yet integrated within SynCE-KPM, it is just a separate program at the moment. Furthermore, it does not show any of the values within the registry just yet, only the structure of the keys are shown via a tree within the QTreeView. I have made a small screencast which you can see below:

For the moment you have to take my word that the data shown is actually taken realtime from the device and is not hardcoded in my program One thing that I still like to solve is the issue that can be seen towards the end of the video: clicking on HKEY_CLASSES_ROOT takes a really long time before anything is actually shown. My current idea to ’solve’ this is to give all nodes by default one virtual child key with the name “Fetching…”

When the user expands a node, he will first see the “Fetching…” childkey being displayed. At the same time Synce-KPM will be retrieving the data from the device. After all sub-keys have been retrieved, they will be shown and the “Fetching…” childkey will then be removed.

I have tried implementing the above approach within the current prototype program, but this resulted in a lot of segmentation faults that I could not place. I am not sure what is causing this issue, but it appears that the segfaults are caused when I both delete the “Fetching…” childkey and add the actual childkeys all within the code that handles the the node-expand signal. My guess (well, hope ) is that in the final SynCE-KPM version this should not be a problem: because of the two separated processes (GUI and dataserver) I can ensure that I am only doing either deletion, or adding, but not both.

Still todo are:

• Include within SynCE-KPM (instead of separate program)
• Create a listview for the values that are stored the selected key
• Add possibility of not only viewing the registry, but also modifying

While the other [...]]]> For the new feature of SynCE-KPM I am working on at the moment, I want to emulate the look and feel of the windows standard program regedit.exe. This means showing the user a QTreeView showing the hierarchy of the keys and a QListView on the right showing all values within the selected key.

While the other day I have been working (and finished) on the librapi2 stuff, in particular the python bindings, to facilitate a registry editor, for some days I have been looking at this whole QTreeView stuff. I have to say that I really do appreciate the idea behind MVC, but I have to say that to use this in a nice way in PyQt is really difficult. After some days I am now at least able to create a nice QTreeView based on a model that represents the registry. Currently, everything is still hardcoded, but at least I can see a structure now (the QListView with values will come much later ).

Next step is to see if I can connect the model to the actual contents of the registry on the device in a dynamic way. The problem is that I need to fetch new data from the registry only when it is needed. One simple approach is to first read the complete registry into the model and then show this to the user. However, I don’t think users will like it if there is a 5 minute delay showing “Fetching data” when going to the registry editor before they can actually use the registry editor. This means I will have to fetch data in some asynchronous way. Fortunately, I already have some ideas about this. For some reason I think this fetching part is again the easy component….. Don’t want to think about all the mess that is involved to show this in a nice way to the end-user.

For the moment just happy that at least the very basics of the left-hand side of the future screen (i.e. the hierarchy of the keys) needed to display actual data are there. Onwards to new challenges with PyQt and its MVC

Due to the [...]]]> Update 2010-04-05: I have created a new screencast with the new features that will be present in the upcoming 0.15 release. Currently it only works with the SVN version of SynCE-KPM (which depends on SVN version of librapi2). This screencast can be found in the New feature in SynCE-KPM post on my website.

Due to the crash, I lost all my posts. One of the posts was showing a screencast of synce-kpm in action.

For the people that could not see it anymore and just for making my blog complete with the screencast again, here it is:

Unfortunately I did not have a lot of time to do this earlier, first of all my time was taken completely by finishing up on my thesis and getting all the details right. After that there was [...]]]> Although it has been released for some time already, finally there is the message on my blog

Unfortunately I did not have a lot of time to do this earlier, first of all my time was taken completely by finishing up on my thesis and getting all the details right. After that there was a servercrash at my hosting provider and after that I went on vacation.

The main improvements with SynCE-KPM 0.12 are that some bugs have been fixed and that SynCE-HAL is now supported. This synce-hal is a new connection manager that is intented to replace odccm. The main advantage of synce-hal over odccm is that we do not longer require a separate daemon running (odccm) in the background, but everything is taken care of by HAL. The moment a device is plugged in, HAL will make fire up the needed stuff. Another advantage of SynCE-HAL is that it also is able to work transparently with the legacy way of connecting (i.e. PPP over USB) and that bluetooth is working also (though I don’t know about whether this feature is enabled in the packaged version of synce-hal, I did have it working when running the SVN version of it some time ago).

When people have new ideas of things that can be added to future versions of SynCE-KPM, please let me know and I will see what I can do to implement these wishes. One thing that is still on my own wish list is to implement a remote registry editor. For this I will have to put some more time in pyqt though