User: fs Date: 2007-10-08 12:12:03+0000 Modified: dba/www/development/projects.html
Log: re-directing some items to our Wiki File Changes: Directory: /dba/www/development/ ================================ File [changed]: projects.html Url: http://dba.openoffice.org/source/browse/dba/www/development/projects.html?r1=1.5&r2=1.6 Delta lines: +9 -188 --------------------- --- projects.html 2007-02-05 08:40:53+0000 1.5 +++ projects.html 2007-10-08 12:12:01+0000 1.6 @@ -54,8 +54,6 @@ <li> <a href="#syntax_hilight">SQL Syntax Highlighting</a></li> <li> - <a href="#editable_views">HSQLDB: editable views</a></li> - <li> <a href="#cross_access">native, cross-platform access to MS Access databases</a></li> <li> <a href="#vcards">SDBC driver for vCards</a></li> @@ -95,53 +93,10 @@ <!-- ====================== --> <!-- Joins in dBase queries --> <h3><a name="dbase_joins"></a>Joins in dBase queries</h3> - <h4>description</h4> - <p>Our own dBase implementation (actually: the <a href="http://api.openoffice.org/docs/common/ref/com/sun/star/sdbc/module-ix.html";> - SDBC</a> driver which allows to access dBase files) is not capable of - executing queries which span more than one table. This means you can do a - <code>SELECT <field> FROM <table></code>, but no <code>SELECT - <table1>.<field1>, <table2>.<field2> FROM - <table1>, <table2></code>.</p> - - <p>Enhancing this would be a major step towards a dBase implementation which - provides everything for low end database needs.</p> - - <p>This includes probably no UI, but only core implementations in the dBase - driver, probably including some heavy-to-read STL stuff, so be prepared to - invest some time for digging around.</p> - - <table style="text-align: left;" cellspacing="0"> - <tbody> - <tr> - <td class="effort_header" width="200px">required skills</td> - <td> - <ul> - <li>C++</li> - <li>some SQL knowledge</li> - </ul> - </td> - </tr> - <tr> - <td class="effort_header">useful skills</td> - <td> - <ul> - <li>Lexx and Yacc</li> - </ul> - </td> - </tr> - <tr> - <td class="effort_header">estimated effort</td> - <td>3 weeks for an experienced developer</td> - </tr> - <tr> - <td class="effort_header">difficulty</td> - <td>high</td> - </tr> - </tbody> - </table> - <br/> - <hr style="width: 100%; height: 2px;"> + <p>The descirption of this project has been moved to + <a href="http://wiki.services.openoffice.org/wiki/Base_To-Do/Joins_in_dBase_queries"; target="_blank">our + Wiki</a>.</p> <!-- ================================ --> <!-- SDBC driver for LDAP directories --> @@ -468,152 +423,18 @@ <!-- =============================== --> <!-- Embed Derby into OpenOffice.org databases --> <h3><a name="embed_derby"></a>Embed Derby into OpenOffice.org databases</h3> - <h4>description</h4> - <p>OpenOffice.org Base features an abstract mechanism to embed database backend files into OOo - databases (.odb). Currently, this is implemented for <a href="http:///hsqldb.org";>HSQLDB</a>, - which is used as OOo's default database engine.</p> - - <p>To allow this feature for other engines, one must - <ul> - <li>virtualize the engine's file access, so that it re-routes all its file operations through - an abstract API.</li> - <li>implement this API on the OOo Base side</li> - </ul> - The project is to do those implementations for the <a href="http://db.apache.org/derby/";>Apache Derby - database</a>. - </p> - <table style="text-align: left;" cellspacing="0"> - <tbody> - <tr> - <td class="effort_header" width="200px">required skills</td> - <td>C++</td> - </tr> - <tr> - <td class="effort_header">useful skills</td> - <td> - <ul> - <li>familarity with OOo's database access API</li> - <li>relational database concepts</li> - <li>OOo's component technology (UNO)</li> - </ul> - </td> - </tr> - <tr> - <td class="effort_header">estimated effort</td> - <td>2 months</td> - </tr> - <tr> - <td class="effort_header">difficulty</td> - <td>high</td> - </tr> - </tbody> - </table> - <br/> - <hr style="width: 100%; height: 2px;"> + <p>The descirption of this project has been moved to + <a href="http://wiki.services.openoffice.org/wiki/Base_To-Do#Embed_Derby_into_OpenOffice.org_databases"; target="_blank">our + Wiki</a>.</p> <!-- =============================== --> <!-- SQL Syntax Highlighting --> <h3><a name="syntax_hilight"></a>SQL Syntax Highlighting</h3> - <h4>description</h4> - - <p>The SQL view of the query designer, which displays, and allows to edit, - raw SQL statements, currently is a mere text input field. It would be helpful - especially to the unexperienced user to have syntax highlighting here: SQL keywords - should be notable, literals should be distinguished, and the like.</p> - - <p>OpenOffice.org already features core components which allow syntax highlighting - in a text field - the most prominent example is the Basic IDE -, so there already is - a foundation to base this feature on.</p> - - <table style="text-align: left;" cellspacing="0"> - <tbody> - <tr> - <td class="effort_header" width="200px">required skills</td> - <td> - <ul> - <li>C++</li> - <li>SQL knowledge</li> - </ul> - </td> - </tr> - <tr> - <td class="effort_header">useful skills</td> - <td> - <ul> - – - </ul> - </td> - </tr> - <tr> - <td class="effort_header">estimated effort</td> - <td>2 weeks</td> - </tr> - <tr> - <td class="effort_header">difficulty</td> - <td>medium</td> - </tr> - </tbody> - </table> - <br/> - <hr style="width: 100%; height: 2px;"> - <!-- =============================== --> - <!-- HSQLDB: editable views --> - <h3><a name="editable_views"></a>HSQLDB: editable views</h3> - <h4>description</h4> - - <p><a href="http:///hsqldb.org"; title="http:///hsqldb.org";>HSQLDB</a>, - used as OpenOffice.org's database engine, features the usage of views - (basically, stored SQL queries).</p> - - <p>An advantage of views over queries is that the former can be re-used in - other queries, i.e. you can do a <code>SELECT * FROM foo</code> where - <code>foo</code> is the name of an existing view, i.e. a <code>SELECT</code> - statement itself.</p> - - <p>A disadvantage of views is that the constituting statement cannot be edited - in OpenOffice.org Base once the view has been created.</p> - - <p>Goal of this project is to provide an "Edit view" functionality in - OpenOffice.org Base, for the moment for the HSQLDB backend only. - For this, an API needs to be defined which allows editing views. This API has - to be implemented in Base' dedicated HSQLDB driver. Additionally, the user - interface should respect the existence of this API by offering an "Edit View" - item in the context menu of views. Once chosen, Base' query designer is to be - started, to modify the SQL statement constituting the view. Saving the work in - the designer should change the view's underlying statement.</p> - - <table style="text-align: left;" cellspacing="0"> - <tbody> - <tr> - <td class="effort_header" width="200px">required skills</td> - <td> - <ul> - <li>C++</li> - </ul> - </td> - </tr> - <tr> - <td class="effort_header">useful skills</td> - <td> - <ul> - <li>OpenOffice.org's component model (<a href="http://wiki.services.openoffice.org/wiki/Uno";>UNO</a>)</li> - </ul> - </td> - </tr> - <tr> - <td class="effort_header">estimated effort</td> - <td>3 weeks</td> - </tr> - <tr> - <td class="effort_header">difficulty</td> - <td>medium</td> - </tr> - </tbody> - </table> - <br/> - <hr style="width: 100%; height: 2px;"> + <p>The descirption of this project has been moved to + <a href="http://wiki.services.openoffice.org/wiki/Base_To-Do#SQL_Syntax_Highlighting"; target="_blank">our + Wiki</a>.</p> <!-- ==================================================== --> <!-- Native, cross-platform access to MS Access databases --> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
