Contents of /contributions/modules/annotationfield/USER_INTERFACE

--------------------------------
Life of an Annotation Value
--------------------------------
This is what I believe to be best practice.  When people annotate only
one thing in one way, we can vary this process, but we cause user
confusion when annotating different objects/types behave differently.

CREATE
(if a single field/annotator pair is available then start at #3)
1. pre-action (optional)
	* highlight text
	* seek in video
2. AnnotationController action:
	* choose field (to create action)
		* choose annotator if there is more than one (possibly in one click)
3. form widget exposed 
	* other form items from the annotationfield's node are available
	now too, e.g. title/body/tag
4. if pre-action, prepopulate form
5. allow for further annotation editing (implicit save-ability/overwrite of actions here)
   Update buttons like 'Set Start Time' or 'Update Selection' should change margin-markers
   Opportunity here to:
	* add another annotation (to same field)
	* cancel/delete
	* replant annotation (choose a different node/field)

EDIT
1. Click to edit annotation node (if more than one)
2. Annotation values should be represented in the fields margins as well
	(preferably below the field, but for text, e.g.--the side)
	* In View mode, this might:
		- toggle annotation's visibility
		- show annotation details
	* In Edit mode, this should:
		-activate annotation value
3. Activate annotation value (first is activated by default)
4. We are now at #5 from CREATE


COLOR
* Each annotator needs to specify the type of color that is compatible.
  Options are:
	- background (e.g. for highlighted text)
	- foreground (e.g. video/audio clip bar)
	- user toggle:light/dark (e.g. for outlines over an image)
Colors should stay available to the system to communicate additional 
information like:
	- creator
	- date
	- system type (e.g. comment, diff, suggestion, alternative, translation)
	- grouping (e.g. tag)


--------------------------------
Guidelines when working out UI
--------------------------------
Don't worry about this stuff too much.
Instead, focus on what you want people annotating
and what they are communicating with the annotation
(to themselves or others)
1	--------------------------------
2	Life of an Annotation Value
3	--------------------------------
4	This is what I believe to be best practice. When people annotate only
5	one thing in one way, we can vary this process, but we cause user
6	confusion when annotating different objects/types behave differently.
7
8	CREATE
9	(if a single field/annotator pair is available then start at #3)
10	1. pre-action (optional)
11	* highlight text
12	* seek in video
13	2. AnnotationController action:
14	* choose field (to create action)
15	* choose annotator if there is more than one (possibly in one click)
16	3. form widget exposed
17	* other form items from the annotationfield's node are available
18	now too, e.g. title/body/tag
19	4. if pre-action, prepopulate form
20	5. allow for further annotation editing (implicit save-ability/overwrite of actions here)
21	Update buttons like 'Set Start Time' or 'Update Selection' should change margin-markers
22	Opportunity here to:
23	* add another annotation (to same field)
24	* cancel/delete
25	* replant annotation (choose a different node/field)
26
27	EDIT
28	1. Click to edit annotation node (if more than one)
29	2. Annotation values should be represented in the fields margins as well
30	(preferably below the field, but for text, e.g.--the side)
31	* In View mode, this might:
32	- toggle annotation's visibility
33	- show annotation details
34	* In Edit mode, this should:
35	-activate annotation value
36	3. Activate annotation value (first is activated by default)
37	4. We are now at #5 from CREATE
38
39
40	COLOR
41	* Each annotator needs to specify the type of color that is compatible.
42	Options are:
43	- background (e.g. for highlighted text)
44	- foreground (e.g. video/audio clip bar)
45	- user toggle:light/dark (e.g. for outlines over an image)
46	Colors should stay available to the system to communicate additional
47	information like:
48	- creator
49	- date
50	- system type (e.g. comment, diff, suggestion, alternative, translation)
51	- grouping (e.g. tag)
52
53
54	--------------------------------
55	Guidelines when working out UI
56	--------------------------------
57	Don't worry about this stuff too much.
58	Instead, focus on what you want people annotating
59	and what they are communicating with the annotation
60	(to themselves or others)