I’d hoped to have a 0.2 of Twaddle out by now, unfortunately that’s not been the case.
First off, I recently moved house which took a fair amount of time and effort to get packed / unpacked and have DSL connected at my new place. In addition to this I’ve had a few Uni assignments which took away even more time. In amongst all this my computer chair broke… I’ve purchased a new chair which won’t arrive for another 4 – 8 weeks. The dining chair I’m using in the mean time places a lot of strain on my back meaning I can only code for short periods of time.
Secondly, I’ve put a lot of work into making Twaddle a lot faster. On my HTC Touch Pro rotating the screen redraws virtually straight away and Twaddle continues to be responsive throughout the whole process. A vastly improved algorithm for laying out tweets (50 tweets get laid out in ~150ms on my phone) as well as moving non-visible layouts to a background process ensures Twaddle remains responsive throughout rotations. I’m still working on improving the speed of performing updates.
Long story short: 0.2 won’t be released as soon as I’d hoped as I’m putting a lot of work into it to ensure it far eclipses previous versions of Twaddle.
I use the Samsung Omnia and I’m still getting text Tweets until I know this works fully. I’m only getting about half of the tweets through Twaddle. What’s up with this?
What refresh interval and statuses to display do you have set? And is the number of tweets you’re expecting greater than the number of statuses to display?
When Twaddle grabs data from the Twitter servers it asks for the statuses-to-display most recent items for that view (eg. Your friends timeline). Once it’s grabbed these items it remembers the most recent item and the next time it updates it requests the statuses-to-display most recent items that are newer than the most recent one it knows about. If you have statuses to display set to be 20 and refresh every 10 minutes, but typically get 30 tweets / 10 minutes then you’ll miss the first 10 tweets for that period. This is because the Twitter servers return the data in reverse-order. What you can try doing is increasing the number of statuses to display or lowering the refresh interval. I’d recommend leaving the refresh interval as it will impact battery life.
To be honest – this isn’t an issue I’ve come across before, but I’ll throw it in my to-do list and see if I can do something about “filling in the holes” as it were.
I HAD the intervals set at 5 minutes and was saying to show 200 posts and only had 143. I think I’m going to switch back to Pocketwit, this is becoming increasingly difficult to use. I think you have a good product but unless you can get your 0.2 out more quickly (fixing bugs) I’m not sure you have much of a chance against the others–which is too bad, your concept of BASIC functions and GUI is EXACTLY what I was looking for.
Can you give me some more information about the tweets you’re not getting? Are they missing from your friends timeline? Do you get them with other clients? How many people are you following? Would you be able to send me the files from the Logs/ subdirectory of where you installed Twaddle to? You can mail it to support@twaddle.mobi