This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: BottomFeeder 3.4 nears
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
The 3.4 release of BottomFeeder is fast approaching. There have been a lot of nice improvements and bug fixes; the UI is much cleaner now. The documentation for 3.4is almostready (Thanks Rich!). Expect a push around the end of the month or the beginning of March. Here's what's changed:
Simplified the user interface - all the view modes are available via toolbar buttons or the menu. Feed icons are moved to properties, and the wasted space at the top of the UI is gone
Downloading upgrades has been made safer via a validity check
Added support for some Atom components in RSS 2.0 feeds as modules
Added Search feeds - synthetic feeds made up of items searched from what has been downloaded into BottomFeeder
Added a Google Feed builder, akin to the Feedster feed builder
Feeds which are parsed with errors will be flagged as such so that end users who wish to notify the producer can do so. For the same purpose, there is an interface to the feed validator at http://www.feedvalidator.org
Added a News Ticker that can be used instead of the 'slim mode' interface.
Modified the application so that all user interface elements respect the text settings of the user.
There's a menu option that can stop an in-process update cycle without taking BottomFeeder offline. Previously, you would have to take the application offline
There is now a Mac OSX installation that installs properly
Fixed a bug that prevented proper startup after an abnormal quit
Added more information to the upgrade screen for the user (sizes and descriptions of the change). Also modified the properties to disallow save on a bad download, and to disallow loading without a restart if that would be inadvisable (in the case of UI changes, for instance).
Browsing options could have different behavor depending on how the option was selected; this has been cleaned up and unified
Previous Topic
