gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/FutureVision oplan.txt plan.txt


From: Tuomas J. Lukka
Subject: [Gzz-commits] manuscripts/FutureVision oplan.txt plan.txt
Date: Wed, 12 Nov 2003 16:23:46 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Tuomas J. Lukka <address@hidden>        03/11/12 16:23:38

Modified files:
        FutureVision   : oplan.txt plan.txt 

Log message:
        sync

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/FutureVision/oplan.txt.diff?tr1=1.7&tr2=1.8&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/FutureVision/plan.txt.diff?tr1=1.14&tr2=1.15&r1=text&r2=text

Patches:
Index: manuscripts/FutureVision/oplan.txt
diff -u manuscripts/FutureVision/oplan.txt:1.7 
manuscripts/FutureVision/oplan.txt:1.8
--- manuscripts/FutureVision/oplan.txt:1.7      Wed Nov 12 07:58:57 2003
+++ manuscripts/FutureVision/oplan.txt  Wed Nov 12 16:23:24 2003
@@ -24,7 +24,9 @@
     Things currently represented by files or folders,
     such as documents or projects, are usually
     items, but there are several items that are not files:
-    appointments, emails, ...
+    appointments (often all appointments are stored
+    in a binary, proprietary database file by programs), 
+    emails (usually several stored in one file), ...
 
     XXX
     
@@ -54,6 +56,21 @@
 
 ...
 
+Example images of a small structure and different views of it: [42]
+    
+    Two persons, a meeting, ?
+
+Mockup of different views, showing the local structure in as different
+ways as possible.
+
+Also: Views are not versioned; the structure is.
+Providing versioning information in the structure as *reflected*
+information (Example!) makes it easier to build views
+that can *show* the versioning, and allow the user
+to merge different users' changes to a document.
+
+The views simply show whatever they see in the structure
+around a given set of *focus* items.
 
 3.1 Zzstructure (used in ZigZag(tm))
 ------------------------------------
@@ -108,6 +125,7 @@
     we have to simultaneously replace the 
     backend structure and the entire user-interface framework.
 
+Mention "Research prototype, &c"
 
 4.1 Structures
 --------------
@@ -201,14 +219,22 @@
     example in the Cyc (XXXCite) and SemNet (XXXCite) projects, which allowed 
the user 
     to navigate through the graph locally, with one node as the *focus*,
     and showing the 
-    Later, similar visualizations were also used in the commercial
-    product TheBrain(XXXCite), to allow users to organize files on their
-    computers.
+    Later, a similar style of navigation and structural
+    editing was also used in the commercial
+    product TheBrain(XXXCite), to allow users to organize files 
+    and "thoughts" on their computers.
+
+Should we mention the following?: "These are not the only user interfaces 
+to such a structure - there are several other possibilities;
+with a well-defined hyperstructure, creating different, interesting
+visualizations is easy"
 
 5.5 Open Hypermedia
 -------------------
 
 [11] Change reference
+(I'd rather *add* the older one, and keep the FOHM to 
+say how they're moving towards an unified structure --Tjl)
 
 
 5.6 Fluid Links and Transpointing Windows
Index: manuscripts/FutureVision/plan.txt
diff -u manuscripts/FutureVision/plan.txt:1.14 
manuscripts/FutureVision/plan.txt:1.15
--- manuscripts/FutureVision/plan.txt:1.14      Tue Nov 11 21:38:15 2003
+++ manuscripts/FutureVision/plan.txt   Wed Nov 12 16:23:30 2003
@@ -203,3 +203,7 @@
 
   - XXX put points here
 
+- views! [42]
+    
+    - explain what a view is, that it's not versioned but the
+      *structure* is




reply via email to

[Prev in Thread] Current Thread [Next in Thread]