[Windows Mobile Software Development] meltwater:
When you mean latest, I guess you mean the icon fixes for release D. If so, you can probably update your _manila files by hand by transferring them from the zip (just leave your tab control 26948339_manila file as is).

The next release will consider how to upgrade existing installs as well as clean installs (as far as the cab is concerned I *hope* captain_throwback will be able to do the usual honours for me in that department, also Moonnah's manila fix program should help smooth out the install issues from the past). Testing out cab files and developing custom code is not a good mix on the same device and is a good way to lose stuff, so will leave that for others to test.

One of the core concepts I've been trying to keep to is to keep is as integrated as possible, as soon as it stops being a "tab" it's just another fb app and the experience is ruined. However, this concept is at odds with making life easy, since tying into the tab side is difficult, particularly (as I've discovered) when it's using manila lists of items and it's own tie-in's to htc dlls. This is also why I've delayed the rest of my fb api integration as creating the interface for that would delay any release for a good while, any good GUI needs time to be played with.

Dev Update 03June:

Transfer of the settings page is going well, items are now populated from registry (although may add some more yet) and about 1/2 way there for transferring the event handlers, then need to transfer the saving of the settings.

There is tons of code in it, but at least once it's done it'll be easy to add anything new! Trying to get my head around my code I did for adding/editing app/web shortcuts now...

At some point I'll post the old settings page and you can see how much better the Sense SDK from eboelzner makes things.

The language support is gonna take a while to do as well (have the code to do it, just a case of tying code to every text item), still not sure how much of a performance hit it will have either (will decide on this later I think if it'll make beta).

Dev Update 04June:

Getting there slowly. Since the way I've put things into subpages, taking some time to sort out how best to handle accepting changes occurs inside and outside of the subpages (particularly when the subpage controls the data in the one above etc), which is more complicated than it looks. Still will keep at it, more and more of the settings are getting done.

Totally Off-topic:

Had some interesting ideas for TV/PVR/PC device (another of my interests), just need bags more time and a tiny bit of cash to experiment with the electronics side. I think the software is available to do what I want (or at least the basics) but for all the PC connected solutions I've seen there's two problems.

1. Unless you keep your pc turned on, it's not available when you want it.

2. Usually you want to keep watching tv, so you don't want to switch over to the pc.

Solution:

Device which senses TV turned on (and also automatically activated by internal timers for PVR function) and when completed booting automatically switches TV input to the pc (which by default is a live feed of the current channel full screen - so only difference is say a logo in corner). Any apps/features then sit on side bars etc which can be pinned like channel logos etc where-ever you want them as an overlay or the feed reduces side to accommodate them. Need a graphics input which can transfer/resize a input feed with very little processing load (ideally kinda want video-overlay but in reverse - video is the main display and the windows are over-layed).

Add PVR function tied to a network hard-drive with automatic compression of recordings, streaming between like devices, rss feeds and widgets etc etc. Plug in any number of freeview/tv tuners/video feeds/sat usb sources...

Oh well, that's my offtopic and I'm sure someone will make it eventually if they don't already.

As I see it, we can't be far off being able to do this, 10% hardware and perhaps 20% gui to do?