2016-09-07 20:30:26 +09:00
|
|
|
/* Copyright 2017 Mozilla Foundation
|
|
|
|
*
|
|
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
* you may not use this file except in compliance with the License.
|
|
|
|
* You may obtain a copy of the License at
|
|
|
|
*
|
|
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
*
|
|
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
* See the License for the specific language governing permissions and
|
|
|
|
* limitations under the License.
|
|
|
|
*/
|
|
|
|
|
2020-01-02 20:00:16 +09:00
|
|
|
import { GrabToPan } from "./grab_to_pan.js";
|
2020-12-29 01:03:27 +09:00
|
|
|
import { PresentationModeState } from "./ui_utils.js";
|
2016-09-07 20:30:26 +09:00
|
|
|
|
|
|
|
const CursorTool = {
|
|
|
|
SELECT: 0, // The default value.
|
|
|
|
HAND: 1,
|
|
|
|
ZOOM: 2,
|
|
|
|
};
|
|
|
|
|
|
|
|
/**
|
|
|
|
* @typedef {Object} PDFCursorToolsOptions
|
|
|
|
* @property {HTMLDivElement} container - The document container.
|
|
|
|
* @property {EventBus} eventBus - The application event bus.
|
2019-10-12 23:30:32 +09:00
|
|
|
* @property {number} [cursorToolOnLoad] - The cursor tool that will be enabled
|
|
|
|
* on load; the constants from {CursorTool} should be used. The default value
|
|
|
|
* is `CursorTool.SELECT`.
|
2016-09-07 20:30:26 +09:00
|
|
|
*/
|
|
|
|
|
|
|
|
class PDFCursorTools {
|
|
|
|
/**
|
|
|
|
* @param {PDFCursorToolsOptions} options
|
|
|
|
*/
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
constructor({ container, eventBus, cursorToolOnLoad = CursorTool.SELECT }) {
|
2016-09-07 20:30:26 +09:00
|
|
|
this.container = container;
|
|
|
|
this.eventBus = eventBus;
|
|
|
|
|
|
|
|
this.active = CursorTool.SELECT;
|
|
|
|
this.activeBeforePresentationMode = null;
|
|
|
|
|
|
|
|
this.handTool = new GrabToPan({
|
|
|
|
element: this.container,
|
|
|
|
});
|
|
|
|
|
|
|
|
this._addEventListeners();
|
|
|
|
|
2018-07-08 17:55:56 +09:00
|
|
|
// Defer the initial `switchTool` call, to give other viewer components
|
|
|
|
// time to initialize *and* register 'cursortoolchanged' event listeners.
|
2018-03-20 07:24:56 +09:00
|
|
|
Promise.resolve().then(() => {
|
|
|
|
this.switchTool(cursorToolOnLoad);
|
|
|
|
});
|
2016-09-07 20:30:26 +09:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2019-10-13 00:02:54 +09:00
|
|
|
* @type {number} One of the values in {CursorTool}.
|
2016-09-07 20:30:26 +09:00
|
|
|
*/
|
|
|
|
get activeTool() {
|
|
|
|
return this.active;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* NOTE: This method is ignored while Presentation Mode is active.
|
|
|
|
* @param {number} tool - The cursor mode that should be switched to,
|
|
|
|
* must be one of the values in {CursorTool}.
|
|
|
|
*/
|
|
|
|
switchTool(tool) {
|
|
|
|
if (this.activeBeforePresentationMode !== null) {
|
|
|
|
return; // Cursor tools cannot be used in Presentation Mode.
|
|
|
|
}
|
|
|
|
if (tool === this.active) {
|
|
|
|
return; // The requested tool is already active.
|
|
|
|
}
|
|
|
|
|
2019-12-27 08:22:32 +09:00
|
|
|
const disableActiveTool = () => {
|
2016-09-07 20:30:26 +09:00
|
|
|
switch (this.active) {
|
|
|
|
case CursorTool.SELECT:
|
|
|
|
break;
|
|
|
|
case CursorTool.HAND:
|
|
|
|
this.handTool.deactivate();
|
|
|
|
break;
|
|
|
|
case CursorTool.ZOOM:
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
/* falls through */
|
2016-09-07 20:30:26 +09:00
|
|
|
}
|
|
|
|
};
|
|
|
|
|
2019-12-26 04:03:46 +09:00
|
|
|
// Enable the new cursor tool.
|
|
|
|
switch (tool) {
|
2016-09-07 20:30:26 +09:00
|
|
|
case CursorTool.SELECT:
|
|
|
|
disableActiveTool();
|
|
|
|
break;
|
|
|
|
case CursorTool.HAND:
|
|
|
|
disableActiveTool();
|
|
|
|
this.handTool.activate();
|
|
|
|
break;
|
|
|
|
case CursorTool.ZOOM:
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
/* falls through */
|
2016-09-07 20:30:26 +09:00
|
|
|
default:
|
|
|
|
console.error(`switchTool: "${tool}" is an unsupported value.`);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
// Update the active tool *after* it has been validated above,
|
|
|
|
// in order to prevent setting it to an invalid state.
|
|
|
|
this.active = tool;
|
|
|
|
|
|
|
|
this._dispatchEvent();
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* @private
|
|
|
|
*/
|
|
|
|
_dispatchEvent() {
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
this.eventBus.dispatch("cursortoolchanged", {
|
2016-09-07 20:30:26 +09:00
|
|
|
source: this,
|
|
|
|
tool: this.active,
|
|
|
|
});
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* @private
|
|
|
|
*/
|
|
|
|
_addEventListeners() {
|
Re-factor the `EventBus` to allow servicing of "external" event listeners *after* the viewer components have updated
Since the goal has always been, essentially since the `EventBus` abstraction was added, to remove all dispatching of DOM events[1] from the viewer components this patch tries to address one thing that came up when updating the examples:
The DOM events are always dispatched last, and it's thus guaranteed that all internal event listeners have been invoked first.
However, there's no such guarantees with the general `EventBus` functionality and the order in which event listeners are invoked is *not* specified. With the promotion of the `EventBus` in the examples, over DOM events, it seems like a good idea to at least *try* to keep this ordering invariant[2] intact.
Obviously this won't prevent anyone from manually calling the new *internal* viewer component methods on the `EventBus`, but hopefully that won't be too common since any existing third-party code would obviously use the `on`/`off` methods and that all of the examples shows the *correct* usage (which should be similarily documented on the "Third party viewer usage" Wiki-page).
---
[1] Looking at the various Firefox-tests, I'm not sure that it'll be possible to (easily) re-write all of them to not rely on DOM events (since getting access to `PDFViewerApplication` might be generally difficult/messy depending on scopes).
In any case, even if technically feasible, it would most likely add *a lot* of complication that may not be desireable in the various Firefox-tests. All-in-all, I'd be fine with keeping the DOM events only for the `MOZCENTRAL` target and gated on `Cu.isInAutomation` (or similar) rather than a preference.
[2] I wouldn't expect any *real* bugs in a custom implementation, simply based on event ordering, but it nonetheless seem like a good idea if any "external" events are still handled last.
2020-02-27 07:33:27 +09:00
|
|
|
this.eventBus._on("switchcursortool", evt => {
|
2016-09-07 20:30:26 +09:00
|
|
|
this.switchTool(evt.tool);
|
|
|
|
});
|
|
|
|
|
Re-factor the `EventBus` to allow servicing of "external" event listeners *after* the viewer components have updated
Since the goal has always been, essentially since the `EventBus` abstraction was added, to remove all dispatching of DOM events[1] from the viewer components this patch tries to address one thing that came up when updating the examples:
The DOM events are always dispatched last, and it's thus guaranteed that all internal event listeners have been invoked first.
However, there's no such guarantees with the general `EventBus` functionality and the order in which event listeners are invoked is *not* specified. With the promotion of the `EventBus` in the examples, over DOM events, it seems like a good idea to at least *try* to keep this ordering invariant[2] intact.
Obviously this won't prevent anyone from manually calling the new *internal* viewer component methods on the `EventBus`, but hopefully that won't be too common since any existing third-party code would obviously use the `on`/`off` methods and that all of the examples shows the *correct* usage (which should be similarily documented on the "Third party viewer usage" Wiki-page).
---
[1] Looking at the various Firefox-tests, I'm not sure that it'll be possible to (easily) re-write all of them to not rely on DOM events (since getting access to `PDFViewerApplication` might be generally difficult/messy depending on scopes).
In any case, even if technically feasible, it would most likely add *a lot* of complication that may not be desireable in the various Firefox-tests. All-in-all, I'd be fine with keeping the DOM events only for the `MOZCENTRAL` target and gated on `Cu.isInAutomation` (or similar) rather than a preference.
[2] I wouldn't expect any *real* bugs in a custom implementation, simply based on event ordering, but it nonetheless seem like a good idea if any "external" events are still handled last.
2020-02-27 07:33:27 +09:00
|
|
|
this.eventBus._on("presentationmodechanged", evt => {
|
2020-12-29 01:03:27 +09:00
|
|
|
switch (evt.state) {
|
|
|
|
case PresentationModeState.CHANGING:
|
|
|
|
break;
|
|
|
|
case PresentationModeState.FULLSCREEN: {
|
|
|
|
const previouslyActive = this.active;
|
2016-09-07 20:30:26 +09:00
|
|
|
|
2020-12-29 01:03:27 +09:00
|
|
|
this.switchTool(CursorTool.SELECT);
|
|
|
|
this.activeBeforePresentationMode = previouslyActive;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
case PresentationModeState.NORMAL: {
|
|
|
|
const previouslyActive = this.activeBeforePresentationMode;
|
2016-09-07 20:30:26 +09:00
|
|
|
|
2020-12-29 01:03:27 +09:00
|
|
|
this.activeBeforePresentationMode = null;
|
|
|
|
this.switchTool(previouslyActive);
|
|
|
|
break;
|
|
|
|
}
|
2016-09-07 20:30:26 +09:00
|
|
|
}
|
|
|
|
});
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
Enable auto-formatting of the entire code-base using Prettier (issue 11444)
Note that Prettier, purposely, has only limited [configuration options](https://prettier.io/docs/en/options.html). The configuration file is based on [the one in `mozilla central`](https://searchfox.org/mozilla-central/source/.prettierrc) with just a few additions (to avoid future breakage if the defaults ever changes).
Prettier is being used for a couple of reasons:
- To be consistent with `mozilla-central`, where Prettier is already in use across the tree.
- To ensure a *consistent* coding style everywhere, which is automatically enforced during linting (since Prettier is used as an ESLint plugin). This thus ends "all" formatting disussions once and for all, removing the need for review comments on most stylistic matters.
Many ESLint options are now redundant, and I've tried my best to remove all the now unnecessary options (but I may have missed some).
Note also that since Prettier considers the `printWidth` option as a guide, rather than a hard rule, this patch resorts to a small hack in the ESLint config to ensure that *comments* won't become too long.
*Please note:* This patch is generated automatically, by appending the `--fix` argument to the ESLint call used in the `gulp lint` task. It will thus require some additional clean-up, which will be done in a *separate* commit.
(On a more personal note, I'll readily admit that some of the changes Prettier makes are *extremely* ugly. However, in the name of consistency we'll probably have to live with that.)
2019-12-25 23:59:37 +09:00
|
|
|
export { CursorTool, PDFCursorTools };
|