[Gzz-commits] gzz/Documentation/Presentations/ThursdaySeminar...

[Asko Soukka]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Asko Soukka <address@hidden>    03/03/27 04:45:48

Modified files:
        Documentation/Presentations/ThursdaySeminar03: ABSTRACTS 

Log message:
        unindented version with \:Author\:s

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/Presentations/ThursdaySeminar03/ABSTRACTS.diff?tr1=1.16&tr2=1.17&r1=text&r2=text

Patches:
Index: gzz/Documentation/Presentations/ThursdaySeminar03/ABSTRACTS
diff -u gzz/Documentation/Presentations/ThursdaySeminar03/ABSTRACTS:1.16 
gzz/Documentation/Presentations/ThursdaySeminar03/ABSTRACTS:1.17
--- gzz/Documentation/Presentations/ThursdaySeminar03/ABSTRACTS:1.16    Thu Mar 
27 04:40:48 2003
+++ gzz/Documentation/Presentations/ThursdaySeminar03/ABSTRACTS Thu Mar 27 
04:45:48 2003
@@ -1,169 +1,164 @@
-Tuomas J. Lukka, Ph.D, Group Leader
------------------------------------
-
 Gzz postmortem -- Fenfire prenatal
 ==================================
 
-    This spring, the work of our hyperstructure group has
-    undergone significant changes. While the overall goals
-    and directions remain the same, the specific tools had
-    to be changed due to Ted Nelson's actions with his U.S. 
-    patent on zzStructure. 
-
-    Currently, we are using RDF instead of zzStructure
-    as a basis for our next-generation user environment.
-    The underlying philosophy of deep linking simple navigation
-    remains, however, and almost all our technologies and tools
-    are still applicable.
-
-    At the same time, we have split the project on the free software
-    development server Savannah to several subprojects
-    due to their maturity --- some parts should
-    be easily applicable outside fenfire itself.
-
+:Author: Tuomas J. Lukka, Ph.D, Group Leader
 
-Matti J. Katila
----------------
+This spring, the work of our hyperstructure group has
+undergone significant changes. While the overall goals
+and directions remain the same, the specific tools had
+to be changed due to Ted Nelson's actions with his U.S. 
+patent on zzStructure. 
+
+Currently, we are using RDF instead of zzStructure
+as a basis for our next-generation user environment.
+The underlying philosophy of deep linking simple navigation
+remains, however, and almost all our technologies and tools
+are still applicable.
+
+At the same time, we have split the project on the free software
+development server Savannah to several subprojects
+due to their maturity --- some parts should
+be easily applicable outside fenfire itself.
 
 Example application prototypes
 ==============================
 
-    There are various of ways to show information to user.
-    Most of people know only systems with overlapping windows,
-    menus etc. which are common in Windows(tm) like environments.
-    We show some new innovations around user interfaces and
-    combine them with ones that are already known but rarely seen.
-    You are going to see in action: bidirectional links, buoys,
-    fisheye, unique paper background and other techniques available
-    with todays graphic hardware.
-
+:Author: Matti J. Katila
 
-Tuukka Hastrup
---------------
+There are various of ways to show information to user.
+Most of people know only systems with overlapping windows,
+menus etc. which are common in Windows(tm) like environments.
+We show some new innovations around user interfaces and
+combine them with ones that are already known but rarely seen.
+You are going to see in action: bidirectional links, buoys,
+fisheye, unique paper background and other techniques available
+with todays graphic hardware.
 
 Loom browses RDF as hyperstructure
 ==================================
 
