1,183
edits
Support/ScreenshotAnnotator: Difference between revisions
category -> Support Archive
(category -> Support Archive) |
|||
| (3 intermediate revisions by one other user not shown) | |||
| Line 12: | Line 12: | ||
===Syntax requirements=== | ===Syntax requirements=== | ||
* DefaultText and HoverText should support full TikiWiki syntax, meaning '''Bold text''', ''Italic text'', new lines (%%%) and [[Links]] should be supported | * DefaultText and HoverText should support full TikiWiki syntax, meaning '''Bold text''', ''Italic text'', new lines (%%%) and [[Links]] should be supported | ||
(x1,y1),(x2,y2) [Zonelink] Static text with support for wiki syntax | |||
- attrib1 = value1 | |||
- attrib2 = value2 | |||
Hover text which can span across multiple lines | |||
with support for wiki syntax | |||
===Review requirements=== | ===Review requirements=== | ||
| Line 20: | Line 24: | ||
===Style requirements=== | ===Style requirements=== | ||
* All CSS used for e.g. frame border and background, and text style, should be globally part of the theme used on SUMO | * All CSS used for e.g. frame border and background, and text style, should be globally part of the theme used on SUMO | ||
** While testing the plugin, the CSS can be inline | |||
* The wireframe around an annotation should only be visible when the mouse is hovering over the image (which would show all annotation frames). | * The wireframe around an annotation should only be visible when the mouse is hovering over the image (which would show all annotation frames). | ||
** It should be possible to change this behavior with a setting of the plugin (for example, we might want to always show the frames if that proves to be better) | ** It should be possible to change this behavior with a setting of the plugin (for example, we might want to always show the frames if that proves to be better) | ||
| Line 28: | Line 33: | ||
** Clicking on that image should open up a screenshot annotation editor, where the contributor can add/edit/remove annotations for that particular screenshot. | ** Clicking on that image should open up a screenshot annotation editor, where the contributor can add/edit/remove annotations for that particular screenshot. | ||
** The annotations should be loaded from the '''staging copy''' of the article, not the live article. | ** The annotations should be loaded from the '''staging copy''' of the article, not the live article. | ||
*** Nelson says there is a php function in tikiwiki that can modify the contents of a specific tag of a wiki article, so saving this should be fairly straightforward | |||
*** If the clicked screenshot doesn't exist in the staging copy, an error message should be displayed informing that the staging copy has changed. (It could also automatically direct the contributor to the staging copy when this happens.) | *** If the clicked screenshot doesn't exist in the staging copy, an error message should be displayed informing that the staging copy has changed. (It could also automatically direct the contributor to the staging copy when this happens.) | ||
* The annotation editor should show the image in full size, and include Add and Remove buttons. | * The annotation editor should show the image in full size, and include Add and Remove buttons. | ||
| Line 33: | Line 39: | ||
* Selecting an annotation should allow you to enter both hover text and standard text in two text boxes. Again, bold/italic text, as well as links and new lines should be supported. | * Selecting an annotation should allow you to enter both hover text and standard text in two text boxes. Again, bold/italic text, as well as links and new lines should be supported. | ||
* When saving the changes of the annotations, the staging copy should be modified, just like in a normal article edit. Approvers will then be able to review the changes. | * When saving the changes of the annotations, the staging copy should be modified, just like in a normal article edit. Approvers will then be able to review the changes. | ||
==Notes regarding possible way to localize annotations== | ==Notes regarding possible way to localize annotations== | ||
| Line 56: | Line 61: | ||
LPH: yep... if you add a version attribute on the content tag, there is something to do about this. Each region already has a unique identifier | LPH: yep... if you add a version attribute on the content tag, there is something to do about this. Each region already has a unique identifier | ||
[[Category:Support Archive]] | |||