I was planning to get RC #2 out a bit earlier but my back has decided to raise hell with me. I’m actually active and healthy but every once and a while I manage to do something that lays me out. However, I’ve managed to stay vertical for the last couple of hours and so I’ve packaged up the latest fixes. Hopefully there are no bad regressions.
- Ignore bad data. Twitter occasionally sends ill formatted data. Tweetz will ignore the bad data instead of crashing
- Fix the purge old tweets routine to correctly delete the old tweets
- Fix url parsing to align more closely with how twitter parses urls (exclude trailing ? for instance)
- Fix misspelling of messages in “Unified” tool tip
Excellent bug hunting guys. Also, the suggestions are great. I’ve added them to the bottom of app.js so you can see which ones I’m aware of.
Available on the downloads page.
Hey, it’s almost done. All that’s left to do is to write a new Web page and documentation. That will take an evening or two. In the mean time, here are the release bits barring some major bug. I’m anxious to get started on 3.1 so it’s time to stick a fork in it.
What’s new:
- Direct messages sent were displaying the author instead of the recipient
- Hover indicator on tabs
- Parse hashtags, @names and urls more like twitter
- Purge old tweets
Parsing hashtags, @names and urls like twitter was way more work than I expected. It’s not at all obvious what the rules are for parsing these items. Fortunately, twitter recently published their text parsing code. It’s in Ruby which I only have a passing knowledge of. Translating to JavaScript was a chore I’m glad to have behind me. There’s also a test description in YAML. One of these days I’ll have to code up some tests to verify the code.
I’ve capped each timeline at 250 tweets (the unified timeline is the sum of all timelines). Tweetz 2.3.5 did something similar.
Available on the downloads page.
previous | next
powered by Bloget™