1. 07 Mar, 2016 1 commit
  2. 04 Mar, 2016 8 commits
  3. 03 Mar, 2016 2 commits
  4. 02 Mar, 2016 2 commits
    • Robert Knight's avatar
      Use Element.scrollIntoView() to scroll new annotations into view · dbbeadf8
      Robert Knight authored
      The previous method of scrolling a newly created annotation
      into view in the sidebar resulted in the input field for
      the new annotation losing focus.
      
      Note that only top level annotations have an 'id'
      attribute set on the corresponding HTML element.
      It might make sense to change this in future although
      it would add an extra binding. For now I've just noted this.
      dbbeadf8
    • Robert Knight's avatar
      Focus annotation editor when a new annotation is created · ec0e0f9f
      Robert Knight authored
      When a new annotation card was added, the sidebar tried
      to focus it but this failed because the sidebar iframe
      itself did not have focus.
      
      When a new annotation is created, first focus the sidebar
      in the Annotator host and then let the sidebar focus the
      input field.
      
       * Remove unnecessary use of the $timeout service which
         triggers a root scope digest.
      ec0e0f9f
  5. 01 Mar, 2016 8 commits
  6. 29 Feb, 2016 6 commits
  7. 26 Feb, 2016 7 commits
  8. 25 Feb, 2016 6 commits
    • Nick Stenning's avatar
      Merge pull request #3015 from hypothesis/b9PFMDM7-add-activate-button-to-admin-users-page · 6e25ab1c
      Nick Stenning authored
      Enable admins to activate users
      6e25ab1c
    • Sean Hammond's avatar
      Enable admins to activate users · 6c9e4f61
      Sean Hammond authored
      Add an "Activate" button next to users on the /admin/users page so that
      admins can activate user accounts.
      
      Some refactoring to avoid code duplication between activating by users
      clicking on an activation link and admins clicking the new activate button:
      move the code that actually activates the user onto the User model where
      both views can call it.
      6c9e4f61
    • Sean Hammond's avatar
      Make hound run jscs · f0882ffc
      Sean Hammond authored
      f0882ffc
    • Robert Knight's avatar
      Merge pull request #3018 from hypothesis/packaging-cleanups · 1a6112f8
      Robert Knight authored
      Packaging cleanups
      1a6112f8
    • Nick Stenning's avatar
      Merge pull request #2979 from hypothesis/editor-js-conversion-and-tests · 2dc90311
      Nick Stenning authored
      Convert <markdown> component to JS and add basic tests
      2dc90311
    • Nick Stenning's avatar
      Clean up Makefile · 73769fe2
      Nick Stenning authored
      This commit moves a couple of helper tasks for developing the frontend
      into the gulpfile, and also improves the automatic installation of
      dependencies and building of assets.
      
      All that is now required to get a running development server (with built
      frontend assets) from a fresh checkout of the repository is:
      
          make dev
      
      Subsequent runs of `make dev` will ensure the JavaScript and Python
      dependencies are up-to-date but will not rebuild the assets unless they
      are either explicitly cleaned,
      
          make clean dev
      
      or the developer runs the gulp `watch` task independently (recommended).
      
      Similarly, from a fresh checkout, it should be possible to run the test
      suite simply by running:
      
          make test
      
      Note that this commit removes `gulp-cli` and `karma-cli` from the
      package dependencies -- these packages are not intended to be installed
      in a software distribution, although they can both be installed globally
      to assist with easier dispatch of gulp/karma tasks if needed:
      
          npm install -g gulp-cli karma-cli
      73769fe2