gzz-commits
[Top][All Lists]
Advanced

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

[Gzz-commits] manuscripts/FutureVision vision.rst


From: Benja Fallenstein
Subject: [Gzz-commits] manuscripts/FutureVision vision.rst
Date: Thu, 18 Sep 2003 08:11:40 -0400

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/09/18 08:11:40

Modified files:
        FutureVision   : vision.rst 

Log message:
        applitudes

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/FutureVision/vision.rst.diff?tr1=1.80&tr2=1.81&r1=text&r2=text

Patches:
Index: manuscripts/FutureVision/vision.rst
diff -u manuscripts/FutureVision/vision.rst:1.80 
manuscripts/FutureVision/vision.rst:1.81
--- manuscripts/FutureVision/vision.rst:1.80    Thu Sep 18 07:47:41 2003
+++ manuscripts/FutureVision/vision.rst Thu Sep 18 08:11:40 2003
@@ -163,6 +163,32 @@
 (There may be more than one view available for the same item.
 The user can choose between alternative views through a menu.)
 
+A user would be able to **choose the views appropriate for the
+task at hand**, which may come **from different sources**. 
+The historian's map and timeline views may have been developed
+independently, for completely different purposes, and it may
+have been the user who re-purposed them for their work.
+(For convenience, the user may create menus and choose
+view defaults for each task, providing quick access
+to the functionality needed for this task.)
+
+Instead of forcing the user to think in applications,
+such a system lends itself to be structured around
+the user's tasks. Nelson [XXXfwref] uses the term
+**applitude** for such a "[zone] of functionality."
+An applitude is not "walled off" from the rest of the
+system; when information from a different applitude
+is needed, it is always available. 
+
+Items are **not owned
+by any single applitude**: When you need to connect
+information to an item that doesn't fit into the
+current applitude, you can always do so by creating
+a new type of relationship. Items **may have roles
+in more than one applitude**; for example, a person
+may exist both in our scheduling applitude, and
+the address book we use when writing e-mail.
+
 Such an environment would not only help us structure the
 information we already store in our computers, it may also
 help us to **organize our thoughts**.




reply via email to

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