TweetDeck v0.15.1b Details
Version 0.15.1 of TweetDeck is complete. This is a point release which contains no new features instead it introduces fixes for a number of UI/Window related bugs and a more efficient method of gathering data from Summize. The details are below.
Clicking on the "+" button whilst maximised will now restore the TweetDeck back to its original size and position.
In the top right corner of the window you will now see two new buttons. One has a "1" on it and clicking on this will switch TweetDeck to a one column view. Clicking on the "1" button again with restore TweetDeck to its original width. The other new button has an "r" on it and this is the window reset button. Clicking on this will reset TweetDeck to the initial size and position it when when first installed. You can use this button to get out of any window related difficulties. This button is rather ugly in this position so I will be moving it to the settings panel (yes there is a full setting panel on the way) and this command will also be available from the task bar/dock.
Direct Messages now have their own column and will no longer show up in the Replies column. There is a DIRECT button in the button bar at the top which when clicked adds the Direct Messages column. This column has been added to the default set of columns for new users.
The maximum timeframe has been reduced from 168 to 48 hours. With the introduction of Global Search columns (powered by Summize) a user could potentially have 9 columns each containing thousands of tweets - TweetDeck can easily cope with this volume whilst running but there could be an impact on the application load time when started. This is a "preemptive strike" whilst I investigate how to make the application initialisation more palletable.
When the TweetDeck window goes below a certain width there is now a new single column version of the Tweet panel. The TWEET button is now also present making it easier to use TweetDeck in a minimal one column mode.
On Saturday there was a brief period when multiple copies of queued tweets (either from offline or twitter problem modes) were sent out. I investigated the issue at length with Cali Lewis (@calilewis) since she could recreate the issue quite easily. I could find no definite cause for this but suspect it may have something to do with the HTTP response code that is sent back from the twitter API, especially since it does not appear to have happened since. Whatever the cause this is unacceptable so I have decided to pull offline tweeting from TweetDeck until a more robust solution can be found. I do not anticipate this being very long.
Finally the API calls used to get data from Summize have been made more efficient, at their suggestion, so as to reduce unnecessary load on the Summize infrastructure and to make the updates more efficient within TweetDeck.
TweetDeck v0.15.2 now in development.
