-rw-r--r-- | core/pim/datebook2/DESIGN | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/core/pim/datebook2/DESIGN b/core/pim/datebook2/DESIGN new file mode 100644 index 0000000..7442e81 --- a/dev/null +++ b/core/pim/datebook2/DESIGN | |||
@@ -0,0 +1,29 @@ | |||
1 | A small abstract about the design | ||
2 | |||
3 | First of all we've a namespace called Datebook | ||
4 | |||
5 | class MainWindow is our QMainWindow and PimMainWindow | ||
6 | it's the center of all datebook operations. | ||
7 | It loads all Views, Configs, Shows, Manager | ||
8 | and dispatches between them | ||
9 | |||
10 | the Interface declarations use protected methods instead | ||
11 | of signals because templates and signals does not match | ||
12 | that nicely. | ||
13 | I add friend declarations to the mainwindow so that we've a | ||
14 | tight interface of interactions and know that it works. | ||
15 | friend can not be inherited so all got enough abstraction. The | ||
16 | dependency on the MainWindow is acceptable. | ||
17 | |||
18 | Then we've a small DB Manager class which is responsible | ||
19 | for controlling the ODateBookAccess class and to resolve | ||
20 | other records ( due todo items, Birthdays.. ) | ||
21 | |||
22 | Show - Show can show richtext of OEvent | ||
23 | View - The basic view | ||
24 | MainWindow - The mainwindow with all the actions | ||
25 | Editor - The editor interface to edit and create OEvents | ||
26 | AlarmManager - A widget to take care of alarm activation | ||
27 | ManagerTemplate,StringManager - Responsible for managing strings | ||
28 | for the Location and Description ComboBox | ||
29 | TemplateManager - the OEvent TemplateManager \ No newline at end of file | ||