search

austgl / keynote-nf

Automatically exported from code.google.com/p/keynote-nf
0 stars 0 forks source link

New kind of virtual nodes: links to other nodes (Mirror nodes) #57

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The objetive is to let nodes to be in several positions simultaneously, in
the same or in different notes. It will be like file links in Unix. Changes
made to one node will be applied to the virtual nodes related and
viceversa. Indeed they both will share the same content.

With this new kind of node it will be possible:
- Organize the information in different ways. For example we can group
nodes as tasks in a note, ordering by priority, and at the same time,
hanging that nodes from other nodes (or in other notes) based in a
functionality approach.

- In ocassions, when we are working with one node, can be useful to have
other node/s with related information (that resides in other point, for any
reason) near to first one. We can use hyperlinks, but jumping from one to
others is sometimes a little messy.

- Personally for me it is very useful (it is a necessity) to have a
selection of certain nodes (certain tasks, for example) in a different note
(tab). There I will be able to have a global vision of the main things to
do, sorting, ranking and structuring in a free tree hierarchy, completely
independent of the hierarchy in wich 'real' nodes reside, classified by
other criterion.

- A 'view' of nodes with alarm set could be offered, in a new note, or
hanging of any node.

- The result of a search may be used to create views of information,
selection of virtual nodes.  In general we can copy a hyperlink to a
keynote location and paste as a virtual node.

- Also, it will be possible to create dynamic notes, wich will include all
the nodes satisfying a certain search criterion. If finally I implement
some kind of tag managing, we could create a note with all the nodes
including certain tag or combination of tags, or etc.

Original issue reported on code.google.com by dpra...@gmail.com on 15 Feb 2009 at 9:39

GoogleCodeExporter commented 9 years ago 
Implemented in revision r53

To implement this functionality has been defined a new type of virtual node
(vmKNTNode): TVirtualMode = (vmNone, vmText, vmRTF, vmHTML, vmIELocal, 
vmIERemote,
vmKNTNode). Has been necessary to widen KNT file format, including a new 
optional
marker (VN)

It has been defined a new icon for this node, for use with option 'Standard 
icons'

Can create such virtual nodes (called mirror nodes) in several ways:
- Virtual Node -> Insert Mirror node
  Inserts a new node, mirror of the currently selected node.

- Transfer Subtree -> Graft Subtree Here as Mirror
  Alternative to Graft Subtree Here. It is equivalent but pasting mirror nodes
instead of usual nodes. Also, unlike the previous one, considers only nodes not
hidden. This has been done to facilitate their use in conjunction with the 
option
'Filter Tree note' in the search of the resource panel. This way is easily 
possible
to create mirrors of the nodes that satisfy a condition, if the tree is filtered
beforehand.

The mirror node can be created on any node, without distinction, whether another
virtual node, for example to a file. In the case of trying to create a  mirror 
node
on another mirror node what is created is a new mirror on node pointed by the 
first one.

It is possible to unlink the mirror node, just as is already allowed with 
existing
virtual nodes. The node will be an independent copy. The mechanism is the same:
  Virtual Node -> Unlink Node

You can navigate from one mirror node to the node to which it points.
  Virtual Node -> Navigate to Non Virtual

Mirror nodes share the contents with the nodes they point to. They also share:
- The state of the property Checked. 
- Alarms. There will be only one alarm: set or remove alarm on one node will 
set or
remove on the others.

Both the non virtual node as all mirror nodes that might point to it are 
equivalent
and delete or move one of them, whether virtual or not, not invalidate the 
remaining.
For this, if the current 'real' node is removed, one of the remaining virtual 
nodes
(mirrors) will act as a new real node and the rest of the mirrors will point to 
it.
In this sense function as links in Unix.

Original comment by dpra...@gmail.com on 3 Mar 2009 at 11:57

GoogleCodeExporter commented 9 years ago 
Were some outstanding things like removing notes or merging notes from Tools.
Implemented/fixed in revision r54

Original comment by dpra...@gmail.com on 8 Mar 2009 at 8:52

GoogleCodeExporter commented 9 years ago 
It is possible to test this new functionality with the beta version 
downloadable from
the following direction:
http://groups.google.com/group/keynote-nf/files

as it is indicated in wiki/LastVersion_BETA

Original comment by dpra...@gmail.com on 8 Mar 2009 at 9:41

GoogleCodeExporter commented 9 years ago 
An error associated to revision r53 : Notes of standard Rich text editor (not
multi-tree) were not shown when tabs changed.

Resolved in revision r58

Original comment by dpra...@gmail.com on 15 Mar 2009 at 5:04

GoogleCodeExporter commented 9 years ago

Original comment by dpra...@gmail.com on 17 Mar 2009 at 6:56