RE: Cursors

System for holding shared informaion on non-content.

tag {
  Position ( first character effected )
  Owner    ( unique within scope of editor )
  Index    ( uniquie within scope of owner )
  Type     ( reference for forign translation )
}

TypeTable {
  Endpoint ( 0 = unused, 1 = start, 2 = end, 3 = single )
  TypeDesc ( cursor, bookmark ... )
}
 
 
Non content dynamic positional markers:
cursors
bookmarks
frameMarker

-----

Important realization here that accumulator is responcable for holding
 all content related information, this means fonts / colours and that
 this 'other' system is for information not part of the result when saved.
 
 --------------
 
 stages of cursor hilighting during screen draw:
 - finding out what tags apply to the draw region
 - finding out what the user wants done with the various tags
 - prioratizing the tags
 - building the resulting attribute map
 
 these need to be bound with an object...
 The storage part of the object needs to be shared in a networked environment
 A linked list seem apropriot
 Something similar to the accumulator
 ?????Filter
 Props
 FieldPropsFilter
 The storage and access objects should be different
 PropAccumulator // > = internal
   - add prop
   - delete prop
   - >sort props
   - get prop
   - modify prop
   - clear props (varoius scopes)
 PropFilter
   - >prop search (position)
   - >sort props (user defined z leveling)
   - >map props (use z leveling to make an attribute map (or as user defined))
   - do props ( position ) ( general wrapper )
   - SetSource ( accumulator )
   
 how to speed up drawing of 'sequential' characters...
 
 draw system should be changed to buffer the screen before its refreshed.
 
 
 
 
