If you ran the
devinstall installation instructions, you have downloaded
the sources, connected to the github repository. You are in the ideal
situation to start looking into the software, understand how it works,
contribute to ghini.desktop’s development.
Helping Ghini development¶
If you want to contribute to Ghini, you can do so in quite a few different ways:
- Use the software, note the things you don’t like, open an issue for each of them. A developer will react sooner than you can imagine.
- If you have an idea of what you miss in the software but can’t quite formalize it into separate issues, you could consider hiring a professional. This is the best way to make sure that something happens quickly on Ghini. Do make sure the developer opens issues and publishes their contribution on github.
- Translate! Any help with translations will be welcome, so please do! you can do this without installing anything on your computer, just using the on-line translation service offered by http://hosted.weblate.org/
- fork the respository, choose an issue, solve it, open a pull request. See the bug solving workflow below.
If you haven’t yet installed Ghini, and want to have a look at its code history, you can open our github project page and see all that has been going on around Ghini since its inception as Bauble, back in the year 2004.
If you install the software according to the
you have the whole history in your local git clone.
Software source, versions, branches¶
If you want a particular version of Ghini, we release and maintain versions
as branches. You should
git checkout the branch corresponding to the
version of your choice.
Branch names for Ghini stable (production) versions are of the form
ghini-x.y (eg: ghini-1.0); branch names where Ghini testing versions are
published are of the form
ghini-x.y-dev (eg: ghini-1.0-dev).
Our workflow is to continuously commit to the testing branch, to often push them to github, to let travis-ci and coveralls.io check the quality of the pushed testing branches, finally, from time to time, to merge the testing branch into the corresponding release.
When working at larger issues, which seem to take longer than a couple of days, I might open a branch associated to the issue. I don’t do this very often.
When facing a single larger issue, create a branch tag at the tip of a main
development line (e.g.:
ghini-1.0-dev), and follow the workflow
git up git checkout -b issue-xxxx git push origin issue-xxxx
Work on the new temporary branch. When ready, go to github, merge the branch with the main development line from which you branched, solve conflicts where necessary, delete the temporary branch.
When ready for publication, merge the development line into the corresponding production line.
Updating the set of translatable strings¶
From time to time, during the process of updating the software, you will be
adding or modifying strings in the python sources, in the documentation, in
the glade sources. Most of our strings are translatable, and are offered to
weblate for people to contribute, in the form of several
po is mostly composed of pairs of text portions, original and
translation, and is specific to a target language. When a translator adds a
translation on weblate, this reaches our repository on github. When a
programmer adds a string to the software, this reaches weblate as “to be
Weblate hosts the Ghini project. Within this project we have components, each of which corresponds to a branch of a repository on github. Each component accepts translations in several languages.
To update the
po files relative to the software, you set the working
directory to the root of your checkout of ghini.desktop, and you run the
To update the
po files relative to the documentation, you set the
working directory to the root of your checkout of ghini.desktop-docs.i18n,
and you run the script:
When you run either of the above mentioned scripts, chances are you need to
po files in the project. You may want to review the changes
before committing them to the respository. This is most important when you
perform a marginal correction to a string, like removing a typo.
Something that happens: running into a conflict. Solving conflicts is not difficult once you know how to do that. First of all, add weblate as remote:
git remote add weblate-doc10 https://hosted.weblate.org/git/ghini/documentation-10/
Then make sure we are in the correct repository, on the correct branch, update the remote, merge with it:
git checkout ghini-1.0-dev git remote update git merge weblate-doc10/ghini-1.0-dev
Readthedocs checks the project’s Language setting, and invokes
sphinx-intl to produce the formatted documentation in the target
language. With the default configuration —which we did not alter—
sphinx-intl expects one
po file per source document, named as the
source document, and that they all reside in the directory
On the other hand, Weblate (and ourselves) prefers a single
po file per
language, and keeps them all in the same
/po directory, just as we do
for the software project:
In order not to repeat information, and to let both systems work their natural way, we have two sets of symbolic links (git honors them).
To summarise: when a file in the documentation is updated, the
- copy the
rstfiles from the software to the documentation;
- create a new
potfile for each of the documentation files;
- merge all
potfiles into one
- use the updated
doc.potto update all
doc.pofiles (one per language);
- create all symbolic links:
- those expected by
- those used by weblate in
- those expected by
We could definitely write the above in a Makefile, or even better include it
/doc/Makefile. Who knows, maybe we will do that.
Which way do the translated strings reach our users?¶
A new translator asked the question, adding: »Is this an automated process from Weblate –> GIT –> Ghini Desktop installed on users computers, or does this require manual steps?
The aswer is that the whole interaction is quite complex, and it depends on the component.
When you install
ghini.desktop or one of the Android apps, the
installation doesn’t assume a specific run-time language: a user can change
their language configuration any time. So what we do is to install the
software in English together with a translation table from English to
At run-time the GUI libraries (Android or GTK) know where to look for the translation strings. These translation tables are generated during the installation or upgrade process, based on the strings you see on Weblate.
The path followed by translations is: You edit strings on Weblate, Weblate
keeps accumulating them until you are done, or you don’t interact with
Weblate for a longer while; Weblate pushes the strings to github, directly
into the development line
ghini-1.0-dev; I see them and I might blindly
trust or prefer to review them, maybe I look them up in wikipedia or get
them translated back to Italian, Spanish or English by some automatic
translation service; sometimes I need to solve conflicts arising because of
changed context, not too often fortunately. As said, this lands in the
ghini-1.0-dev, which I regularly publish to the
ghini-1.0, and this is the moment when the new
translations finally make it to the distributed software.
Users will notice a new version available warning and can decide to ignore it, or to update.
ghini.pocket, it is similar, but the notification is handled by the
Android system. We publish on the Play Store, and depending on your
settings, your phone will update the software automatically, or only notify
you, or do nothing. It depends on how you configured automatic updates.
ghini.web, we haven’t yet defined how to distribute it.
For ghini’s documentation, it’s completely automatic, and all is handled by readthedocs.org.
Adding missing unit tests¶
If you are interested contributing to development of Ghini, a good way to do so would be by helping us finding and writing the missing unit tests.
A well tested function is one whose behaviour you cannot change without breaking at least one unit test.
We all agree that in theory theory and practice match perfectly and that one first writes the tests, then implements the function. In practice, however, practice does not match theory and we have been writing tests after writing and even publishing the functions.
This section describes the process of adding unit tests for
What to test¶
First of all, open the coverage report index, and choose a file with low coverage.
For this example, run in October 2015, we landed on
bauble.plugins.plants.family, at 33%.
The first two functions which need tests,
add_genera_callback, include creation and activation of an object
relying on a custom dialog box. We should really first write unit tests for
that class, then come back here.
The next function,
remove_callback, also activates a couple of dialog
and message boxes, but in the form of invoking a function requesting user
input via yes-no-ok boxes. These functions we can easily replace with a
function mocking the behaviour.
how to test¶
So, having decided what to describe in unit test, we look at the code and we see it needs discriminate a couple of cases:
- parameter correctness
- the list of families has no elements.
- the list of families has more than one element.
- the list of families has exactly one element.
- the family has no genera
- the family has one or more genera
- the user confirms deletion
- the user does not confirm deletion
- all goes well when deleting the family
- there is some error while deleting the family
I decide I will only focus on the cascade and the confirm aspects. Two binary questions: 4 cases.
where to put the tests¶
Locate the test script and choose the class where to put the extra unit tests.
what about skipped tests
FamilyTestsclass contains a skipped test, implementing it will be quite a bit of work because we need rewrite the FamilyEditorPresenter, separate it from the FamilyEditorView and reconsider what to do with the FamilyEditor class, which I think should be removed and replaced with a single function.
writing the tests¶
After the last test in the FamilyTests class, I add the four cases I want to describe, and I make sure they fail, and since I’m lazy, I write the most compact code I know for generating an error:
def test_remove_callback_no_genera_no_confirm(self): 1/0 def test_remove_callback_no_genera_confirm(self): 1/0 def test_remove_callback_with_genera_no_confirm(self): 1/0 def test_remove_callback_with_genera_confirm(self): 1/0
One test, step by step¶
Let’s start with the first test case.
When writing tests, I generally follow the pattern:
- T₀ (initial condition),
- T₁ (testing the result of the action given the initial conditions)
what’s in a name — unit tests
There’s a reason why unit tests are called unit tests. Please never test two actions in one test.
So let’s describe T₀ for the first test, a database holding a family without genera:
def test_remove_callback_no_genera_no_confirm(self): f5 = Family(family=u'Arecaceae') self.session.add(f5) self.session.flush()
We do not want the function being tested to invoke the interactive
utils.yes_no_dialog function, we want
remove_callback to invoke a
non-interactive replacement function. We achieve this simply by making
utils.yes_no_dialog point to a
lambda expression which, like the
original interactive function, accepts one parameter and returns a
boolean. In this case:
def test_remove_callback_no_genera_no_confirm(self): # T_0 f5 = Family(family=u'Arecaceae') self.session.add(f5) self.session.flush() # action utils.yes_no_dialog = lambda x: False from bauble.plugins.plants.family import remove_callback remove_callback(f5)
Next we test the result.
Well, we don’t just want to test whether or not the object Arecaceae was
deleted, we also should test the value returned by
message_details_dialog were invoked or
lambda expression is not enough for this. We do something apparently
more complex, which will make life a lot easier.
Let’s first define a rather generic function:
def mockfunc(msg=None, name=None, caller=None, result=None): caller.invoked.append((name, msg)) return result
and we grab
partial from the
functools standard module, to partially
apply the above
mockfunc, leaving only
msg unspecified, and use this
partial application, which is a function accepting one parameter and
returning a value, to replace the two functions in
utils. The test
function now looks like this:
def test_remove_callback_no_genera_no_confirm(self): # T_0 f5 = Family(family=u'Arecaceae') self.session.add(f5) self.session.flush() self.invoked =  # action utils.yes_no_dialog = partial( mockfunc, name='yes_no_dialog', caller=self, result=False) utils.message_details_dialog = partial( mockfunc, name='message_details_dialog', caller=self) from bauble.plugins.plants.family import remove_callback result = remove_callback([f5]) self.session.flush()
The test section checks that
message_details_dialog was not invoked,
yes_no_dialog was invoked, with the correct message parameter, that
Arecaceae is still there:
# effect self.assertFalse('message_details_dialog' in [f for (f, m) in self.invoked]) self.assertTrue(('yes_no_dialog', u'Are you sure you want to ' 'remove the family <i>Arecaceae</i>?') in self.invoked) self.assertEquals(result, None) q = self.session.query(Family).filter_by(family=u"Arecaceae") matching = q.all() self.assertEquals(matching, [f5])
And so on¶
there are two kinds of people, those who complete what they start, and so on
Next test is almost the same, with the difference that the
utils.yes_no_dialog should return
True (this we achieve by
result=True in the partial application of the generic
With this action, the value returned by
remove_callback should be
True, and there should be no Arecaceae Family in the database any more:
def test_remove_callback_no_genera_confirm(self): # T_0 f5 = Family(family=u'Arecaceae') self.session.add(f5) self.session.flush() self.invoked =  # action utils.yes_no_dialog = partial( mockfunc, name='yes_no_dialog', caller=self, result=True) utils.message_details_dialog = partial( mockfunc, name='message_details_dialog', caller=self) from bauble.plugins.plants.family import remove_callback result = remove_callback([f5]) self.session.flush() # effect self.assertFalse('message_details_dialog' in [f for (f, m) in self.invoked]) self.assertTrue(('yes_no_dialog', u'Are you sure you want to ' 'remove the family <i>Arecaceae</i>?') in self.invoked) self.assertEquals(result, True) q = self.session.query(Family).filter_by(family=u"Arecaceae") matching = q.all() self.assertEquals(matching, )
have a look at commit 734f5bb9feffc2f4bd22578fcee1802c8682ca83 for the other two test functions.
bauble.test.BaubleTestCase objects use handlers of the class
bauble.test.MockLoggingHandler. Every time an individual unit test is
setUp method will create a new
handler and associate it
to the root logger. The
tearDown method takes care of removing it.
You can check for presence of specific logging messages in
messages is a dictionary, initially empty,
with two levels of indexation. First the name of the logger issuing the
logging record, then the name of the level of the logging record. Keys are
created when needed. Values hold lists of messages, formatted according to
whatever formatter you associate to the handler, defaulting to
You can explicitly empty the collected messages by invoking
Putting all together¶
From time to time you want to activate the test class you’re working at:
And at the end of the process you want to update the statistics:
Structure of user interface¶
The user interface is built according to the Model — View — Presenter architectural pattern. For much of the interface, Model is a SQLAlchemy database object, but we also have interface elements where there is no corresponding database model. In general:
The View is described as part of a glade file. This should include the signal-callback and ListStore-TreeView associations. Just reuse the base class
bauble.editor. When you create your instance of this generic class, pass it the glade file name and the root widget name, then hand this instance over to the presenter constructor.
In the glade file, in the
action-widgetssection closing your GtkDialog object description, make sure every
action-widgetelement has a valid
responsevalue. Use valid GtkResponseType values, for example:
- GTK_RESPONSE_OK, -5
- GTK_RESPONSE_CANCEL, -6
- GTK_RESPONSE_YES, -8
- GTK_RESPONSE_NO, -9
There is no easy way to unit test a subclassed view, so please don’t subclass views, there’s really no need to.
In the glade file, every input widget should define which handler is activated on which signal. The generic Presenter class offers generic callbacks which cover the most common cases.
- GtkEntry (one-line text entry) will handle the
changedsignal, with either
- GtkTextView: associate it to a GtkTextBuffer. To handle the
changedsignal on the GtkTextBuffer, we have to define a handler which invokes the generic
on_textbuffer_changed, the only role for this function is to pass our generic handler the name of the model attribute that receives the change. This is a workaroud for an unresolved bug in GTK.
- GtkComboBox with translated texts can’t be easily handled from the glade
file, so we don’t even try. Use the
init_translatable_combomethod of the generic
GenericEditorViewclass, but please invoke it from the presenter.
The Model is just an object with known attributes. In this interaction, the model is just a passive data container, it does nothing more than to let the presenter modify it.
The subclassed Presenter defines and implements:
widget_to_field_map, a dictionary associating widget names to name of model attributes,
view_accept_buttons, the list of widget names which, if activated by the user, mean that the view should be closed,
- all needed callbacks,
- optionally, it plays the model role, too.
The presenter continuously updates the model according to changes in the view. If the model corresponds to a database object, the presenter commits all model updates to the database when the view is closed successfully, or rolls them back if the view is canceled. (this behaviour is influenced by the parameter
If the model is something else, then the presenter will do something else.
A well behaved presenter uses the view api to query the values inserted by the user or to forcibly set widget statuses. Please do not learn from the practice of our misbehaving presenters, some of which directly handle fields of
view.widgets. By doing so, these presenters prevents us from writing unit tests.
The base class for the presenter,
GenericEditorPresenter defined in
bauble.editor, implements many useful generic callbacks. There is a
MockView class, that you can use when writing tests for your presenters.
ContactPresenter are implemented following the above
lines. The view is defined in the
A good example of Presenter/View pattern (no model) is given by the connection manager.
We use the same architectural pattern for non-database interaction, by
setting the presenter also as model. We do this, for example, for the JSON
export dialog box. The following command will give you a list of
grep -nHr -e GenericEditorView\( bauble
Extending Ghini with Plugins¶
Nearly everything about Ghini is extensible through plugins. Plugins can create tables, define custom searchs, add menu items, create custom commands and more.
To create a new plugin you must extend the
Tag plugin is a good minimal example, even if the
falls outside the Model-View-Presenter architectural pattern.
Ghini is a framework for handling collections, and is distributed along with a set of plugins making Ghini a botanical collection manager. But Ghini stays a framework and you could in theory remove all plugins we distribute and write your own, or write your own plugins that extend or complete the current Ghini behaviour.
Once you have selected and opened a database connection, you land in the Search window. The Search window is an interaction between two objects: SearchPresenter (SP) and SearchView (SV).
SV is what you see, SP holds the program status and handles the requests you express through SV. Handling these requests affect the content of SV and the program status in SP.
The search results shown in the largest part of SV are rows, objects that are instances of classes registered in a plugin.
Each of these classes must implement an amount of functions in order to properly behave within the Ghini framework. The Ghini framework reserves space to pluggable classes.
SP knows of all registered (plugged in) classes, they are stored in a dictionary, associating a class to its plugin implementation. SV has a slot (a gtk.Box) where you can add elements. At any time, at most only one element in the slot is visible.
A plugin defines one or more plugin classes. A plugin class plays the role of a partial presenter (pP - plugin presenter) as it implement the callbacks needed by the associated partial view fitting in the slot (pV - plugin view), and the MVP pattern is completed by the parent presenter (SP), again acting as model. To summarize and complete:
- SP acts as model,
- the pV partial view is defined in a glade file.
- the callbacks implemented by pP are referenced by the glade file.
- a context menu for the SP row,
- a children property.
when you register a plugin class, the SP:
- adds the pV in the slot and makes it non-visible.
- adds an instance of pP in the registered plugin classes.
- tells the pP that the SP is the model.
- connects all callbacks from pV to pP.
when an element in pV triggers an action in pP, the pP can forward the action to SP and can request SP that it updates the model and refreshes the view.
When the user selects a row in SP, SP hides everything in the pluggable slot and shows only the single pV relative to the type of the selected row, and asks the pP to refresh the pV with whatever is relative to the selected row.
Apart from setting the visibility of the various pV, nothing needs be disabled nor removed: an invisible pV cannot trigger events!
bug solving workflow¶
normal development workflow¶
- while using the software, you notice a problem, or you get an idea of something that could be better, you think about it good enough in order to have a very clear idea of what it really is, that you noticed. you open an issue and describe the problem. someone might react with hints.
- you open the issues site and choose one you want to tackle.
- assign the issue to yourself, this way you are informing the world that you have the intention to work at it. someone might react with hints.
- optionally fork the repository in your account and preferably create a branch, clearly associated to the issue.
- write unit tests and commit them to your branch (please do not push
failing unit tests to github, run
- write more unit tests (ideally, the tests form the complete description of the feature you are adding or correcting).
- make sure the feature you are adding or correcting is really completely described by the unit tests you wrote.
- make sure your unit tests are atomic, that is, that you test variations on changes along one single variable. do not give complex input to unit tests or tests that do not fit on one screen (25 lines of code).
- write the code that makes your tests succeed.
- update the i18n files (run
- whenever possible, translate the new strings you put in code or glade files.
- when you change strings, please make sure that old translations get re-used.
- commit your changes.
- push to github.
- open a pull request.
publishing to production¶
please use the
publish.sh script, in the
scritps directory. This
one takes care of every single step, and produces recognizable commit
comments, it publishes the release on pypi, and in perspective it will
contain all steps for producing a
deb file, and a windows executable.
you can also do this by hand:
- open the pull request page using as base a production line
ghini-x.y, compared to
- make sure a
bumpcommit is included in the differences.
- it should be possible to automatically merge the branches.
- create the new pull request, call it as “publish to the production line”.
- you possibly need wait for travis-ci to perform the checks.
- merge the changes.
your own fork¶
If you want to keep your own fork of the project, keep in mind this is full force work in progress, so staying up to date will require some effort from your side.
The best way to keep your own fork is to focus on some specific issue, work relatively quickly, often open pull requests for your work, make sure that you get it accepted. Just follow Ghini’s coding style, write unit tests, concise and abundant, and there should be no problem in having your work included in Ghini’s upstream.
- review this workflow. consider this as a guideline, to yourself and to your colleagues. please help make it better and matching the practice.
Python Package Index - PyPI¶
This is not much mentioned, but we keep ghini.desktop on the Python Package Index, so you could install it by no more than:
pip install ghini.desktop
There are a couple packages that can’t be installed with
otherwise that’s really all you need to type, and it’s platform independent.
Publishing on PyPI is a standard
python setup.py sdist --formats zip upload -r pypi
For building a Windows installer or executable you need a running Windows system. The methods described here has been used successfully on Windows 7, 8 and 10. Windows Vista should also work but has not been tested.
If you are on GNU/Linux, or on OSX, you are not interested in the remainder of this section. None of Ghini’s contributors knows how to produce a Windows installer without having a Windows system.
The goal of the present instructions is to help you produce a Windows installer, that is a single executable that you can run on any Windows workstation and that will install a specific version of ghini.desktop. This is achieved with the NSIS script-driven installer authoring tool.
As a side product of the installer production, you will have a massive but relocatable directory, which you can copy to a USB drive and which will let you use the software without needing an installation.
The files and directories relevant to this section:
scripts/build-win.bat— the single batch script to run.
setup.py— implements the NSIS and py2exe commands.
scripts/build-multiuser.nsi— the nsis script, used by the above.
nsis/— contains redistributable NSIS files, put here for conveniency.
ghini-runtime/— built by
py2exe, used by
dist/— receives the executable installation file.
Most steps are automated in the
build-win.bat script. Installation of a few
tools needs to be done manually:
Download and install Git, Python 2.7 and PyGTK.
This is outlined in the
devinstall-based installation instructions.
Download and install NSIS v3.
A reboot is recommended.
Clone the ghini.desktop repository.
Use your own fork if you plan contributing patches, or the organization’s repository
https://github.com/Ghini/ghini.desktop.gitif you only wish to follow development.
Clone the repository from GitHub to wherever you want to keep it, and checkout a branch. Replace
<path-to-keep-ghini>with the path of your choice, e.g.
Local\github\Ghini\. Production branch
ghini-1.0is recommended as used in the example.
To do this, open a command prompt and type these commands:
cd <path-to-keep-ghini> git clone <ghini.desktop repository URL> cd ghini.desktop git checkout ghini-1.0
The result of the above is a complete development environment, on Windows, with NSIS. Use it to follow development, or to propose your pull requests, and to build Windows installers.
All subsequent steps are automated in the
scripts\build_win.bat script. Run
it, and after a couple of minutes you should have a new
dist\ghini.desktop-<version>-setup.exe file, and a working, complete
relocatable directory named
Read the rest if you need details about the way the script works.
A batch file is available that can complete the last few steps. To use it use this command:scripts\build_win.bat
build_win.bataccepts 2 arguments:
/e— executable only.
Produce an executable only, skipping the extra step of building an installer, and will copy
venv_path— A path to the location for the virtual environment to use.
CHECKOUTcorresponds to the name of the branch you checked out.
If you want to produce an executable only and use a virtual environment in a folder beside where you have ghini.desktop, you could execute
scripts\build_win.bat /e ..\ghi2exe
py2exe will not work with eggs
Building a Windows executable with py2exe requires packages not be installed as eggs. There are several methods to accomplish this, including:
pip. The easiest method is to install into a virtual environment that doesn’t currently have any modules installed as eggs using
pip install .as described below. If you do wish to install over the top of an install with eggs (e.g. the environment created by
devinstall.bat) you can try
pip install -I .but your mileage may vary.
By adding:[easy_install] zip_ok = False
to setup.cfg (or similarly
zip_safe = Falseto
setup.py) you can use
python setup.py installbut you will need to download and install Microsoft Visual C++ Compiler for Python 2.7 to get any of the C extensions and will need a fresh virtual environment with no dependent packages installed as eggs.
build-winscript uses the
installing virtualenv and working with environments
Install virtualenv, create a virtual environment and activate it.
With only Python 2.7 on your system (where
<path-to-venv>is the path to where you wish to keep the virtual environment) use:pip install virtualenv virtualenv --system-site-packages <path-to-venv> call <path-to-venv>\Scripts\activate.bat
On systems where Python 3 is also installed you may need to either call pip and virtualenv with absolute paths, e.g.
C:\Python27\Scripts\pipor use the Python launcher e.g.
py -2.7 -m pip(run
python --versionfirst to check. If you get anything other than version 2.7 you’ll need to use one of these methods.)
Populate the virtual environment
Install dependencies and ghini.desktop into the virtual environment:pip install psycopg2 Pygments py2exe_py2 pip install .
Compile for Windows
Build the executable:python setup.py py2exe
ghini-runtimefolder will now contain a full working copy of the software in a frozen, self contained state.
This folder is what is packaged by NSIS.
This same folder can also be transferred however you like and will work in place. (e.g. placed on a USB flash drive for demonstration purposes or copied manually to
C:\Program Fileswith a shortcut created on the desktop). To start ghini.desktop double click
ghini.exein explorer (or create a shortcut to it).
Fixing paths to GTK components.
If you run the relocatable compiled program, unpackaged, you might occasionally have trouble with the GUI not displaying correctly.
Should this happen, you need to set up paths to the GTK components correctly. You can do this by running the
win_gtk.bat, from the
You will only need to run this once each time the location of the folder changes. Thereafter
ghini.exewill run as expected.
Finally, invoke NSIS
Build the installer:python setup.py nsis
This should leave a file named
distfolder. This is your Windows installer.
about the installer
Capable of single user or global installs.
At this point in time ghini.desktop installed this way will not check or or notify you of any updated version. You will need to check yourself.
Capable of downloading and installing optional extra components:
- Apache FOP - If you want to use xslt report templates install FOP. FOP requires Java Runtime. If you do not currently have it installed the installer will let you know and offer to open the Oracle web site for you to download and install it from.
- MS Visual C runtime - You most likely don’t need this but if you have any trouble getting ghini.desktop to run try installing the MS Visual C runtime (e.g. rerun the installer and select this component only).
Can be run silently from the commandline (e.g. for remote deployment) with the following arguments:
/AllUser(when run as administrator) or
/C=[gFC]to specify components where:
g= Deselect the main ghini.desktop component (useful for adding optional component after an initial install)
F= select Apache FOP
C= select MS Visual C runtime
Between 2009 and 2010 someone packaged the then already obsolete Bauble 0.9.7 for Debian, and the package was included in Ubuntu. That version is still being distributed, regardless being it impossible to install.
Only recently has Mario Frasca produced a new bauble debian package, for the
latest bauble.classic version 1.0.56, and proposed for inclusion in Debian.
View it on mentors. This
version depends on
fibra, a package that was never added to Debian and
which Mario also has packaged and proposed for inclusion in Debian. Mario has been trying to
activate some Debian Developer, to take action. There’s not much more we can
do, other than wait for a sponsor, and hoping the package will eventually get
all the way to Ubuntu.
I am not going to explain in a few words the content of several books on
Debian packaging. Please choose your sources. For a very compact idea of
what you’re expected to do, have a look at