Document Title Here
AET65 API
Version 1.0
idvation GmbH
Otto-Hesse-Straße 19 / T5
Phone +49 6151 9926567
D-64293 Darmstadt
Fax +49 6151 3689296
www.idvation.com
Title Here
Page 8 of 84
Application developers can choose from several approaches on how to deal with the GUI:
•
Use BSGUI.DLL as it is, will guarantee appearance of the applications, consistent with their own
applications.
•
Use BSGUI.DLL, with customized .zip file (some or all of the graphics in the .zip file can be modified
or replaced with other graphics).
•
Implement their own callback implementation. This allows maximal freedom in customization, includ-
ing adding support for languages not supported by BSGUI.DLL.
BSAPI is implemented on top of BioFrame. The BioFrame is a library providing high level management of the
device, quality assurance and other policies. This allows users of BSAPI to concentrate on application logic
and not sink into low level details.
Future versions of BioAPI BSP will be redesigned as a simple layer on top of BSAPI to avoid duplicity of code
in BSAPI and TFMESSBSP implementations. BSAPI should be linked statically into the TFMESSBSP. This
will prevent unnecessary exporting BSAPI symbols from the DLL so users of BioAPI could not mix the two
APIs in one program by mistake. Also due to the nature of static libraries only the required subset of BSAPI
library will be included in the TFMESSBSP.
2.4. Naming Conventions
All identifiers (names of constants, types and functions) will use prefix “ABS”, and follow the patterns below:
•
ABS_MACRO_IDENTIFIER
•
ABS_TYPE_IDENTIFIER
•
ABSFunctionIdentifier()
In function prototypes special words IN, OUT and INOUT are used, to denote if the parameter is used to pass
data into the function, return some result data or both.
