... | ... | @@ -18,9 +18,12 @@ |
|
|
|
|
|
![scheme](https://gitlab.pagedmedia.org/tools/pagedjs/uploads/e3c8acdd3b82e6c368f115466fd9c3e6/20180509_schema-tool.png)
|
|
|
|
|
|
**CORE** will handle the required files and functions for the paged.js to work : chunker + polisher;
|
|
|
**INFERFACE** will provide tools to preview the output on screen (the list of features is yet to define, but the basics would be: show/hide margin-boxes, zoom in/out, go to page, etc.) The goal is to provide as much tools as you'd get in a pdf reader;
|
|
|
**PLUG-IN** will be set of the file needed per css features supported by the paged media team.
|
|
|
> **CORE** will handle the required files and functions for the paged.js to work : chunker + polisher;
|
|
|
|
|
|
> **INFERFACE** will provide tools to preview the output on screen (the list of features is yet to define, but the basics would be: show/hide margin-boxes, zoom in/out, go to page, etc.) The goal is to provide as much tools as you'd get in a pdf reader;
|
|
|
|
|
|
> **PLUG-IN** will be set of the file needed per css features supported by the paged media team.
|
|
|
|
|
|
|
|
|
- From this scheme: a configurable workflow should be able to let the user add new javascript scripts plug-in (hooks), in the order he decides. So, for instance, you could use a hyphenization library, a dropcap one, and some javascript to render visually random titles and choose exactly when each will be used. The flow of even should be configurable.
|
|
|
|
... | ... | |