-    We want to allow the users to bring together any information
-    items they decide related, no matter which task the
-    information originates from. These connections build a
-    hyperstructure, which should be easy to edit and navigate.
-    Formerly, we used Ted Nelson's zzStructure as the form to this
-    structure, but our current browser utilises the RDF standard.
-
-    Currently, we apply our previous experiences to the RDF browser
-    called Loom. After 4 weeks of development, it can already
-    browse structures and soon also edit. RDF does not have the
-    limits of zzStructure, but we have learned from Gzz how to
-    visualize rich structures.
-
-    RDF is a standard of the World Wide Web Consortium for machine-
-    processable information, and the Semantic Web builds on it.
-    Several other projects are using or evaluating RDF for
-    hypertextual information as well. Others can use Loom for 
-    browsing, and we can make good use of the existing RDF 
-    libraries.
+:Author: Tuukka Hastrup
+
+We want to allow the users to bring together any information
+items they decide related, no matter which task the
+information originates from. These connections build a
+hyperstructure, which should be easy to edit and navigate.
+Formerly, we used Ted Nelson's zzStructure as the form to this
+structure, but our current browser utilises the RDF standard.
+
+Currently, we apply our previous experiences to the RDF browser
+called Loom. After 4 weeks of development, it can already
+browse structures and soon also edit. RDF does not have the
+limits of zzStructure, but we have learned from Gzz how to
+visualize rich structures.
+
+RDF is a standard of the World Wide Web Consortium for machine-
+processable information, and the Semantic Web builds on it.
+Several other projects are using or evaluating RDF for
+hypertextual information as well. Others can use Loom for 
+browsing, and we can make good use of the existing RDF 
+libraries.
 
 ..  zzStructure, but there are several alternatives. We re-evaluated
     some other structures after Ted Nelson received a patent on
     zzStructure and wanted to enforce it, and found RDF better for
     us.
 
-
-Janne V. Kujala, MSc
---------------------
-
 Pre-attentive cues in user interfaces
 =====================================
 
-    Employing the effortless and parallel pre-attentive
-    processes of human vision can yield substantial improvements 
-    in the usability of computer interfaces. We show several
-    examples in our prototype interfaces: Fillets --- smoothing 
-    of sharp angles at the joints --- make the connections in a 
-    graph-like diagram easily discriminable. Unique background 
-    textures help the user instantly identify a familiar 
-    document, even if only a fragment is seen. Tearing instead 
-    of rectangularly clipped viewports makes document fragments 
-    comprehensible at a glance.
-    
+:Author: Janne V. Kujala, MSc
+
+Employing the effortless and parallel pre-attentive
+processes of human vision can yield substantial improvements 
+in the usability of computer interfaces. We show several
+examples in our prototype interfaces: Fillets --- smoothing 
+of sharp angles at the joints --- make the connections in a 
+graph-like diagram easily discriminable. Unique background 
+textures help the user instantly identify a familiar 
+document, even if only a fragment is seen. Tearing instead 
+of rectangularly clipped viewports makes document fragments 
+comprehensible at a glance.
+
 Lego controllers
 ================
 
-    New user interfaces could benefit from customized controllers,
-    but it is expensive to design and produce for a specific 
-    purpose unless standard, mass-produced parts can be used.
-    We show how controllers can be built from a standard mouse
-    and Lego bricks, allowing anyone to reproduce the design
-    without any tools and to easily prototype new designs.
+:Author: Janne V. Kujala, MSc
 
-
-Vesa Kaihlavirta
-----------------
+New user interfaces could benefit from customized controllers,
+but it is expensive to design and produce for a specific 
+purpose unless standard, mass-produced parts can be used.
+We show how controllers can be built from a standard mouse
+and Lego bricks, allowing anyone to reproduce the design
+without any tools and to easily prototype new designs.
 
 Storm
 =====
 
-    Storm (STORage Module) is a library for storing and retrieving data as
-    immutable byte sequences, which are identified by cryptographic
-    content hashes. This allows for addressing two important issues 
-    of data mobility: dangling links and version management.
-
-    Dangling (broken) links are a well-known problem in contemporary hypertext 
networks, 
-    ultimately caused by the links referring to a specific location.
-    In Storm, we assume that location-independent identifiers are resolvable 
-    in an efficient and trusted manner, thus causing links not to dangle.
-
-    Version management allows a user to fluently work with and move between
-    between different versions of a resource. This includes editing
-    the current version, merging it with another version, forking, and 
reverting
-    to older versions.
-
+:Author: Vesa Kaihlavirta
 
