[Windows Mobile Software Development] meltwater:
Dev Update 11th May:

Work is continuing on the API, coming along nicely, due to my lack of experience with generating API code, I have to evolve it by using it to work out how best to provide the functions etc.

Now have a basic "update status" page, which is independent of the test code and uses the API calls, still needs Sense SDK look implementing.

Started to look at other users status updates, discovered I also can get to status updates for contacts which although linked to facebook on HTC, their status updates don't appear (due to privacy settings). Not sure how I can integrate that at the moment though.

Need to covert the JSON text which the fb api returns for the status feed into a meaningful object to work with (done this with the friends list, but this is more complex).

> Done this now (using copied data, will need to test again using genuine responses)

> It sort of works, although there is a mix of data in the feeds so don't just get status updates back. Not much use for the main tab yet...

Need to resolve issues with authorisation, currently handled within the specific page, but I think I will move it to the settings page. Still don't know what to do about the application keys.

Also need to determine how updates should occur, do we want the tab to gather all the information in one go or download it when we need it? Currently, it's downloaded on demand, but I think support for downloading all the required information during the update would be helpful. Ideally, this could be selectable, perhaps even on a component basis (or even friend basis). Should be able to store the data in files, hopefully would then be able to only request data since the last update of the file, will be tricky to manage though.

Need to update my manila code to use direct links to My Update key copy, Status Update Page, Settings Page

> Done, although left it so you can still use mortscript which appears to be quicker for My Update key copy (could just be that the

At what point do I release???? :D

UPDATE:

Interestingly I just switched between using mortscript and the exe for performing the copy of the registry for the status text (using my device touch HD) and the scrolling was slightly more jumpy! Perhaps this is the same issue others have experience with the tab, I'll keep the support in for the script (if the registry reference is removed, it'll default to the exe).

Dev Update 12th May:

Still looking into items:

1. Sense look - will finish off layout first then transfer to sdk

3. Need to experiment with this to filter the data as needed

4. Settings page is updated now - just need to change api.

5. Will split requests and processing in the api, with requests writing to files and processing reading from them.

8. Update setting page with improved browser from johncmolyneux

Dev Update 13th May:

4. Ok broke some stuff, such as the authorisation as I moved it to the settings page. Ah found the error, will check tonight!

Nope still busted, but I'm hoping I've not completed the switch over fully (the problem with only having short bursts of dev time).

8. Done, much better!

Language:

Considering dropping mutli-language support from the settings page (for now). There is a lot of text involved and until we are sure of what settings we want and how best to describe each one, it'll be better to focus on only translating important stuff which isn't likely to change, i.e. any subpages... Also, the settings page is complex enough without needing to deal with "text in language X doesn't fit" issues etc etc.

When we are happy with it multi-lang can be added.

I'll still support multi-lang for any pages the tab opens directly, although I will try to use icons where possible anyway.

Supported languages will currently be:

"en-gb", "en-us", "de-de", "pt-pt", "es-es", "fr-fr", "cs-cz", "it-it", "zh-tw", "no-no"

Just experimenting with a standalone device emulator, which should allow easier testing of api stuff remotely.