This page aims to help you get started with Dionysus.
Access to the software is "password-protected". Consequently, the first window asks you to provide a password (and a login for versions >= 1.x).
For versions 0.1 and 0.1.5, there is only a single password which is stored in clear in the file passe.txt.
For higher versions, a login will also be required. This allows to differentiate transactions performed by each registered vendor in the shop, useful for example for student pubs which are run by different teams on different days. Once logged in, logging out is found under File > Change vendor.
Login data is stored in the file called logins.txt, with one line for each vendor using the following pattern login:screen_name:password. All characters are allowed for each field, except of course the separator : . Suggestions to encrypt the password properly with the Java standard library are warmly welcome.
The interface of Dionysus is split between 4 panels:
Releases higher than 0.1.5 will see the additional panel:
For all views, the big text area at the bottom of the screen is meant to display any stock alerts when stock management is used. It will become smaller in versions >= 1.x.
This is meant to be the main view of the software.
For versions < 1.x:
In order to start registering a sale, you must first select the user it will be applied to, or choose 'default' if the user is not registered in the list and does not want/need to create an account. Then you can add items to the ticket by choosing an article, either by clicking on the corresponding button or providing the article code. You will then be prompted to enter the quantity, and choose the correct price if this article has several prices registered. Always follow the instructions provided by the software; not doing so will result in unpredictable behavior, and you will have to restart the software.
At this point, you can choose to add other articles, or close the ticket by selecting the right payment method. There can only be one payment method for a given ticket. After payment is complete, the transactions for each article in the ticket will be stored in the database, inventory will be updated, and the whole ticket edition process can be started again.
There is no possibility to temporarily close a ticket while waiting for the payment.
Both views share the same properties: they list the contents of the corresponding databases. Entries can be filtered using the search box, or by clicking on the column headers. It is also possible to add, delete or modify entries with the provided buttons.
A user has a first name, a last name, a third field corresponding to his/her graduation year (for example), an account balance.
An article has a name, a code (for example the barcode, or any other significant integer). You can use the stock management features so that the software can keep track of the number of units sold, and (if requested) display a warning when the number of units for a given article becomes too low. It will also belong to 0, 1 or more categories. Finally, it can have up to 3 prices (hardcoded number). The original idea was to have a different price depending on the type of customer (member of the student association, non-member, visitor). If you need fewer prices, please start from the beginning (Price #0) and leave unused fields blank (no zeroes please!).
This view displays all transactions performed with the software. Unlike users or articles, transactions cannot be added or edited (this happens indirectly on the Cash desk view), but they can be deleted. You have the possibility to also revert the changes (user balance, number of articles in stock) if needed.