-Hermanni Hyytiälä
------------------
+Storm (STORage Module) is a library for storing and retrieving data as
+immutable byte sequences, which are identified by cryptographic
+content hashes. This allows for addressing two important issues 
+of data mobility: dangling links and version management.
+
+Dangling (broken) links are a well-known problem in contemporary
+hypertext networks, ultimately caused by the links referring to a
+specific location.  In Storm, we assume that location-independent
+identifiers are resolvable in an efficient and trusted manner, thus
+causing links not to dangle.
+
+Version management allows a user to fluently work with and move between
+between different versions of a resource. This includes editing
+the current version, merging it with another version, forking, and reverting
+to older versions.
 
 Fenfire and P2P
 ===============
-    
-    We use Peer-to-Peer technologies to build a location transparent,
-    hyperstructured desktop environment. We believe that the properties
-    of Peer-to-Peer technology, such as the ad hoc connectivity and
-    the lack of central authority, are prerequisites while mobilizing
-    the Fenfire system. We wish to use globally unique, semantic-free
-    references for locating data in Peer-to-Peer environment. Our future
-    work includes a implmentation of Fenfire Peer-to-Peer prototype. 
 
+:Author: Hermanni Hyytiälä
 
-Asko Soukka
------------
+We use Peer-to-Peer technologies to build a location transparent,
+hyperstructured desktop environment. We believe that the properties
+of Peer-to-Peer technology, such as the ad hoc connectivity and
+the lack of central authority, are prerequisites while mobilizing
+the Fenfire system. We wish to use globally unique, semantic-free
+references for locating data in Peer-to-Peer environment. Our future
+work includes a implmentation of Fenfire Peer-to-Peer prototype. 
 
 Navidoc
 =======
 
-    Navidoc is a collection of lightweight tools built to support our
-    project's documentation. Navidoc expands UML diagrams embedded in
-    design documentation to work as multi-ended links, which 
-    hypertextually connect design documentation to Javadoc generated 
-    documentation. For describing UML diagrams, Navidoc provides a 
-    readily-authored lexical language, which can be written within 
-    design documentation. The example of Navidoc enhanced documentation 
-    could be found at http://himalia.it.jyu.fi/gzzdoc/
+:Author: Asko Soukka
+
+Navidoc is a collection of lightweight tools built to support our
+project's documentation. Navidoc expands UML diagrams embedded in
+design documentation to work as multi-ended links, which 
+hypertextually connect design documentation to Javadoc generated 
+documentation. For describing UML diagrams, Navidoc provides a 
+readily-authored lexical language, which can be written within 
+design documentation. The example of Navidoc enhanced documentation 
+could be found at http://himalia.it.jyu.fi/gzzdoc/
 
 ..  - developed as byproduct
       * components/features added when needed
+
     - Navidoc
       * linking different documentations via UML diagrams
-       + design documentation
-       + javadoc
-       + lexically described UML diagrams within design documentation
-       + postprocessing html files, adding imagemaps and images,
+       + design documentation
+       + javadoc
+       + lexically described UML diagrams within design documentation
+       + postprocessing html files, adding imagemaps and images,
           creating crosslinks/backlinks
+
       * Gzz's documentation in himalia as example
+
     - built especially to fit for our needs, to fit and support
       our software development process
+
       * usable with any text editor
       * use of open software toolchain
+
     - using reStructuredText
       * documentation and code could be written with same tools
       * "language" could be expanded with directives
@@ -171,23 +166,22 @@
       * describing diagrams is easy, placing could be difficult
       * (pegboard)
       * (latex writer)
+
     - test framework
       * adopting XP, importance of writing tests
       * framework minimizes the gap of writing and running test
 
-
-Tuomas J. Lukka
----------------
-
 Closing remarks
 ===============
 
-    The graphical interfaces in the demos shown above were written in
-    libvob, of which we didn't have an opportunity to discuss more -
-    please contact us for details.  We are planning to spin off more
-    subprojects in the future as they mature.
-
-    As an overall vision for the project, the basic idea is to keep
-    doing what we are doing, working on cool stuff and trying
-    to make a computer environment we would like to use ourselves.
+:Author: Tuomas J. Lukka
+
+The graphical interfaces in the demos shown above were written in
+libvob, of which we didn't have an opportunity to discuss more -
+please contact us for details.  We are planning to spin off more
+subprojects in the future as they mature.
+
+As an overall vision for the project, the basic idea is to keep
+doing what we are doing, working on cool stuff and trying
+to make a computer environment we would like to use ourselves.