71 |
|
|
72 |
No matter which view you're using, when the event is shown |
No matter which view you're using, when the event is shown |
73 |
somewhere, the RDF connection to Carli will be shown-- |
somewhere, the RDF connection to Carli will be shown-- |
|
as a buoy. |
|
74 |
|
as a buoy. |
75 |
|
|
76 |
|
If you click on "Carli," what will be shown depends on your |
77 |
|
view settings. I expect that you will be able to select |
78 |
|
different views for the different types of nodes you have; |
79 |
|
so when you have selected "spiral time view" for events, |
80 |
|
when your focus is on "Carli," that setting has no effect, |
81 |
|
because Carli isn't an event, but when you go back to the |
82 |
|
meeting event (all connections are bi-directional), it |
83 |
|
will be shown in the time view. |
84 |
|
|
85 |
|
If no other view is specified for a node type, a basic |
86 |
|
Loom view will be used. So if you have no view setting |
87 |
|
for people, when you click on "Carli," you'll look at |
88 |
|
a Loom structure. Connected negwards on ``event:with`` |
89 |
|
will be the meeting. |
90 |
|
|
91 |
|
In the loom view, the meeting will generally be shown as a node |
92 |
|
no larger than any Loom node, no matter what your special |
93 |
|
view settings for events are when those events are focused. |
94 |
|
But when you actually move onto the event, the spiral time view |
95 |
|
will again occupy most of the screen and the RDF connections |
96 |
|
will only be shown as buoys. |
97 |
|
|
98 |
|
(It is then vital that the Loom bindings work for buoys.) |
99 |
|
|
100 |
|
--------------------------------------------------------------------------- |
101 |
|
|
102 |
|
Therefore, any node's RDF properties can be shown |
103 |
|
as buoys. (A side-effect is that this can always be used |
104 |
|
for introspection, e.g. you can make the x/y positions |
105 |
|
of objects on a canvas visible through this mechanism.) |
106 |
|
|
107 |
|
Many applitudes will deeply make use of this. You don't |
108 |
|
need to come up with a way to show details about an event |
109 |
|
in a calendar view; you simply tell users to show |
110 |
|
these-and-these RDF properties as buoys. |
111 |
|
|
112 |
|
This makes applitudes naturally extensible: The user needs |
113 |
|
some more, the user shows some more. When you add properties, |
114 |
|
it looks natural and integrated, because the applitude |
115 |
|
*always* uses this mechanism to show additional information. |
116 |
|
|
117 |
|
|