Difference between revisions of "Base To-Do"

From Apache OpenOffice Wiki
Jump to: navigation, search
 
(26 intermediate revisions by 5 users not shown)
Line 1: Line 1:
Below is a list of [[Base]]-related projects which could be implemented by interested developers. Most of these projects are relatively self-contained, and do not require too much knowledge about OOo's code infrastructure.
+
Below is a list of [[Base]]-related projects which could be implemented by interested developers. Most of these projects are relatively self-contained, and do not require too much knowledge about AOO's code infrastructure.
  
Note that the actual project descriptions are not yet moved to this place here, they still reside [http://dba.openoffice.org/development/projects.html one of the project's static pages]. Your'e encourage to visit this page, as it contains much more information currently.
+
Note that the actual project descriptions are not yet moved to this place here, they still reside [https://www.openoffice.org/dba/development/projects.html one of the project's static pages]. You're encouraged to visit this page, as it contains much more current information.
  
(So if you want, one of the To-Dos of our project is to move the To-Dos from http://dba.openoffice.org/development/projects.html to this Wiki page.)
+
(So if you want, one of the To-Dos of our project is to move the To-Dos from https://www.openoffice.org/dba/development/projects.html to this Wiki page.)
  
 
== Joins in dBase queries ==
 
== Joins in dBase queries ==
  
Queries to dBase files can currently contain one table only. Scope of the project is to enhance Base' built-in simple query engine to be capable of executing statements line <code>SELECT table1.field1, table2.field2 FROM table1, table2</code>. The dBase driver, the text/csv driver, and the Spreadsheet driver would all benefit from this extension.
+
The content of this item moved to a dedicated page: [[Base_To-Do/Joins_in_dBase_queries]]
 
+
Be prepared to dig around here before starting the project, the project touches low-level core implementations, including some heavy-to-read STL stuff, so be prepared to invest some time before writing the first line of code.
+
 
+
* required skills C++, SQL knowledge
+
* useful skills: Lexx and Yacc
+
* Contact: mailto:dev@dba.openoffice.org
+
* effort: 4 weeks for an experienced developer
+
* difficulty: high
+
  
 
== SDBC driver for LDAP directories ==
 
== SDBC driver for LDAP directories ==
  
described in more detail at the [http://dba.openoffice.org/development/projects.html#ldap here].
+
The content of this item moved to a dedicated page: [[Base_To-Do/SDBC_driver_for_LDAP_directories]]
  
 
== New/Enhanced Form Controls ==
 
== New/Enhanced Form Controls ==
  
described in more detail at the [http://dba.openoffice.org/development/projects.html#form_controls here].
+
The content of this item moved to a dedicated page: [[Base_To-Do/New+Enhanced_Form_Controls]]
  
 
== Dialogs with Form Functionality ==
 
== Dialogs with Form Functionality ==
  
described in more detail at the [http://dba.openoffice.org/development/projects.html#form_dialogs here].
+
The content of this item moved to a dedicated page: [[Base_To-Do/Dialogs_with_Form_Functionality]]
  
 
== Database driver UI modularization ==
 
== Database driver UI modularization ==
  
described in more detail at the [http://dba.openoffice.org/development/projects.html#driver_modules here].
+
The content of this item moved to a dedicated page: [[Base_To-Do/Database_driver_UI_modularization]]
  
 
== HSQLDB: single-file backend ==
 
== HSQLDB: single-file backend ==
  
described in more detail at the [http://dba.openoffice.org/development/projects.html#single_file_backend here].
+
The content of this item moved to a dedicated page: [[Base_To-Do/HSQLDB:_single-file_backend]]
  
== Embed Derby into OpenOffice.org databases ==
+
== Embed Derby into OpenOffice databases ==
  
described in more detail at the [http://dba.openoffice.org/development/projects.html#embed_derby here].
+
OpenOffice Base features an abstract mechanism to embed database backend files into AOO databases (.odb). Currently, this is implemented for [https:///hsqldb.org HSQLDB], which is used as AOO's default database engine.
  
== SQL Syntax Highlighting ==
+
To allow this feature for other engines, one must:
  
described in more detail at the [http://dba.openoffice.org/development/projects.html#syntax_hilight here].
+
* virtualize the engine's file access, so that it re-routes all its file operations through an abstract API.
 +
* implement this API on the AOO Base side
  
== HSQLDB: editable views ==
+
The project is to do those implementations for [https://db.apache.org/derby Apache Derby database].
  
described in more detail at the [http://dba.openoffice.org/development/projects.html#editable_views here].
+
* required skills Java, C++
 +
* useful skills: AOO's database access API, AOO's component technology (UNO)
 +
* Contact: mailto:dev@dba.openoffice.org
 +
* effort: 2 months
 +
* difficulty: high
 +
 
 +
See also:
 +
* [[File:DerbyToursDB.odb]]
 +
* [[User:HCPotter]]
  
 
== Native, cross-platform access to MS Access databases ==
 
== Native, cross-platform access to MS Access databases ==
Line 61: Line 62:
 
described in more detail at the [http://dba.openoffice.org/development/projects.html#new_filter here].
 
described in more detail at the [http://dba.openoffice.org/development/projects.html#new_filter here].
  
<noinclude>[[Category:Database]]</noinclude>
+
== Enable Picture Insertion ==
 +
 
 +
:For example uses see table MAPS in  [[File:ToursDB_schema.sql]] and [[File:DerbyToursDB.odb]]. [[User:HCPotter|HCPotter]]
 +
 
 +
== Discuss Remote Operation Necessity ==
 +
 
 +
:When [[File:DerbyToursDB.odb]] is downloaded it can be used only when saved for local access. I have not tried the external application editing option. [[User:HCPotter|HCPotter]] 09:00, 14 June 2010 (UTC)
 +
 
 +
<noinclude>[[Category:Database]][[Category:To-Do]]</noinclude>

Latest revision as of 16:24, 30 July 2022

Below is a list of Base-related projects which could be implemented by interested developers. Most of these projects are relatively self-contained, and do not require too much knowledge about AOO's code infrastructure.

Note that the actual project descriptions are not yet moved to this place here, they still reside one of the project's static pages. You're encouraged to visit this page, as it contains much more current information.

(So if you want, one of the To-Dos of our project is to move the To-Dos from https://www.openoffice.org/dba/development/projects.html to this Wiki page.)

Joins in dBase queries

The content of this item moved to a dedicated page: Base_To-Do/Joins_in_dBase_queries

SDBC driver for LDAP directories

The content of this item moved to a dedicated page: Base_To-Do/SDBC_driver_for_LDAP_directories

New/Enhanced Form Controls

The content of this item moved to a dedicated page: Base_To-Do/New+Enhanced_Form_Controls

Dialogs with Form Functionality

The content of this item moved to a dedicated page: Base_To-Do/Dialogs_with_Form_Functionality

Database driver UI modularization

The content of this item moved to a dedicated page: Base_To-Do/Database_driver_UI_modularization

HSQLDB: single-file backend

The content of this item moved to a dedicated page: Base_To-Do/HSQLDB:_single-file_backend

Embed Derby into OpenOffice databases

OpenOffice Base features an abstract mechanism to embed database backend files into AOO databases (.odb). Currently, this is implemented for HSQLDB, which is used as AOO's default database engine.

To allow this feature for other engines, one must:

  • virtualize the engine's file access, so that it re-routes all its file operations through an abstract API.
  • implement this API on the AOO Base side

The project is to do those implementations for Apache Derby database.

  • required skills Java, C++
  • useful skills: AOO's database access API, AOO's component technology (UNO)
  • Contact: mailto:dev@dba.openoffice.org
  • effort: 2 months
  • difficulty: high

See also:

Native, cross-platform access to MS Access databases

described in more detail at the here.

SDBC driver for vCards

described in more detail at the here.

New Filter Dialog

described in more detail at the here.

Enable Picture Insertion

For example uses see table MAPS in File:ToursDB schema.sql and File:DerbyToursDB.odb. HCPotter

Discuss Remote Operation Necessity

When File:DerbyToursDB.odb is downloaded it can be used only when saved for local access. I have not tried the external application editing option. HCPotter 09:00, 14 June 2010 (UTC)
Personal tools