[Windows Mobile Software Development] meltwater:
WOW

WOW! What a response!

Thank you for the messages of support and encouragement, it's really nice to see that the project is a good choice.

I'll try to cover everything (sorry if I miss something specific).

1. Still looking for developers to work on this, as I said even novice programmers can get involved it should be a good learning platform, and I'm fairly sure that between us on here we can complete most of what needs to be implemented.

A) At the moment the code already reads the xml files (which is the format of a RSS feed) but I need it extending to cover a bigger range of xml files and to read in the general feed information. It is not a difficult job, since it's a case of using the code there and adding to it for other fields.

B) I've got so many aspects I need to address and work on, however the main jobs at the moment are:

- Implement the rss selection layer view (with interface to and from RSSUtil.exe), this will mean the source feed is no longer fixed to a single file.

- Transfer the facebook settings code to be used and adapted later on (will initially just provide the code but remove saving of the settings and authorisation section). It will include the source for the langapi which allows the sense language files to be used for translations. [settings and translations are best done later though since there will be a lot of change]

- finish the media launch code (so close but gets the incorrect item), need some graphics for this...

2. Clearly I've not missed the requests for support of different apps and in particular Google Reader.

My answer to this is the following:

It is an open project, so you are welcome to make the changes required to include support for whatever you want (obviously make sure it is selectable and optional).

For now, my focus is to get the basics working and make it usable (the sooner that is done, the sooner it'll be able to be used). The nice thing is with RSS is that the source file is the same, so it's not too important where it gets it's data from or how (we can work that detail out later, if we sync to other apps, if it is standalone or managed online etc). If there are specific features or ideas on how you think it should work or things you'd like to implement then put it in the wiki so it doesn't get lost within the thread. I wouldn't mind some detail about how you'd think the Google Reader integration would work, api protocol etc.

3. Has anyone got it working as it stands? There's been a good number of downloads, but no one has mentioned if it's tested ok (although granted it will be easier to try when not tied to a single test file/file location). Clearly when we have something which is supposed to work, the offers for testing will be great (I expect we can keep this open too (unlike the facebook app, there is no issue with personal info and application keys, security etc).

4. Are there any developers who are interested in taking the plunge and giving it a go? At some point I'll try to add to the wiki to explain the different baselines in the dev package etc (will attempt to keep a running change history as I do stuff), but basically they are the different stages I went through to generate the separate tab and would form the bare-bones for another tab.

At the moment my time is limited so will work on this slowly, if I get any thing decent working I'll update the WIP file with any changes from latest baseline within the dev package and I'll update the dev package with a new baseline as and when it needs it. Open for suggestions still on the best way to keep these files updated if/when there's more than one dev. If you start developing using the files then let me know so we don't end up working on the same bits (I'll try to keep the development list updated with what I am up to, but I may deviate from time to time).