Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
PDF.js skin and theme reuse guidelines
676 views
Skip to first unread message
Eric Gagnon
Nov 7, 2016, 2:54:19 PM11/7/16
to dev-p...@lists.mozilla.org
Hello,
I would appreciate if it would be possible to find more precise guidance
regarding the note that appear in
https://mozilla.github.io/pdf.js/getting_started/ about the skin of pdf.js
"Viewer :
The viewer is built on the display layer and is the UI for PDF viewer in
Firefox and the other browser extensions within the project. It can be a
good starting point for building your own viewer. However, we do ask if
you plan to embed the viewer in your own site, that it not just be an
unmodified version. Please re-skin it or build upon it."
The way it is formulated make it appear like it is more a courtesy issue
than a licencing one, do I read right?
What would "re-skin" imply? Color change? New icons?
In my case, it goes a bit further. The project I joined has a need for a
"universal viewer" the work that have been done so far reuse PDF.js skin as
skin for OpenSeadDragon.
Seems to be a good match from a fonctionnality standpoint (many compatible
fonctionnality from a UI/fonctionnal standpoint) but it surely strech the
line of reusing pdf.js in another context.
Would it still be considered acceptable derivative work?
I would appreciate if it would be possible to find more precise guidance
regarding the note that appear in
https://mozilla.github.io/pdf.js/getting_started/ about the skin of pdf.js
"Viewer :
The viewer is built on the display layer and is the UI for PDF viewer in
Firefox and the other browser extensions within the project. It can be a
good starting point for building your own viewer. However, we do ask if
you plan to embed the viewer in your own site, that it not just be an
unmodified version. Please re-skin it or build upon it."
The way it is formulated make it appear like it is more a courtesy issue
than a licencing one, do I read right?
What would "re-skin" imply? Color change? New icons?
In my case, it goes a bit further. The project I joined has a need for a
"universal viewer" the work that have been done so far reuse PDF.js skin as
skin for OpenSeadDragon.
Seems to be a good match from a fonctionnality standpoint (many compatible
fonctionnality from a UI/fonctionnal standpoint) but it surely strech the
line of reusing pdf.js in another context.
Would it still be considered acceptable derivative work?
0 new messages