Difference between revisions of "Base To-Do/HSQLDB: single-file backend"
(Created page with "Description OpenOffice.org Base follows a component-oriented approach for enabling database access. For this, database drivers are installed in OpenOffice.org which provide a...") |
|||
| Line 1: | Line 1: | ||
| − | Description | + | ===Description=== |
| − | + | OpenOffice Base follows a component-oriented approach for enabling database access. For this, database drivers are installed in OpenOffice which provide access to a certain (class of) database(s). | |
| − | OpenOffice | + | |
While at the driver level, the implementation is pretty good modularized, the UI implementation can be improved. Currently, there are a lot of places in the code with hard-coded information, such as "database X requires UI option Y". | While at the driver level, the implementation is pretty good modularized, the UI implementation can be improved. Currently, there are a lot of places in the code with hard-coded information, such as "database X requires UI option Y". | ||
| − | The goal of this project is to design and implement a reasonable architecture for bringing a driver to the UI. The existing implementation needs to be migrated to this new architecture. As a proof of concept, an existing currently-external driver (e.g. the native PostgreSQL driver) should be modified so that it can be deployed into an | + | The goal of this project is to design and implement a reasonable architecture for bringing a driver to the UI. The existing implementation needs to be migrated to this new architecture. As a proof of concept, an existing currently-external driver (e.g. the native PostgreSQL driver) should be modified so that it can be deployed into an AOO installation and makes use of the features of the new architecture. |
* required skills C++ | * required skills C++ | ||
| − | * useful skills: | + | * useful skills: AOO's component technology (UNO), as well as AOO's configuration concepts |
* Contact: mailto:dev@dba.openoffice.org | * Contact: mailto:dev@dba.openoffice.org | ||
* estimated effort: 2 months | * estimated effort: 2 months | ||
* difficulty: high | * difficulty: high | ||
[[Category:Database]][[Category:To-Do]] | [[Category:Database]][[Category:To-Do]] | ||
Revision as of 14:44, 28 July 2022
Description
OpenOffice Base follows a component-oriented approach for enabling database access. For this, database drivers are installed in OpenOffice which provide access to a certain (class of) database(s).
While at the driver level, the implementation is pretty good modularized, the UI implementation can be improved. Currently, there are a lot of places in the code with hard-coded information, such as "database X requires UI option Y".
The goal of this project is to design and implement a reasonable architecture for bringing a driver to the UI. The existing implementation needs to be migrated to this new architecture. As a proof of concept, an existing currently-external driver (e.g. the native PostgreSQL driver) should be modified so that it can be deployed into an AOO installation and makes use of the features of the new architecture.
- required skills C++
- useful skills: AOO's component technology (UNO), as well as AOO's configuration concepts
- Contact: mailto:dev@dba.openoffice.org
- estimated effort: 2 months
- difficulty: high
