Diffstat (limited to 'development/pim/pimpaper/gui_xref.tex') (more/less context) (ignore whitespace changes)
-rw-r--r-- | development/pim/pimpaper/gui_xref.tex | 44 |
1 files changed, 24 insertions, 20 deletions
diff --git a/development/pim/pimpaper/gui_xref.tex b/development/pim/pimpaper/gui_xref.tex index d869c5f..f86e618 100644 --- a/development/pim/pimpaper/gui_xref.tex +++ b/development/pim/pimpaper/gui_xref.tex | |||
@@ -1,40 +1,44 @@ | |||
1 | \section{GUI Classes} | 1 | \section{GUI Classes} |
2 | GUI elements should be provided for modifying records in a general way. The next sections | ||
3 | shows suggested widgets for this purpose. | ||
2 | 4 | ||
3 | \subsubsection{Recurrence Widget} | 5 | \subsubsection{Recurrence Widget} |
4 | Opie PIM offers a recurrence Widget to let the user | 6 | Opie PIM offers a recurrence widget to let the user |
5 | configure the recurrence. | 7 | configure the recurrence. |
6 | 8 | ||
7 | \subsubsection{Mainwindow} | 9 | \subsubsection{Mainwindow} |
8 | The mainwindow implements a QCOP Interface for showing, | 10 | The mainwindow implements a QCOP interface for showing and |
9 | editing records. It can handle alarms and reminder activation. | 11 | editing records. It can handle alarms and reminder activation. |
10 | 12 | ||
11 | \section{Cross Reference} | 13 | \section{Cross Reference} |
12 | 14 | ||
13 | \subsection{The idea} | 15 | \subsection{The idea} |
14 | Sometimes an Event or Todo is related to something else. | 16 | Sometimes a datebook-event or todo is related to something else. |
15 | For example the Birthday Attribute of your children Record relate | 17 | For example, the birthday attribute of a child record relate |
16 | to the Birthday Event in your Datebook and the ``Book clown'' | 18 | to the birthday event in a datebook and to the entry ``Book clown'' |
17 | in your Todolist.\\ | 19 | in your todolist.\\ |
18 | We need a way to select the Record and the attribute if we want | 20 | We need a way to interconnect information to describe such relations. |
19 | that fine grained information. | ||
20 | 21 | ||
21 | \subsection{Selecting the Reference} | 22 | \subsection{Selecting the Reference} |
22 | \subsubsection{Out Of Process Selection} | 23 | \subsubsection{Out Of Process Selection} |
23 | For an Out of Process solution we could utilize the targeted | 24 | For an out of process solution, we could utilize the targeted |
24 | Application to request the selection of an record.\\ | 25 | application to request the selection of an record.\\ |
25 | For that to work we need to know which application offers | 26 | For that to work we need to know which application offers |
26 | Cross Referencing and the API needs to be able to find the | 27 | cross referencing. The API needs to be able to find the |
27 | application and then call them via QCOP.\\ | 28 | application and then call them via QCOP.\\ |
28 | Later for resolving the Cross Reference the same application\\ | 29 | Later, for resolving the cross-references, the same application\\ |
29 | would be either asked to give a summary string or it could | 30 | would be either asked to give a summary string or it could |
30 | display the reference on demand. This requires the application | 31 | display the reference on demand. This requires the application |
31 | to start and a specific selection window, but more easily | 32 | to start a specific selection window, but more easily |
32 | allows to cross reference attributes. | 33 | allows to cross reference attributes. \comment{``, but..'' Das verstehe ich nicht!. Ich wuerde den Satz so uebersetzen: |
34 | Dies erfordert, dass die Application ein spezielles Auswahlfenster startet, aber viel einfacher die | ||
35 | Crossreferenzierung von Attributen erlaubt. | ||
36 | Meinst Du das ? } | ||
33 | 37 | ||
34 | \subsubsection{In Process Selection} | 38 | \subsubsection{In-Process-Selection} |
35 | In Process Selection is possible with the usage of OPimBase | 39 | In-process-selection is possible using OPimBase |
36 | and OPimRecord. It allows to query and sort in a generic way. | 40 | and OPimRecord. It allows to query and sort in a generic way. |
37 | This would allow to have a generic Selector widget which | 41 | This would allow to have a generic selector widget, which |
38 | can be used to select a Record and possible files as well. To | 42 | can be used to select a record and possible files as well. To |
39 | support new types one could dlopen the Frontends to allow | 43 | support new types it should be possible to use plugins (via dlopen) do load |
40 | custom Frontends. | 44 | and support custom frontends. |