17 |
|
|
18 |
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"></head><body> |
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"></head><body> |
19 |
This is a rough script for a presentation about our research group's work. <br> |
This is a rough script for a presentation about our research group's work. <br> |
20 |
|
<br> |
21 |
|
<table cellpadding="2" cellspacing="2" border="0" width="100%"> |
22 |
|
<tbody> |
23 |
|
<tr> |
24 |
|
<td valign="top"><br> |
25 |
|
</td> |
26 |
|
<td valign="top"><br> |
27 |
|
</td> |
28 |
|
<td valign="top"><br> |
29 |
|
</td> |
30 |
|
<td valign="top"><br> |
31 |
|
</td> |
32 |
|
</tr> |
33 |
|
<tr> |
34 |
|
<td valign="top"><small><br> |
35 |
|
</small></td> |
36 |
|
<td valign="top"><small>Gzz version timeline<br> |
37 |
|
</small></td> |
38 |
|
<td valign="top"><small><br> |
39 |
|
</small></td> |
40 |
|
<td valign="top"><small><br> |
41 |
|
</small></td> |
42 |
|
</tr> |
43 |
|
<tr> |
44 |
|
<td valign="top">Before I start to tell you about our technology, let me explain our current status.<br> |
45 |
|
</td> |
46 |
|
<td valign="top">There have been a lot of releases, the last "stable" |
47 |
|
one being 0.6. However, 0.6 is not yet usable for real work, it's still proof-of-concept.<br> |
48 |
|
</td> |
49 |
|
<td valign="top">After 0.6, the system has been <b>completely</b> redesigned from a more solid ground.<br> |
50 |
|
</td> |
51 |
|
<td valign="top">In the process, we have had several difficulties combining |
52 |
|
our research and software engineering activities. With version 0.8alpha1, |
53 |
|
I think we're finally starting to strike the right balance.<br> |
54 |
|
</td> |
55 |
|
</tr> |
56 |
|
<tr> |
57 |
|
<td valign="top"><br> |
58 |
|
</td> |
59 |
|
<td valign="top"><br> |
60 |
|
</td> |
61 |
|
<td valign="top"><br> |
62 |
|
</td> |
63 |
|
<td valign="top"><br> |
64 |
|
</td> |
65 |
|
</tr> |
66 |
|
<tr> |
67 |
|
<td valign="top"><br> |
68 |
|
</td> |
69 |
|
<td valign="top"><br> |
70 |
|
</td> |
71 |
|
<td valign="top"><br> |
72 |
|
</td> |
73 |
|
<td valign="top"><br> |
74 |
|
</td> |
75 |
|
</tr> |
76 |
|
<tr> |
77 |
|
<td valign="top"><br> |
78 |
|
</td> |
79 |
|
<td valign="top"><br> |
80 |
|
</td> |
81 |
|
<td valign="top"><br> |
82 |
|
</td> |
83 |
|
<td valign="top"><br> |
84 |
|
</td> |
85 |
|
</tr> |
86 |
|
<tr> |
87 |
|
<td valign="top">The things I'm about to show you are research, user-interface-wise, |
88 |
|
and software engineering on the structure side (since we think we now have |
89 |
|
that side pretty much in control.)<br> |
90 |
|
</td> |
91 |
|
<td valign="top">One really important thing is that we're not cheating. |
92 |
|
These are not mockups. It's all real and possible to use. And the code is |
93 |
|
publically available from our CVS repository.<br> |
94 |
|
<br> |
95 |
|
This <b>doesn't</b> mean that it's ready for production use. Most of it is not. Making production-level software takes a lot of polishing.<br> |
96 |
|
</td> |
97 |
|
<td valign="top"><br> |
98 |
|
</td> |
99 |
|
<td valign="top"><br> |
100 |
|
</td> |
101 |
|
</tr> |
102 |
|
<tr> |
103 |
|
<td valign="top"><br> |
104 |
|
</td> |
105 |
|
<td valign="top"><br> |
106 |
|
</td> |
107 |
|
<td valign="top"><br> |
108 |
|
</td> |
109 |
|
<td valign="top"><br> |
110 |
|
</td> |
111 |
|
</tr> |
112 |
|
</tbody> |
113 |
|
</table> |
114 |
|
<br> |
115 |
|
|
116 |
|
|
117 |
|
|
157 |
</small></td> |
</small></td> |
158 |
</tr> |
</tr> |
159 |
<tr> |
<tr> |
160 |
<td valign="top">Lots of PDF files, hard to keep track<br> |
<td valign="top">Anyway, |
161 |
|
let's start with this. A PDF article from somewhere on the net. Information |
162 |
|
workers like me get Lots of PDF files, hard to keep track<br> |
163 |
</td> |
</td> |
164 |
<td valign="top">Easier if printed on fancy paper (even virtual)<br> |
<td valign="top">Easier if printed on fancy paper (even virtual)<br> |
165 |
</td> |
</td> |
168 |
<td valign="top">Even easier using distortion-oriented views. <small>I |
<td valign="top">Even easier using distortion-oriented views. <small>I |
169 |
must stress that distorting the view like this is NOT our invention - several |
must stress that distorting the view like this is NOT our invention - several |
170 |
research groups have been working on such ideas. It only took us a day to |
research groups have been working on such ideas. It only took us a day to |
171 |
implement it and it *does* make it easier to read the text.</small><br> |
implement it and it *does* make it easier to read the text.</small> What, your browser and PDF viewer doesn't let you do that? ;) ;)<br> |
172 |
</td> |
</td> |
173 |
</tr> |
</tr> |
174 |
<tr> |
<tr> |
537 |
</td> |
</td> |
538 |
</tr> |
</tr> |
539 |
<tr> |
<tr> |
540 |
<td valign="top"><br> |
<td valign="top">NADIR?<br> |
541 |
</td> |
</td> |
542 |
<td valign="top"><br> |
<td valign="top"><br> |
543 |
</td> |
</td> |
689 |
</td> |
</td> |
690 |
<td valign="top">This actually seems to be one of the most difficult |
<td valign="top">This actually seems to be one of the most difficult |
691 |
things for people starting with computers to get used to: the limited structure, |
things for people starting with computers to get used to: the limited structure, |
692 |
making it difficult to find things.<br> |
making it difficult to find things. They get lost easily.<br> |
693 |
</td> |
</td> |
694 |
</tr> |
</tr> |
695 |
<tr> |
<tr> |
733 |
both related to subject X If you're the author of one of them, you can explicitly |
both related to subject X If you're the author of one of them, you can explicitly |
734 |
add a "hyperlink". But it only works one way.<br> |
add a "hyperlink". But it only works one way.<br> |
735 |
</td> |
</td> |
736 |
<td valign="top">However, there's no fundamental reason why you couldn't say "remember the connection" except that the systems' most fundamental parts were designed with computers, not humans in mind.<br> |
<td valign="top">However, |
737 |
|
there's no fundamental reason why you couldn't say "remember the connection" |
738 |
|
except that the systems' most fundamental parts were designed with computers, |
739 |
|
not humans in mind.<br> |
740 |
</td> |
</td> |
741 |
<td valign="top"><br> |
<td valign="top"><br> |
742 |
</td> |
</td> |
774 |
</td> |
</td> |
775 |
</tr> |
</tr> |
776 |
<tr> |
<tr> |
777 |
<td valign="top">Relational databases ...<br> |
<td valign="top">To explain the word "hyperstructure": think about |
778 |
|
a bookshelf. You can choose to put two related books next to each other. |
779 |
|
This is the normal spatial structure. Now, after you've arranged all the |
780 |
|
books in a logical order, you are reading a book and remember "ah, this reminds |
781 |
|
me of something in that book... where is it now"<br> |
782 |
|
</td> |
783 |
|
<td valign="top">Unfortunately, it's in a different part of the bookshelf. |
784 |
|
You can put a piece of paper to refer there but that's not fun. But with |
785 |
|
computers, we don't need to be confined like this. It's difficult to visualize |
786 |
|
but we can at the same time leave all the books in their current locations |
787 |
|
AND additionally put the two books next to each other.<br> |
788 |
|
</td> |
789 |
|
<td valign="top">This is the important thing that Ted Nelson and Douglas |
790 |
|
Engelbart realized in the 1960s, based on Vannevar Bush's earlier visions. |
791 |
|
<br> |
792 |
|
</td> |
793 |
|
<td valign="top"><br> |
794 |
|
</td> |
795 |
|
</tr> |
796 |
|
<tr> |
797 |
|
<td valign="top"><br> |
798 |
|
</td> |
799 |
|
<td valign="top"><br> |
800 |
|
</td> |
801 |
|
<td valign="top"><br> |
802 |
|
</td> |
803 |
|
<td valign="top"><br> |
804 |
|
</td> |
805 |
|
</tr> |
806 |
|
<tr> |
807 |
|
<td valign="top"><br> |
808 |
|
</td> |
809 |
|
<td valign="top"><br> |
810 |
|
</td> |
811 |
|
<td valign="top"><br> |
812 |
|
</td> |
813 |
|
<td valign="top"><br> |
814 |
|
</td> |
815 |
|
</tr> |
816 |
|
<tr> |
817 |
|
<td valign="top"><br> |
818 |
</td> |
</td> |
819 |
<td valign="top"><br> |
<td valign="top"><br> |
820 |
</td> |
</td> |
834 |
</td> |
</td> |
835 |
</tr> |
</tr> |
836 |
<tr> |
<tr> |
837 |
|
<td valign="top">Relational databases ...<br> |
838 |
|
</td> |
839 |
|
<td valign="top">However, |
840 |
|
the relational model, although useful in many contexts, is still limited. |
841 |
|
It's difficult or impossible to express relationships that were not thought |
842 |
|
of by the database model designer.<br> |
843 |
|
<br> |
844 |
|
And indeed, the relational model is designed for machines: accounting, sending checks etc.<br> |
845 |
|
</td> |
846 |
|
<td valign="top"><br> |
847 |
|
</td> |
848 |
|
<td valign="top"><br> |
849 |
|
</td> |
850 |
|
</tr> |
851 |
|
<tr> |
852 |
|
<td valign="top"><br> |
853 |
|
</td> |
854 |
|
<td valign="top"><br> |
855 |
|
</td> |
856 |
|
<td valign="top"><br> |
857 |
|
</td> |
858 |
|
<td valign="top"><br> |
859 |
|
</td> |
860 |
|
</tr> |
861 |
|
<tr> |
862 |
<td valign="top"><br> |
<td valign="top"><br> |
863 |
</td> |
</td> |
864 |
<td valign="top"><br> |
<td valign="top"><br> |
1205 |
|
|
1206 |
|
|
1207 |
<br> |
<br> |
1208 |
|
<br> |
1209 |
</body></html> |
</body></html> |