Added old abandoned KDE3 version of koffice

git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/applications/koffice@1077364 283d02a7-25f6-0310-bc7c-ecb5cbfe19da

1 files changed, 30 insertions, 0 deletions

diff --git a/kexi/doc/dev/kexi_issues.txt b/kexi/doc/dev/kexi_issues.txt
new file mode 100644
index 00000000..62292f2d
--- /dev/null
+++ b/kexi/doc/dev/kexi_issues.txt
@@ -0,0 +1,30 @@
+---------------------------------------------------------
+ Kexi IDEAS, ISSUES, PROPOSALS
+ Copyright (C) 2003 Jaroslaw Staniek js at iidea dot pl
+ Started: 2003-08-01
+ Kexi home page: http://www.koffice.org/kexi/
+---------------------------------------------------
+
+|
+| This document is expected to be independent of given KexiDB driver implementation,
+| but proposals are described here after certain decisions:
+| -drivers are (by current importance): SQLite (embedded), 
+|  ODBC (universality reasons), Mysql (historical reasons), PostgreSQL
+|
+
+1. EXTENSION: Inheriting properties
+	Kexi objects like tables, forms, reports can be put in sort of relation diagram:
+	Easy example: form and report depends on table/query (or more tables and queries).
+
+	This dependency can be called inheriting when we wnat to reuse as many 
+	as possible properties of parent 'object' in child 'object'.
+
+	Examples of these properties: table colors, columns widths, etc. can be 
+	reused in forms/reports that use this its data.
+	Inherited values can be of course changed for 'child' objects if needed.
+
+	Other inherited properties example are custom error/warning messages 
+	(see kexidb_issuses doc, #1).
+
+	Properties inheritance makes database schema more rich and reduces required work 
+	for later stages of the database project.