![]() Let's start exploring MaxBase features, and how do they work. In this document I will sometimes refer to MaxBase as MB, and to a 'database' (a collection of data organized in fields) as a DB. First of all, let's say that MaxBase doesn't have menus, it has panels. Every button in a panel can lead to another panel, or just execute a command. In the picture below, [ sel all ] will select all of the present records in the DB. Not all the features are available at any time: they show up only when they make sense (i.e. you won't see the 'logout' function if you're not logged in to a database). So, for example, picture number 1 shows the MaxBase standard main panel (one DB loaded) plus the Jukebox plugin. Plugins are external applications which can extend the MaxBase set of features, and show up in the main panel. MaxBase looks for plugins at startup, reading the plugin.ini file (see the plugins.zip - unixplug.zip - macplug.zip files for an example).
|
By defaults, in the main panel you find buttons to perform the following actions:
|
This is the panel you will use the most. Here you find all the functions for data entry and manipulation:
|
In this panel you only find three buttons (plus the one that brings you back to the main panel):
|
The tools panel doesn't contains functions, it is only a placeholder for other panels: (beside hosting the 'About' function which will report your registration information and version of MaxBase)
|
In this panel you will find buttons to perform the following operations:
|
Here you will find options to perform the following tasks on the currently in use database:
|
Here you will find two options:
Please be warned that MaxBase saves (in the current directory) its position so the next time it is started it will show up at the same location, with the same size. Other information saved are colors, fonts (if customized by the user), field on which to order the database and active filter (if any): make this work for you - store your databases in different directories and customize differently each DB look'n'feel! Also, you can select which of the standard MaxBase's functions are to be activated upon MaxBase startup. If MaxBase finds a file called maxbase.mnu then it reads all the strings in it, and labels buttons and text bits after those strings. If a button string is set to '-' (the dash character, without the single-quotes), then that button is disabled. If maxbase.mnu doesn't exist, then the default strings will be used.
The following keyboard shortcuts are active in the list which presents the records:
maxbase.mnu files for Unix and Mac (\n and \r line-terminated) are stored in maxbase.*.unix and maxbase.*.mac where * = a language (eg eng = english or ita = italian). Just copy one of them into maxbase.mnu. All the messages and buttons presented to the user are configurable through the customization of maxbase.mnu ASCII file, and that means also that you can translate maxbase from english to other languages (as examples I've put in this package the english and the italian translations; if you translated MaxBase into another language let me know!). From RXDbase 0.90 on, I started using Taligent's widgets. You can browse your data with the vertical and horizontal scrollbars, and you can also resize the columns width by dragging the column separator in the maint caption for that column.
MaxBase can be given a parameter in the command line: the
name of the database to log in to at startup (trailing .dat
extension NEEDED). E.g.: java MaxBase imgs.dat If you provide a name of a directory (without the trailing \ or /) instead, when you'll bring up the [ login ] dialog the browsing will start from the specified directory. Other parameters are presented in the FAQ section, as part of workarounds for problems. Normally you don't need and don't want those extra parameters. You can expand MaxBase functionalities through the use of plugins. Refer to the plugins packages for more details. (file readme.plugins) The printing functions are provided as a plugin, and must be extracted from the plugin.zip (macplug.zip, unixplug.zip) package. (The plugin.ini file gets read *in the current directory* if it's present); see the FAQ section for a first look at them. |