You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@rkwright wrote document about the EOL of the Chrome app here. As part of that it was proposed that the naming of the new repos be as follows:
New Repos
We will need four new repos corresponding to readium-js, readium-js-viewer, shared-js and cfi-js. One approach would be to pattern them of the existing names and the "r2" prefix used elsewhere. Thus:
R1 Name
Readium-Web Name
readium-js-viewer
r2-js-viewer
readium-js
r2-js
readium-shared-js
r2-shared-js
readium-cfi-js
r2-cfi-js
Each of these repos will be a clone of the existing repo, then modified by
removing all code, build-scripts, resources, etc. related to the Chrome app
adding new interfaces and APIs as appropriate
modifying and/or adding tests in order to enable functional testing (e.g. continuous build processes such as on Travis)
The text was updated successfully, but these errors were encountered:
@rkwright wrote document about the EOL of the Chrome app here. As part of that it was proposed that the naming of the new repos be as follows:
New Repos
We will need four new repos corresponding to readium-js, readium-js-viewer, shared-js and cfi-js. One approach would be to pattern them of the existing names and the "r2" prefix used elsewhere. Thus:
Each of these repos will be a clone of the existing repo, then modified by
The text was updated successfully, but these errors were encountered: