blob: 7b33925927a7057327465fb36c8ff891791a2537 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
PROPOSAL: Generic Guidlines For Kexi Development
Jaroslaw Staniek
started: 2003-06-25
Idea 1
Add tests for command line-only operations using kexiDB library.
These tests can be later turned to command line options for Kexi what will allow non
GUI operations o databases/projects.
Idea 2
Look at TQSQL module from TQt. E.g. there is efficient cursor feature (it works quite good with mysql).
We have KexiDBRecordSet instead, but this is just the same thing.
In fact many KexiDB features are compatible with TQSQL.
Focus on:
- avoid loading all result data to client memory (fetch some records instead)
- avoid blocking operations (do asynchronously as many things as possible)
- avoid memory copying (at low level try to store original char* data instead of TQString,
convert to TQString only on data displaying)
Idea 3
Directories layout:
dialogs/
+-altertable/
+-datatable/
+-queryeditor/
+-sqleditor
widgets/
+-tableview/
+-datatableview/
Idea 4
Classes naming guidelines:
'Dialog' suffix for all classes
|
