[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    www/areas/koffice
From:       Martin Ellis <martin.ellis () kdemail ! net>
Date:       2006-10-17 18:49:12
Message-ID: 1161110952.333051.15592.nullmailer () svn ! kde ! org
[Download RAW message or body]

SVN commit 596510 by martin:

* Remove "(functional)" comments - you'd expect it
  to be functional if it's listed.
* Don't point directly to the source download in the
  FAQ: point to the generic download page.


 M  +2 -3      faq/index.php  
 M  +3 -5      filters/1.6/kexi/mdb.php  
 M  +24 -10    kexi/features.php  


--- trunk/www/areas/koffice/faq/index.php #596509:596510
@@ -130,9 +130,8 @@
 $faq->addSection("How to get and install KOffice?");
 
 $faq->addQuestion("How do I get and compile the KOffice sources?",
-"Please have a look at <a href=\"http://www.koffice.org/download/source.php\">
-this page.</a>"
-);
+"Please see the <a href=\"http://www.koffice.org/download/\">download
+page.</a>" );
 
 $faq->addQuestion("I want to be on the bleeding edge. How can I get my sources up to \
date?",  "You need to checkout the koffice path of KDE's SVN either
--- trunk/www/areas/koffice/filters/1.6/kexi/mdb.php #596509:596510
@@ -7,12 +7,10 @@
 
   <h2>Overview</h2>
 
-  <p>Support for importing Microsoft Access databases is available for
-  Kexi.</p>
+  <p>Support for importing Microsoft Access databases is available
+  as <em>separate plugin</em> for Kexi.  For more information, see the
+  Download section below</p>
 
-  <p>It is distributed as <em>separate plugin</em> for Kexi.  For more
-  information, see the Download section below</p>
-
   <p>The plugin can be used to import Access databases into a Kexi
   database only: it cannot be used to edit the database, nor to export
   to an Access database.  However, it should also be able to import
--- trunk/www/areas/koffice/kexi/features.php #596509:596510
@@ -10,8 +10,8 @@
 </p>
 <ul>
  <li>Hiding of the database backend specifics from the user, but allowing advanced \
                users full access at the same time</li>
- <li>Table structure altering (functional)</li>
- <li>Table creation (functional)</li>
+ <li>Table structure altering</li>
+ <li>Table creation</li>
  <li>Database query creation, without the need of knowing SQL (Structured Query \
Language)</li>  <li>User-friendly data manipulation (even on complicated \
queries)</li>  </ul>
@@ -20,9 +20,12 @@
 <b>Data Processing and Access</b><br/>
 </p>
 <ul>
- <li>User-defined forms for data input and presentation (functional)</li>
- <li>Data migration from MySQL, PostgreSQL. Migration from MS Access databases is \
available as an <a href="http://www.kexi-project.org/wiki/wikiview/index.php?MDBDriver#2._Download">additional \
                plugin</a>. (functional)</li>
- <li>Scripting support with Python and JavaScript/ECMA-Script language and/or Python \
(in progress)</li> + <li>User-defined forms for data input and presentation</li>
+ <li>Data migration from MySQL, PostgreSQL.</li>
+ <li>Migration from Microsoft Access databases is available as
+ an <a href="../filters/1.6/kexi/mdb.php">additional plugin</a>.</li>
+ <li>Scripting support with Python and JavaScript/ECMA-Script language
+ and/or Python</li>
  <li>KWord mailmerge integration (planned)</li>
  <li>Easy data report generation (rewrite planned)</li>
 </ul>
@@ -31,13 +34,24 @@
 <b>Supported Database Backends</b>
 </p>
 <p>
-At the moment this documentation is written, drivers for the following database \
engines are developed as integrated (single user) backends:</p> +  Kexi projects are \
usually stored in a file.  This is convenient for +  databases that are only used by \
a single person. +</p>
+<p>
+  However, for some projects, users may prefer to store their data on
+  a remote database server.  This allows several users to use the same
+  database.  Currently, changes to the database structure should only
+  be made by one user: concurrent modifications to the database
+  structure are not supported.
+</p>
+
+<p>Kexi supports the following database systems:</p>
 <ul>
- <li><a href="http://www.sqlite.org">SQLite</a> (version 2 and 3, file-based, \
                complete)</li>
- <li><a href="http://www.postgresql.org">PostgreSQL (complete)</a></li>
- <li><a href="http://www.mysql.com">MySQL (complete)</a></li>
- <li><a href="http://firebird.sourceforge.net">Firebird (planned)</a></li>
+ <li><a href="http://www.sqlite.org">SQLite</a> (version 2 and 3, file-based)</li>
+ <li><a href="http://www.postgresql.org">PostgreSQL</a> (server-based)</li>
+ <li><a href="http://www.mysql.com">MySQL</a> (server-based)</li>
 </ul>
+
 <p>
 It is planned to support also other database systems, especially for \
FireBird/Interbase and ODBC interface, for better corporate usage in the next \
versions. Typically, most up to date and best supported backends (from KexiDB point \
of view) are always: SQLite, PostgreSQL and MySQL.  </p>


[prev in list] [next in list] [prev in thread] [next in thread]