mirror of
https://github.com/mozilla/pdf.js.git
synced 2025-04-25 01:28:06 +02:00
Re-factor the PDFScriptingManager
-class for the viewer-components
Currently this class contains a few "special" code-paths for the COMPONENTS build-target, which normally wouldn't be a problem. However, in this particular case that means accessing code that we don't want to include unconditionally in all builds. This is currently implemented using build-time `require`-calls which we nowadays want to avoid, and we should strive to remove all such cases from the code-base. (Generally speaking `import` is the future, and build-tools may not always play well with a mix of both formats.) We can easily improve things here by using sub-classing for the COMPONENTS build-target, and then use the ability to re-name when exporting (to avoid breaking existing code).
This commit is contained in:
parent
337cba736e
commit
86a868189c
4 changed files with 46 additions and 26 deletions
|
@ -33,7 +33,7 @@ import { GenericL10n } from "../../web/genericl10n.js";
|
|||
import { NullL10n } from "../../web/l10n_utils.js";
|
||||
import { PDFHistory } from "../../web/pdf_history.js";
|
||||
import { PDFPageView } from "../../web/pdf_page_view.js";
|
||||
import { PDFScriptingManager } from "../../web/pdf_scripting_manager.js";
|
||||
import { PDFScriptingManager } from "../../web/pdf_scripting_manager.component.js";
|
||||
import { PDFSinglePageViewer } from "../../web/pdf_single_page_viewer.js";
|
||||
import { PDFViewer } from "../../web/pdf_viewer.js";
|
||||
import { StructTreeLayerBuilder } from "../../web/struct_tree_layer_builder.js";
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue