Remove Bower

Author: jrwdunham

.bowerrc

@@ -1,3 +1,4 @@
 {
-    "directory": "app/bower_components"
+    "directory": "app/bower_components",
+    "registry": "https://registry.bower.io"
 }

.gitignore

@@ -4,7 +4,7 @@ test/temp
 .sass-cache
 app/bower_components
 .tmp
-test/bower_components/
+test/bower_components
 *.sw?
 docs
 notes

.travis.yml

@@ -1,50 +1,17 @@
 language: node_js
 
 node_js:
-  - 0.12.10
-  - 4.3.0
-
-# Travis supports running a real browser (Firefox) with a virtual screen. Just update your .travis.yml to set up the virtual screen like this:
-# before_script:
-#   - export DISPLAY=:99.0
-#   - sh -e /etc/init.d/xvfb start
-
-# whitelist
-# branches:
-#  only:
-#    - master
-bundler_args: --retry 3
-
-notifications:
-  email:
-    recipients:
-      - [email protected]
-    on_success: change
-    on_failure: always
-
-# env:
-#   matrix:
-    # see set_up_new_machine.sh
+  - 8.9.1
 
 before_install:
-  # Download and configure deps
-  - export TZ=Canada/Eastern # http://stackoverflow.com/questions/23371542/how-do-i-configure-travis-ci-to-use-the-correct-time-zone-for-a-rails-app
-  # - sudo apt-get install ncftp
+  - export TZ=Canada/Eastern
   - npm install -g grunt-cli
-  - npm install -g bower
 
-script: grunt deploy
+install:
+  - yarn
 
-env:
-  global:
-   - FIELDDB_HOME=$HOME
-   - secure: MFLi2VIIEDtmYXUwHYTdMelUVTiILNi2d66dqp7amyLIjSfsgypnmmtbH6NBnNEmZ9srpgrvJVym9tR+0JDvtmC1F/qhZyrLTF2K8schfe3M6+dHlMJDpiFgt4vmWkxnYTinRUXh5nb/Tvhtx8RydDW4JDeTZNyurfE6e7FqZ70=
-   - secure: FQG2Ix+HjfFe2s7KT8RDkb8vhXugWSVOBw/fcbkfSLRLMd9+13mQ/mQooo0HC+L9u9ZtfqVeqkEn0dJExej7heSkWFkUg2vKfyR3Mceyou5JdzXWUX3BUrbLAfAvkN4S6IGtO8Nxnbu88ghqw20uUHGeiKUDfjc9tuSPFxtqQBQ=
-   - secure: hE2iibDhUs1CwWVPkfvNz1l9chaZLF4dRJy4xJ+wejdvVCTgWgg2qTSllwYjRXZ8zwSEi9v5MVHng9z2+AGikuMl8i7yYzxFrBbzM5qIRqRonXlfNrJXx9ruMGKKBhffNtIwZAp1b7IxQaapQ3BXsoXbOp/z8wp3u0aX7DJa1Ck=
+script: grunt deploy
 
 after_success:
-  # on:
-  #   branch: master
-  #   condition: $TRAVIS_REPO_SLUG = FieldDB/dative
-    - touch "dist/deployed at `date`"
-    - '[ "${TRAVIS_PULL_REQUEST}" = "false" ] && [ "${TRAVIS_REPO_SLUG}" = "FieldDB/dative" ]  && ncftpput -R -v -u $USERNAME -p $PASSWORD $SERVER /beta dist/*'
+  - touch "dist/deployed at `date`"
+  - '[ "${TRAVIS_PULL_REQUEST}" = "false" ] && [ "${TRAVIS_REPO_SLUG}" = "FieldDB/dative" ]  && ncftpput -R -v -u $USERNAME -p $PASSWORD $SERVER /beta dist/*'

Dockerfile

@@ -1,17 +1,15 @@
 FROM node:8
 
-# Install Bower & Grunt
-RUN npm install -g bower grunt-cli && \
+RUN npm install -g grunt-cli && \
     echo '{ "allow_root": true }' > /root/.bowerrc
 
 COPY . /usr/src/dative
 ENV GIT_DIR=/usr/src/dative
 
 WORKDIR /usr/src/dative/
-RUN npm install
-RUN bower install
+RUN yarn
 WORKDIR /usr/src/dative/test/
-RUN bower install
+RUN yarn
 
 WORKDIR /usr/src/dative/
 CMD grunt serve

Gruntfile.coffee

@@ -281,7 +281,6 @@ module.exports = (grunt) ->
             spin: '../../<%= yeoman.app %>/bower_components/spin.js/spin'
             jqueryspin: '../../<%= yeoman.app %>/bower_components/spin.js/jquery.spin'
             perfectscrollbar: '../../<%= yeoman.app %>/bower_components/perfect-scrollbar/src/perfect-scrollbar'
-            fielddb: '../../<%= yeoman.app %>/bower_components/fielddb/fielddb'
             backbonerelational: '../../<%= yeoman.app %>/bower_components/backbone-relational/backbone-relational'
             backbonelocalstorage: '../../<%= yeoman.app %>/bower_components/backbone.localStorage/backbone.localStorage'
 
@@ -478,33 +477,6 @@ module.exports = (grunt) ->
       setContinuousDeploymentVersion:
         cmd: ->
           return 'bash scripts/set_ci_version.sh'
-      symlinkFieldDBIfAvailable:
-        cmd: ->
-          return 'if [ -z ${FIELDDB_HOME} ]; ' +
-          ' then ' +
-          ' echo "Not using the most recent FieldDB, some functions might not work.";' +
-          ' else ' +
-          ' echo "Symlinking FieldDB to your local dev version in $FIELDDB_HOME/FieldDB/fielddb.js";' +
-          ' rm app/bower_components/fielddb/fielddb.js;' +
-          ' ln -s $FIELDDB_HOME/FieldDB/fielddb.js app/bower_components/fielddb/fielddb.js;' +
-          ' fi '
-      updateFieldDB:
-        cmd: ->
-          return 'if [ -z ${FIELDDB_HOME} ]; ' +
-          ' then ' +
-          ' echo "Not using the most recent FieldDB, some functions might not work.";' +
-          ' else ' +
-          ' echo "Updating FieldDB in $FIELDDB_HOME/FieldDB/fielddb.js";' +
-          ' cd $FIELDDB_HOME;' +
-          ' git clone https://github.com/cesine/FieldDB.git;' +
-          ' cd $FIELDDB_HOME/FieldDB;' +
-          ' pwd; '+
-          ' git remote add cesine https://github.com/cesine/FieldDB.git;' +
-          ' git checkout master;' +
-          ' git pull cesine master;' +
-          ' npm install; ' +
-          ' grunt browserify:src; ' +
-          ' fi '
 
     rev:
       dist:
@@ -688,7 +660,7 @@ module.exports = (grunt) ->
 
   grunt.registerTask 'docs', ['clean:docs', 'clean:doctmp', 'copy:docco', 'docco', 'clean:doctmp']
 
-  grunt.registerTask 'deploy', ['exec:updateFieldDB', 'exec:symlinkFieldDBIfAvailable', 'jshint', 'build', 'exec:setContinuousDeploymentVersion']
+  grunt.registerTask 'deploy', ['jshint', 'build', 'exec:setContinuousDeploymentVersion']
 
   grunt.registerTask 'copydist', 'copy:dist'
   grunt.registerTask 'cleandist', 'clean:dist'

README.md

@@ -50,15 +50,14 @@ Then clone the dative repo and move into the clone:
     $ git clone https://github.com/jrwdunham/dative.git
     $ cd dative
 
-Then install the Node dependencies:
+Then install the dependencies:
 
-    $ npm install
+    $ yarn
 
-Then install the Bower dependencies for the app and the tests:
+Then optionally install the test dependencies:
 
-    $ bower install
     $ cd test
-    $ bower install
+    $ yarn
     $ cd ..
 
 

app/help/html/help.html

@@ -83,7 +83,7 @@ <h2 id="about-dative-a-data-name-about-dative-a-">About Dative<a data-name="abou
 linguistic data to be stored and manipulated on web servers by multiple users
 at the same time.</p>
 <p>In order to log in to an OLD or {{FieldDB.FieldDBObject.application.brand}} web
-service, you must know the web service’s URL and you must create a Dative
+service, you must know the web service&#39;s URL and you must create a Dative
 “server” object for that web service in Dative’s
 <a href="#application-settings">application settings</a>.</p>
 <p>Dative is written in CoffeeScript (and HTML and CSS) using the Backbone
@@ -253,7 +253,7 @@ <h3 id="updating-an-existing-resource-a-data-name-update-resource-a-">Updating a
 the values that they had before you began making changes.</p>
 <h3 id="destroying-a-resource-a-data-name-destroy-resource-a-">Destroying a Resource<a data-name="destroy-resource"></a></h3>
 <p>To destroy (i.e., delete) a resource, click on the
-<i class="fa fa-trash fa-fw"></i> button at the top of the resource’s interface.
+<i class="fa fa-trash fa-fw"></i> button at the top of the resource&#39;s interface.
 Doing this will cause a confirm dialog to be displayed. You must click the
 “Ok” button in order to issue the destroy request. You may also click
 “Cancel” (or press Esc) in order to abort the destroy action.</p>
@@ -307,7 +307,7 @@ <h4 id="advanced-search-a-data-name-advanced-search-a-">Advanced Search<a data-n
 </li>
 </ol>
 <p>Searches of arbitrary structural complexity can be created by using the “and”,
-“not”, “or”, or “…” buttons to create more boolean nodes or
+“not”, “or”, or “...” buttons to create more boolean nodes or
 change existing ones. By changing the select menus you can change the field
 that a given search condition is targeting or you can change the type of search
 from, say, a regular expression search (<em>regex</em>) to an exact match search (<em>=</em>).</p>
@@ -333,7 +333,7 @@ <h4 id="advanced-search-a-data-name-advanced-search-a-">Advanced Search<a data-n
 <h4 id="smart-search-a-data-name-smart-search-a-">Smart Search<a data-name="smart-search"></a></h4>
 <p>The smart search interface has a single search input. Dative tries to guess
 what you want to search for, given your input, and reports back on the type of
-searches it thinks you’re after and how many results they would return. The
+searches it thinks you&#39;re after and how many results they would return. The
 screenshot below shows an example of a smart search for “dog” and the
 suggestions that Dative has returned.</p>
 <p><img src="/images/help/smart-search-500.png" alt="screenshot of an advanced search"></p>
@@ -370,7 +370,7 @@ <h3 id="exporting-resources-a-data-name-export-resources-a-">Exporting Resources
 OpenOffice or Google Sheets.</p>
 <p>JSON files can be parsed by most modern programming languages.</p>
 <h2 id="application-settings-a-data-name-application-settings-a-">Application Settings<a data-name="application-settings"></a></h2>
-<p>Dative’s application settings allows you to:</p>
+<p>Dative&#39;s application settings allows you to:</p>
 <ol>
 <li><p><i class="fa fa-fw fa-server"></i>
 <a href="#configuring-servers">Configure servers</a>, i.e., connections to
@@ -396,24 +396,24 @@ <h3 id="configuring-servers-a-data-name-configuring-servers-a-">Configuring Serv
 (“{{FieldDB.FieldDBObject.application.brand}}” or “OLD”), and
 potentially a server code.</p>
 <p>To change the active server, simply select one of the existing servers from
-the <em>Active Server</em> select menu, or click on that server’s
+the <em>Active Server</em> select menu, or click on that server&#39;s
 <i class="fa fa-fw fa-toggle-off"></i> button. Note that you cannot change the
 active server while you are logged in to a server.</p>
 <p>To create a new server, click on the <i class="fa fa-fw fa-plus"></i> button to
 reveal the interface for creating a new one. In the new server form, enter a
-name, the server’s URL, its type, and (if it’s a FieldDB-type server) its
+name, the server&#39;s URL, its type, and (if it’s a FieldDB-type server) its
 server code. If you do not know which server code value to choose, then choose
 “production.” If you do not know which values to enter to create a new
 server, please contact your {{FieldDB.FieldDBObject.application.brand}} or OLD
 server administrator. Note that there is no “Save” button for creating
 servers: Dative saves all of your application settings changes automatically to
-your browser’s local storage.</p>
+your browser&#39;s local storage.</p>
 <p>To delete a server configuration, click its <i class="fa fa-fw fa-trash"></i>
 button. A confirm dialog will verify that you really want to proceed with the
 deletion.</p>
 <p>Note that you cannot delete or modify a server while it is the designated
 active one.</p>
-<h3 id="changing-dative-s-appearance-a-data-name-changing-appearance-a-">Changing Dative’s Appearance<a data-name="changing-appearance"></a></h3>
+<h3 id="changing-dative-s-appearance-a-data-name-changing-appearance-a-">Changing Dative&#39;s Appearance<a data-name="changing-appearance"></a></h3>
 <p>To change how Dative looks, simply click on one of the example form resources
 in the application settings appearance sub-section. The form examples
 illustrate how Dative will look using each of the possible visual themes.</p>
@@ -422,16 +422,16 @@ <h3 id="changing-dative-s-appearance-a-data-name-changing-appearance-a-">Changin
 Two themes that are known to work well with Dative are “Pepper Grinder” and
 “Cupertino”.</p>
 <h3 id="configuring-server-settings-a-data-name-configuring-server-settings-a-">Configuring Server Settings<a data-name="configuring-server-settings"></a></h3>
-<p>At present, Dative only allows for the configuration of an OLD web server’s
+<p>At present, Dative only allows for the configuration of an OLD web server&#39;s
 application settings. Support for viewing and altering the settings of a
 {{FieldDB.FieldDBObject.application.brand}} web service will be available soon.</p>
 <p>The interface for configuring the settings of a server (i.e., a particular
 server-side web service) works very much like the standard
 <a href="#viewing-single-resource">resource interface described above</a>. Note that you
-must be an administrator in order to have permission to modify a web service’s
+must be an administrator in order to have permission to modify a web service&#39;s
 application settings.</p>
 <h4 id="configuring-old-server-settings-a-data-name-configuring-old-server-settings-a-">Configuring OLD Server Settings<a data-name="configuring-old-server-settings"></a></h4>
-<p>An OLD web service’s application-wide settings are used to identify the
+<p>An OLD web service&#39;s application-wide settings are used to identify the
 language being documented (the “object language”), the language used to
 document and analyze (the “metalanguage”), validation settings for various
 form transcription fields, and the set of users designated as “unrestricted”.</p>
@@ -442,7 +442,7 @@ <h5 id="object-language">Object Language</h5>
 latter must be an
 <a href="http://www-01.sil.org/iso639-3/codes.asp">ISO 639-3 three-letter language identifier code</a>.
 Luckily, the OLD and Dative contain a copy of the ISO 639-3 language database so
-that the application settings interface’s input fields will help you to find the
+that the application settings interface&#39;s input fields will help you to find the
 appropriate code for the language that you are documenting/analyzing. If the
 language categorization of ISO 639-3 standard is not suitable or appropriate for
 your language of documentation, then leave the object language id field blank.</p>
@@ -462,7 +462,7 @@ <h5 id="metalanguage">Metalanguage</h5>
 your Dative/OLD data.</p>
 <h5 id="form-field-validation">Form Field Validation</h5>
 <p><strong>Important Notice:</strong> form field validation is not yet implemented in Dative.
-That is, while you can specify inventories and validation settings via Dative’s
+That is, while you can specify inventories and validation settings via Dative&#39;s
 interface, they will have no effect at present.</p>
 <p>The following form fields can be configured to have validation:</p>
 <ul>
@@ -513,7 +513,7 @@ <h3 id="importing-forms-a-data-name-importing-forms-a-">Importing Forms<a data-n
 in these columns will not be imported.</p>
 <p>You can alter the values in the cells of the table by double-clicking them.</p>
 <p>Some form attributes are not simply strings but are resources in their own
-right. A form’s “source” value and its “tags” value are examples of
+right. A form&#39;s “source” value and its “tags” value are examples of
 this. If Dative cannot identify an existing resource (or existing resources)
 that match(es) the string value in your CSV file, it will display a warning and
 will help you to create a corresponding resource (or resources), if you want
@@ -554,19 +554,19 @@ <h3 id="importing-forms-a-data-name-importing-forms-a-">Importing Forms<a data-n
 <h2 id="files-a-data-name-files-a-">Files<a data-name="files"></a></h2>
 <p>In Dative, a file resource represents a digital file, i.e., an audio or video
 recording, an image, or a textual file, such as a PDF.</p>
-<p>…</p>
+<p>...</p>
 <h2 id="texts-a-k-a-collections-a-data-name-texts-a-">Texts (a.k.a. Collections)<a data-name="texts"></a></h2>
 <p>A text resource reresents a text in the object language. A text may be a story
 or narrative or it may be a conversation, or even a record of an elicitation
 session. In Dative, a text is simply a sequence of forms and is specified as a
 sequence of references to forms.</p>
-<p>…</p>
+<p>...</p>
 <h2 id="corpora-a-data-name-corpora-a-">Corpora<a data-name="corpora"></a></h2>
 <p>A corpus is, like a text, also a sequence of forms. A corpus may be specified
 manually, i.e., by listing form references in the same way as a text is
 specified, or it may be specified by referencing a saved search.</p>
 <p>Corpora may be used in the construction of OLD morphologies and language models.</p>
-<p>…</p>
+<p>...</p>
 <h2 id="parsers-a-data-name-parsers-a-">Parsers<a data-name="parsers"></a></h2>
 <p>Dative provides an interface to the morphological parser creation tools of OLD
 web services. These tools allow users to construct morphological parsers using
@@ -578,7 +578,7 @@ <h2 id="parsers-a-data-name-parsers-a-">Parsers<a data-name="parsers"></a></h2>
 <li>morphologies</li>
 <li>phonologies</li>
 </ul>
-<p>…</p>
+<p>...</p>
 <h2 id="other-resources-a-data-name-other-resources-a-">Other Resources<a data-name="other-resources"></a></h2>
 <p>When logged in to an OLD web service, Dative provides standard resource-style
 interfaces to the following additional resources:</p>
@@ -702,7 +702,7 @@ <h2 id="frequently-asked-questions-a-data-name-frequently-asked-questions-a-">Fr
 <li><p>How can I request new features or report bugs?</p>
 <ul>
 <li>At present, the best way to do this is by creating an issue on
-<a href="https://github.com/jrwdunham/dative/issues">Dative’s GitHub issues page</a>.</li>
+<a href="https://github.com/jrwdunham/dative/issues">Dative&#39;s GitHub issues page</a>.</li>
 </ul>
 </li>
 <li><p>Can I import my existing data into an OLD or
@@ -728,7 +728,7 @@ <h2 id="frequently-asked-questions-a-data-name-frequently-asked-questions-a-">Fr
 </li>
 <li><p>Are there any video tutorials on how to use Dative?</p>
 <ul>
-<li>Not yet. They’re a comin’.</li>
+<li>Not yet. They&#39;re a comin&#39;.</li>
 </ul>
 </li>
 </ol>