[Windows Mobile Software Development] meltwater:
Thanks! I'll add the language files to the next release.

Feedback is great! Just the sort of info which I need to improve it etc.

The tab probably won't be that quick simply because to get around the limitations of sense, we have to push the data through various hoops before it is displayed. However, the code which I use for reading the data out of the xml files has not been changed since I 1st wrote the tab, and I've learnt a lot more since then so I know I can make some significant improvements in this area. Obviously the focus has been on features 1st though, but at some point I'll revisit this and improve it.

I think there may also be improvements if I split up the exe more into dlls, so it would probably allow loading to be quicker too.

This is down to the update methods (since the reading/display side should now be sorted), I will do some more testing with it and hopefully work out the best way to do it (there are lots of ways to download xml files, but compact .net removes the support for different file encoding for many of the methods, hence our issues). Normally I wouldn't have released the update from the tab feature quite yet, but in order for the facebook integration to function it was required (and it seemed silly to put in extra code to disable it when eventually I'd want it back in anyway). [I'll wave the Beta flag here!]

Encoding issues aside, there are also some other feeds it simply can't do at the moment, so I still need to put provision in for them (some servers add all sorts of junk to the response which breaks some methods, while others work). Unfortunately, the only way to find out is to write code for each and test them, as well as put in parsing where possible to handle it.

I should make the external authorisation the default I think. The size issue is one of the many problems with compact .net's builtin webBrowser control, which is why there are several versions of the itemView options (which use different custom controls to try to overcome this).

I might also remove the options to disable the different permissions, since I am at least making use of them now (the fbTab asked for them, but only used some - I was planning on using the others in later versions, in fact the development version did).

I had this a few times using mobile connection, but not on wifi, I'll look into extending the timeout times, hopefully that will solve it.

- Hopefully you can still update the feed via the tab (usually when it adds it also tries to update the 1st time). I'll do some more testing on this anyway.

I've not put this in yet. One issue I will have is finding a way to mark it as read and update the display without losing which feed you were scrolled to. I need to experiment with sense and see if I can do it, this can be a long task, hence why I've not done it quite yet.

I agree, once I got it working I was thinking the same. Again, it'll take some experimenting in sense to work out a way to do this, but yes it would be far better that way.

I also plan to put the normal action as an option i.e. Open Item/Feed since sometimes you don't always want the long press option.

Yes, I've noticed while driving it is hard to tell. I'll tweak the theme file to adjust the colour a little.

I must admit I'd not tested that mode for a while, perhaps I should disable the other views (is everyone happy-ish with that?).

I still want to catch clicks on urls in the OpenNetCF browser so that they can be sent to a proper browser (either default or a selected one), as the control is not suitable for full web content (plus we don't need to be handling the whole overhead of supporting browse history etc).

I will need to dig a lot deeper into the controls code to find out how to do this though..

Yes it is a big help and it is important for me to know which bits are causing the biggest issues.

As always, time is limited, but as a daily user of the tab myself, I'm testing it all the time.

PS: Already made some changes to the facebook item views! I think if I can fix the update encoding issue, I'll do another update and then look into the sense stuff (which is always a pain and takes forever).

My ideas/plans always exceed the time I have!