Xplorer is the framework used to design uniform and attractive user interfaces in a client/server environment. This designing of screen readouts and lists can be done by the user independent of the program while the program is running. On the development side that means less development time and expense, and thus a better price/performance ratio for our customers. The look & feel is modelled on Windows Explorer and allows free navigation. Program functions can be easily integrated in the different views. So there are fewer rigid program flows. Instead, the relevant functions can be invoked from the individual objects. In this connection one speaks of an analytically driven application.
Performance features of the user interface
Clarity
Multiple views are available for every object. In principle, we make a distinction between list-like views and detailed views that mainly look like forms. Multi-stage sorting is possible in the lists with a simple click of the mouse. The navigation path and restrictions imposed by the selection criteria are always visible in the current view. |
|
 |
Navigation
Object relationships are visible and trackable in a tree view for navigation purposes. Informative identifiers are stored for the relationships between the objects (e.g. the customer and his open orders). Result quantities are restricted by making a corresponding choice in a selection dialogue.
Operating comfort
The handling is based on the look & feel of Windows Explorer. Controls can be used to quickly re-partition the screen layout (screen areas are cut in or cut out). The time needed to familiarise oneself with the programme is greatly reduced by orientation of its user control to the Windows standard and by the fact that navigation through the application is guided by informative identifiers.
Further processing
In principle, data can be exported from the application to Excel, the respective data view being assigned to an Excel folder. Only the data segment is exchanged in these Excel folders when an export is repeated. If the Excel folders contain graphics, pivot tables, formatting and further processing operations, they are automatically updated during the next export.
Administration, Technology and Implementation
Rights administration and setup
Rights can be issued for individual views of data. This controls whether a user is allowed to query the respective data. Moreover, the user can also be granted a screen design right. He or she will then be able to redesign or modify the view, or add a new view. The rights administration feature is comfortably implemented as an Explorer of its own. The database for authorisation is expanded map security. The administration of rights presupposes administrator status.
Large and complex systems cannot be respectively created anew from the ground up. It’s possible to export and import the presentation layer as an overall system or in parts.
Screen Design
Screen design changes can be made in every view with a click of the mouse. Autoformat templates of the kind familiar with Excel can be used for list views. More complex forms are edited with Sybase InfoMaker. The system is stored in its entirety in the respective relational database. So it’s possible to do maintenance work, make changes and additions without having to perform setups or updates.
We use a central repository for formats and headings (PowerBuilder). Once headings and fields have been set up they are automatically used when a view is redesigned (e.g. field width, numeric format, date format, field height, field identifier, etc.).
The system has troubleshooting and performance-analysis features to help you implement new functions. After enabling it is possible to read out SQL statements or the SQL execution plan (currently Oracle only). It is possible to optimise the views on this basis, or tuning measures can be derived therefrom in the database.
The building and maintenance of a system is done in a comfortable Xplorer view and presupposes knowledge of and know-how about the underlying data model. That is typically the job of a data-processing department or a user with advanced system knowledge.
Technological basis
The system has been developed with PowerBuilder Enterprise and supports every customary database. Another framework we use is the MAP class library. We support OpenBundle, NewBundle, M_MAP_MAIN interfaces for developers who use this class library.
|
