/[fenfire]/fenfire/docs/pegboard/fenpdf_v1_spec_1--tjl/peg.rst
ViewVC logotype

Diff of /fenfire/docs/pegboard/fenpdf_v1_spec_1--tjl/peg.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.3 by tjl, Tue Jul 29 14:06:36 2003 UTC revision 1.4 by tjl, Wed Jul 30 09:11:45 2003 UTC
# Line 31  Issues Line 31  Issues
31    
32    OTOH, clinks have their uses.    OTOH, clinks have their uses.
33    
34      Hmm, for v1.0 maybe we should have *either* clinks *or*
35      pdf transclusions but not both?
36    
37  - RDF for cursors / bookmarks? Is just two views good enough  - RDF for cursors / bookmarks? Is just two views good enough
38    for browsing? Accidental severing of contacts. Need some way to get anywhere.    for browsing? Accidental severing of contacts. Need some way to get anywhere.
39    
40      PROPOSED RESOLUTION: TREETIME for now.
41    
42  - "overall view" of the whole space? -- embed to 2D somehow for a map?  - "overall view" of the whole space? -- embed to 2D somehow for a map?
43    
44    RESOLVED: Later. Needs experiments first    RESOLVED: Later. Needs experiments first
# Line 42  Issues Line 47  Issues
47    Gives more actions for the mouse, but may be confusing; the UI is definitely    Gives more actions for the mouse, but may be confusing; the UI is definitely
48    not self-explanatory then.    not self-explanatory then.
49    
50      RESOLVED: Later.
51    
52  - Should left-button click+drag select or move?  - Should left-button click+drag select or move?
53    
54    PROPOSED RESOLUTION: move. Shift for select. Clicking and dragging    PROPOSED RESOLUTION: move. Shift for select. Clicking and dragging
# Line 50  Issues Line 57  Issues
57  - Do we need bookmarks and overall views - would simply connecting the previous  - Do we need bookmarks and overall views - would simply connecting the previous
58    and next canvas and pageimagescrolls in time order?    and next canvas and pageimagescrolls in time order?
59    
60  - What were benja's suggestions - couldn't find a PEG    PROPOSED RESOLUTION: Use TREETIME and provide interface for it.
61    
62  - Should the elements in the system contain their insertion time?  - Should the elements in the system contain their insertion time?
63    As wallclock time or a tree (when merging)?    As wallclock time or a tree (when merging)?
64    
65    PROPOSED RESOLUTION: Use TREETIME and provide interface for it.    PROPOSED RESOLUTION: Use TREETIME and provide interface for it.
66    
67    - What were benja's suggestions - couldn't find a PEG
68    
69  Introduction  Introduction
70  ============  ============
71    
# Line 74  in order to keep things simple or for so Line 83  in order to keep things simple or for so
83  FenPDF 1.0 is kind of a "director's cut" (a term Ted sometimes used),  FenPDF 1.0 is kind of a "director's cut" (a term Ted sometimes used),
84  and it's expected that there will be parallel versions, with different  and it's expected that there will be parallel versions, with different
85  names and identities that do almost the same thing but differently.  names and identities that do almost the same thing but differently.
86  These are good for experiments and competition is healthy.  These are good for experiments and competition is healthy -- the same
87    components can be assembled differently by different people.
88    
89  This spec is **extremely** conservative as to which features are taken  This spec is **extremely** conservative as to which features are taken
90  in. We need a working baseline 1.0 that remains the same and functional.  in. We need a working baseline 1.0 that remains the same and functional.
# Line 229  middle mouse button: Line 239  middle mouse button:
239  Context Menus  Context Menus
240  -------------  -------------
241    
242  For any object, "Delete this X" where X is "Text", "Paper", "PDF file", ...  On struct-connected buoys: "Unlink this buoy"
243    
244    For any object, "Delete this X" where X is "Text", "Paper", "PDF file", "transclusion"
245    
246    
247  Visible buttons  Visible buttons
248  ---------------  ---------------
# Line 261  They shall react to mouseovers and mouse Line 274  They shall react to mouseovers and mouse
274  The buttons shall be placed to the upper left corner, stacked vertically, and shall  The buttons shall be placed to the upper left corner, stacked vertically, and shall
275  be relatively small (10-15pixels high)  be relatively small (10-15pixels high)
276    
277    Some space between action buttons and toggles.
278    
279  Versioning / Merging  Versioning / Merging
280  ====================  ====================
281    

Legend:
Removed from v.1.3  
changed lines
  Added in v.1.4

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26