News
October 2009 : a new release (bibus 1.5.0)
- OOo3.1 compatibility
- Infinite number of file/http links
- Clever capitalization (lord of war => Lord of War ...)
- Better handling of journal abbreviations
- Import/Export filters can be added easily (plugin)
- journal abbreviations and shortcuts can be easily edited (simple csv file that can be edited in OOo/excel or a text editor)
- Lot of bug fixes
- Requires python2.5 (not a problem anymore under Windows since OOo3.1 includes 2.6)
- Requires wxpython-2.8
Towards a Bibus application bundle on Mac OS X 10.5 or later
From Bibus
This document lists the current status of our effort working towards a "real" Mac OS X application bundle for Bibus.
Contents |
In short
- Development of Bibus for Mac paused
- Help wanted from real Mac developers, in particular those working with Python/wxpython
Full
The development of Bibus for Mac is hindered by the limited access to Macintosh computers that we currently have. Initially, this seemed not a big problem, since Bibus seemed to run almost 'out of the box' and it was thought that constructing a proper Application Bundle was simple. Development could be done on Linux, and then just tested on Mac. However, on normal use on Macintosh, Bibus displays some annoying glitches. Moreover, the construction of an installer will require some experimentation.
Until we will be able to organise some more serious (time-demanding) experimentation on Mac OS X, the development of a first version for Mac will be on hold.
We will first focus on a Bibus for Mac OS X 10.5 (Leopard) and later, because OSX 10.5 already includes working versions of Python 2.5 and wxpython 2.8.
The preferred distribution format will be that of an “Application Bundle”, which is a folder containing all of the program's files, but which appears as a single Application in the Finder. It can be placed anywhere in the user's file system, but most users will put it in the “Applications” folder. The bundle/application can be run by simply double-clicking on it.
Before choosing the technological strategy, several questions still need to be answered.
1. Use the built-in Python and wxpython of Mac OS X 10.5 or use a separate, more recent MacPython installation?
On many Python web-sites, use of a separate MacPython is strongly encouraged, but it would of course be simpler to use the built-in Python. Bibus 1.5rc (CVS) seems to run on built-in Python, but with several glitches. We should first test Bibus with a separate MacPython and wxpython from the official Python site.
2. Is an Application Bundle the best way to distribute Bibus?
Since Bibus relies on Python, it is not clear how the Application Bundle will be composed. Which libraries/items from Python need to be included in the Bundle? Normally py2app will take care of this. But this should be tested.
It does not seem a good idea to construct an Application Bundle 'by hand' without using tools. At first this appeared an interesting option, but when the Application is Python code, this is not trivial.
There is also the possibility to include Bibus in MacPorts or Fink, which are OS X package managers comparable to APT or RPM.
