gzz-commits
[Top][All Lists]
Advanced

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

[Gzz-commits] fenfire/docs/pegboard/fenpdf_v1_spec_1--tjl peg...


From: Tuomas J. Lukka
Subject: [Gzz-commits] fenfire/docs/pegboard/fenpdf_v1_spec_1--tjl peg...
Date: Fri, 01 Aug 2003 04:45:55 -0400

CVSROOT:        /cvsroot/fenfire
Module name:    fenfire
Branch:         
Changes by:     Tuomas J. Lukka <address@hidden>        03/08/01 04:45:55

Modified files:
        docs/pegboard/fenpdf_v1_spec_1--tjl: peg.rst 

Log message:
        formatting

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/fenfire/fenfire/docs/pegboard/fenpdf_v1_spec_1--tjl/peg.rst.diff?tr1=1.7&tr2=1.8&r1=text&r2=text

Patches:
Index: fenfire/docs/pegboard/fenpdf_v1_spec_1--tjl/peg.rst
diff -u fenfire/docs/pegboard/fenpdf_v1_spec_1--tjl/peg.rst:1.7 
fenfire/docs/pegboard/fenpdf_v1_spec_1--tjl/peg.rst:1.8
--- fenfire/docs/pegboard/fenpdf_v1_spec_1--tjl/peg.rst:1.7     Fri Aug  1 
02:09:55 2003
+++ fenfire/docs/pegboard/fenpdf_v1_spec_1--tjl/peg.rst Fri Aug  1 04:45:55 2003
@@ -4,8 +4,8 @@
 
 :Authors:  Tuomas J. Lukka
 :Date-Created: 2003-07-28
-:Last-Modified: $Date: 2003/08/01 06:09:55 $
-:Revision: $Revision: 1.7 $
+:Last-Modified: $Date: 2003/08/01 08:45:55 $
+:Revision: $Revision: 1.8 $
 :Status:   Incomplete
 :Stakeholders: benja, mudyc, humppake
 :Scope:    Major
@@ -34,91 +34,91 @@
   Hmm, for v1.0 maybe we should have *either* clinks *or*
   pdf transclusions but not both?
 
-  RESOLVED: Later. Again, not absolutely vital
+      RESOLVED: Later. Again, not absolutely vital
 
-  [benja]
-  If we have content links but not PDF transclusions, we need content
-  links to text -> bit difficult to show.
- 
-  Or, a way to make a link between a node and an enfilade. That could
-  actually be good... hm. To the user, it would be functionally very
-  similar to a structlink.
- 
-  Transclusion is probably better if we have only one of the two, but
-  having both would also be good.
- 
-  If we have clinks, when the user has selected a piece of PDF, it would
-  be good to have a "Create link" button which creates a new paper with an
-  empty node that's linked to the PDF. Actually, would also be good to
-  have this when the user is on a canvas and has selected a text node.
-  Then this would be a simple, universal way of creating a new annotation
-  to something.
- 
-  Or maybe "make paper" should always work like this if there's a selected
-  node? When making a new paper, you almost always want it to be linked to
-  the current paper?
- 
-  For text nodes it could also be in the context menu (if we don't have a
-  way to select them in the interface)...
+      [benja]
+      If we have content links but not PDF transclusions, we need content
+      links to text -> bit difficult to show.
+     
+      Or, a way to make a link between a node and an enfilade. That could
+      actually be good... hm. To the user, it would be functionally very
+      similar to a structlink.
+     
+      Transclusion is probably better if we have only one of the two, but
+      having both would also be good.
+     
+      If we have clinks, when the user has selected a piece of PDF, it would
+      be good to have a "Create link" button which creates a new paper with an
+      empty node that's linked to the PDF. Actually, would also be good to
+      have this when the user is on a canvas and has selected a text node.
+      Then this would be a simple, universal way of creating a new annotation
+      to something.
+     
+      Or maybe "make paper" should always work like this if there's a selected
+      node? When making a new paper, you almost always want it to be linked to
+      the current paper?
+     
+      For text nodes it could also be in the context menu (if we don't have a
+      way to select them in the interface)...
 
 - RDF for cursors / bookmarks? Is just two views good enough
   for browsing? Accidental severing of contacts. Need some way to get anywhere.
 
-  PROPOSED RESOLUTION: TREETIME for now.
+      PROPOSED RESOLUTION: TREETIME for now.
 
 - "overall view" of the whole space? -- embed to 2D somehow for a map?
 
-  RESOLVED: Later. Needs experiments first
+      RESOLVED: Later. Needs experiments first
 
 - ``rmb_action_switch--humppake``?
   Gives more actions for the mouse, but may be confusing; the UI is definitely
   not self-explanatory then.
 
-  RESOLVED: Later.
+      RESOLVED: Later.
 
 - Should left-button click+drag select or move?
 
-  PROPOSED RESOLUTION: move. Shift for select. Clicking and dragging
-  for moving *feels* right.
+      PROPOSED RESOLUTION: move. Shift for select. Clicking and dragging
+      for moving *feels* right.
 
 - Do we need bookmarks and overall views - would simply connecting the previous
   and next canvas and pageimagescrolls in time order?
 
-  PROPOSED RESOLUTION: Use TREETIME and provide interface for it.
+      PROPOSED RESOLUTION: Use TREETIME and provide interface for it.
 
 - Should the elements in the system contain their insertion time?
   As wallclock time or a tree (when merging)?
 
-  PROPOSED RESOLUTION: Use TREETIME and provide interface for it.
+      PROPOSED RESOLUTION: Use TREETIME and provide interface for it.
 
 - [benja] How is TREETIME supposed to be *shown*?
 
 - [benja] Will transclusions of *text* be supported, and if so, how?
 
-  PROPOSED RESOLUTION: Later
+      PROPOSED RESOLUTION: Later
 
 - [benja] I don't like the overloading of click+drag. Isn't there a
   better way? Maybe Shift+drag to create the transclusion after
   selecting? Hm.
 
-  RESOLUTION: Shift+drag is not possible, as it needs to 
-  start another selection reliably. See next issue.
+      RESOLUTION: Shift+drag is not possible, as it needs to 
+      start another selection reliably. See next issue.
 
 - [benja] What actions *destroy* the current selection (unselect it)?
   Should every click destroy the selection? (Even panning?) If so, maybe
   the click+drag to create transclusion could be tolerable.
 
-  RESOLUTION: Yes, every click destroys the selection. This way,
-  there will be no annoying things that get easily stuck.
+      RESOLUTION: Yes, every click destroys the selection. This way,
+      there will be no annoying things that get easily stuck.
  
 - [benja] Shift+click+drag is certainly not something you can figure
   you can just figure out (see requirements). What to do about that?
 
-  PROPOSED RESOLUTION: Text in the background always: shift-drag to select?
+      PROPOSED RESOLUTION: Text in the background always: shift-drag to select?
  
 - [benja] How to adjust the view separator position without middle button?
 
-  RESOLUTION: Later - in 1.1. In 1.0, assume middle button.
+      RESOLUTION: Later - in 1.1. In 1.0, assume middle button.
 
 - [benja] How to create structlinks
 
@@ -133,8 +133,8 @@
  
 - [benja] How to unlink two nodes on same paper?
 
-  RESOLUTION: In v1.0, the nodes would be shown as buoys,
-  so in the usual way.
+      RESOLUTION: In v1.0, the nodes would be shown as buoys,
+      so in the usual way.
 
 
 




reply via email to

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