“I honestly don’t recall why I picked that particular name. I had it in mind as a codename for many years and when it came to pick a name for a newsreader, it simply stood out and the name stuck. And, yes, I am aware that Microsoft later picked Vienna as the codename for their successor to Vista.
See the Development page for instructions on getting the source code for Vienna. The source code is freely available if you’re interested in learning how Vienna works, if you want to build your own copy of Vienna from scratch on your own machine or if you want to borrow portions for inclusion in your own project. The source is provided under the Apache 2.0 license.
Create a new issue over at our GitHub site, or post a message over in the forum and somebody will investigate. Provide as much information about the problem as you can including: the build of Vienna (obtained from the About Vienna panel), steps to reproduce and what you expected to happen. If the problem occurs with a specific news feed, always include the URL of the feed. It is easier to fix problems that we can reproduce.
Make sure you’re always running the most recent build of Vienna. The Check for Updates command will report if there’s a newer build available than the one you have.
Fixes for bugs take priority over new features so if your problem is confirmed to be a bug with high impact and no simple workaround then we’ll look at making a fix available as soon as reasonably possible.
See the Custom Styles page for instructions.
Vienna’s scripts are written using AppleScript. See the Apple resource page for more details. Also take a look at the Vienna scripting dictionary and examples of what you can accomplish.
To submit your own script, create a post about it in the forum and after it has been reviewed, it will be made available on the Downloads page.
You can create plugins as easily as editing a single plugin file and no scripting needed. See the Creating Plugins page for more details. You can also package and share your plugins with others on the forum.
Open the Activity Window from the Window menu. The activity window shows all subscriptions and the status of the last time they were refreshed in that session. The bottom of the activity window shows more details include the HTTP headers and may be useful for debugging. (If the details pane is not visible, grab the split bar at the bottom of the Activity Window and drag it up to uncover the pane).
By default, your Vienna database is the messages.db file which is located at ~/Library/Application Support/Vienna. You can move this to another folder if you wish. The following steps show how:
defaults write uk.co.opencommunity.vienna2 "DefaultDatabase" '<path to new messages.db>'
<path to new messages.db> is the name of the folder that contains the messages.db file. The path itself should have the messages.db filename at the end.
For example: `defaults write uk.co.opencommunity.vienna2 "DefaultDatabase" '/Users/steve/mydata/messages.db'` 3. Restart Vienna.
It means that Vienna got a feed back from the subscription that it couldn’t interpret. There are several reasons for this:
If none of the above explain the problem, post a message on the support forum with the URL of the feed exhibiting the problem.
Probably. There are single key equivalents for some of the menu commands such as:
Look in the Vienna Help file for more shortcuts.
Auto-expire moves articles older than a certain number of days to the Trash folder. It allows you to keep your folders manageable by only retaining articles that are recent. The auto-expire runs both when Vienna starts and after you have refreshed any subscriptions. To control the age of articles to auto-expire, change the “Expire articles older than” option in Preferences.
Auto-expire will NOT remove unread or flagged articles. It assumes that you haven’t read these articles and thus leaves them alone.
Create a new issue over at our GitHub site, or post a message over at the support forum. All requested enhancements are logged in the TODO file that is included with the source code as a guidance for future developers.