1. 08 Apr, 2016 2 commits
    • chdorner's avatar
      302ce020
    • chdorner's avatar
      Add our own simpler implementation of the page npm package · 8ae72ed6
      chdorner authored
      We don't need all the client-side routing part, we only need to be able
      to selectively run certain JavaScript code depending on which site the
      user is at the moment.
      This implementation is not as advanced as the one from the `page`
      package, or what is possible with the `url-pattern` package. But we
      don't need any fancy URL matching at the moment, once we do we can
      revisit and maybe introduce something like `url-pattern` instead of just
      a crude `document.location.pathname === path`.
      8ae72ed6
  2. 06 Apr, 2016 9 commits
  3. 05 Apr, 2016 4 commits
    • Christof Dorner's avatar
      Merge pull request #3151 from hypothesis/postgres-write-models · 17e6556c
      Christof Dorner authored
      Postgres Write 2/4: Model code for creating new annotations in Postgres
      17e6556c
    • Nick Stenning's avatar
      Merge pull request #3038 from hypothesis/client-live-reload · e80973ec
      Nick Stenning authored
      Live reload development tool for Hypothesis client
      e80973ec
    • Robert Knight's avatar
      Debounce live-reload notifications · 386e3552
      Robert Knight authored
      If multiple asset bundles are regenerated in quick succession, including
      JS or template files, the client might try to reload whilst some of the
      bundles are still being regenerated, resulting in the client failing to
      load.
      
      This commit reduces the likelihood of this happening by debouncing
      live-reload notifications and makes a note of the issue.
      386e3552
    • Robert Knight's avatar
      Live reload dev tool for the Hypothesis client · 70f5676d
      Robert Knight authored
      This implements support and a test environment
      in which the Hypothesis client can live reload
      when scripts, styles etc. are changed.
      
      Live reloading when scripts change currently requires
      support from the hosting page.
      
      There are two parts to this:
      
       - A server which serves test pages
         with the Hypothesis client embedded and notifies
         it when front-end assets (styles, scripts) are changed.
      
         Test pages are served at http://localhost:3000/<any path>
         by default.
      
       - A small client script which connects to the server and
         listens for notifications of asset changes.
      
         When styles change it will reload styles for the page.
      
         When scripts or Angular templates change it will send a
         request to the top-level page to reload.
      
         This enables reloading to work when changing
         both the sidebar app and Annotator code but also avoids
         the need to manually unload the existing Annotator instance
         before reloading.
      70f5676d
  4. 04 Apr, 2016 2 commits
  5. 01 Apr, 2016 17 commits
  6. 31 Mar, 2016 4 commits
  7. 30 Mar, 2016 2 commits
    • Sean Hammond's avatar
      Merge pull request #3133 from hypothesis/t256-preserve-selection-after-login · c1ee9ae0
      Sean Hammond authored
      Preserve selection when switching accounts
      c1ee9ae0
    • Robert Knight's avatar
      Preserve selection when switching accounts · 347dcefa
      Robert Knight authored
      When visiting a direct-linked annotation (ie. #annotations:<id> is
      present in the URL) we want to preserve the selection when the user
      signs in, whether the annotation was private or in a group, in which
      case they will need to sign in to see it, or public, in which case they
      might need to sign in to reply.
      
      Previously public direct-linked annotations became deselected when
      signing in because they were unloaded when switching accounts, and this
      fired the same ANNOTATION_DELETED event as when an annotation is
      removed, which results in the annotation being removed from the
      selection.
      
      This commit enables the selection to be preserved by introducing a
      different event within the app when annotations are unloaded vs.
      deleted. When an annotation is unloaded, it is not removed from the
      selection.
      347dcefa