1. 30 Nov, 2013 1 commit
  2. 28 Nov, 2013 8 commits
    • csillag's avatar
      DTM changes · 4e1b8ce3
      csillag authored
       * Updated dom-text-mapper to 3fb30bee (master branch)
       * Updated Annotator to 631c1345 (typed-packaging branch)
      
      These are all internal DTM / Annotator changes.
      The communcation about DOM changes has migrated from method calls
      to events.
      
      See also https://github.com/hypothesis/dom-text-mapper/issues/14
      4e1b8ce3
    • csillag's avatar
      When hovering the mouse over a visible highlight, add a drop shadow to the... · 3924bae4
      csillag authored
      When hovering the mouse over a visible highlight, add a drop shadow to the annotation card in the sidebar.
      
      Fixes #918.
      Also fixes #957.
      3924bae4
    • csillag's avatar
      50486382
    • csillag's avatar
      Migrated some H-specific stuff from Annotator level to H · 46675758
      csillag authored
       * Updated Annotator to 3d4ae840 (typed-packaging branch).
         In this version, the `noDocAccess` option has been removed.
       * Added the required (noop) overrides to regain the same functionality
      46675758
    • csillag's avatar
      555ab769
    • csillag's avatar
      Resurrect the forced-login support · a228b13c
      csillag authored
      Also did some cosmetical changes.
      
      Fixes #953.
      a228b13c
    • csillag's avatar
      Selection and adder-related fixes · f7c44667
      csillag authored
       * Update Annotator to bbad33fe (typed-packaging branch),
         which has some adder-related tweaks/fixes.
         (More sane encapsulation of the `canAnnotate` behavior,
         following suggestions from @gergely-ujvari)
       * Copy Annotator's changes to our overrides:
         * In `onAdderClick()`, set `inAdderClick`
         * In `onSuccessfulSelection()`, return false when annotating is forbidden
       * Upon building the channels between the guest and sidebar,
         synchronize the enableAnnotating state.
      
      Really fixes #949.
      f7c44667
    • csillag's avatar
      Add protection against adding new annotations while editing · 74eef1d0
      csillag authored
       * Update Annotator to dd6f102d (typed-packaging branch)
         * Several internal fixes, tweaks and cosmetic changes
           (Now it's fully functional in Stand-alone mode, again.)
       * Follow Annotator API changes
         * `noMatcing` option renamed to `noDocAccess`
         * `ignoreMouseUp` option renamed to `canAnnotate`,
            and the semantics got inverted
       * The bridge plugin now propagates the 'enableAnnotating' events
       * Added an `isEmpty` method to the draft service
       * When editing/replying/canceling/saving in the sidebar,
         enable/disable annotating.
      
      Fixes #949
      74eef1d0
  3. 27 Nov, 2013 6 commits
  4. 26 Nov, 2013 11 commits
  5. 25 Nov, 2013 2 commits
  6. 22 Nov, 2013 2 commits
  7. 18 Nov, 2013 1 commit
  8. 16 Nov, 2013 1 commit
  9. 15 Nov, 2013 3 commits
    • csillag's avatar
      Update Annotator to b055f169b (bugfix) · 568f5fa9
      csillag authored
      568f5fa9
    • Kristof Csillag's avatar
      Merge pull request #924 from hypothesis/380-typed-anchors-4 · 16215622
      Kristof Csillag authored
      Introducing typed anchor support
      16215622
    • csillag's avatar
      Introducing typed anchor support · bcadbfd8
      csillag authored
       * Updated Annotator to de4c0dfc (maintenance branch), which has
         typed anchors support merged.
         See https://github.com/hypothesis/annotator/pull/18 for explanation.
      
      The H specific parts:
      
       * Following Annotator API and packaging changes
       * The heatmap got a lot trickier. Since it can no longer make any
         assumption about the actual implementation of the highlights and
         anchors, now it does not rely on any data inside them. That includes
         the start and stop character offsets, too, which was previously used
         to find the nearest anchor for the up/down arrows on.
         We can't assume that all anchors have that data.
         Unfortunately, the Y coordinate is not always available, because
         the required part of the DOM might not be rendered yet.
         So the only data we have is the page number. (All anchors have page
         numbers). In the first phase, we only collect the anchors from the
         nearest page. Then we go there, to assure that it's rendered.
         When all the anchors have been realized, we select the nearest one,
         and actually scroll to it. This way, we can make it work with
         all kinds of anchors/highlights.
      bcadbfd8
  10. 12 Nov, 2013 5 commits