Code structure » History » Revision 1
Revision 1/7
| Next »
jahoti, 07/05/2021 01:39 AM
Code structure¶
The idea of arranging script files based on their execution context might not be the best one. Suggestions are welcome.
- Table of contents
- Code structure
background/
¶
Contains scripts that are to be run exclusively in the context of the background page.
common/
¶
Contains scripts that are to be run in more than one context. E.g. script that gets evaluated in contexts of both settings page and background page is going to reside in this directory.
content/
¶
Contains scripts that execute exclusively in the context of content scripts.
COPYING.txt
¶
Contains copyright information (not the actual license texts, these reside under licenses/
).
html/
¶
Contains javascript, HTML and (in the future) CSS files for settings and popup pages.
icons/
¶
Contains icons graphics used by the extension.
licenses/
¶
Contains full legal texts of licenses used.
manifest.json
¶
Is the manifest file with the most important extension information for the browser. For now this is a version 2 manifest (version 3 is to require a redesign of the entire extension). Temporarily, the same manifest.json
is being used for both browser families.
README.txt
¶
Contains some general information about the extension.
TODOS.org
¶
Lists tasks that need to be done and those that have already been done.
Updated by jahoti about 2 years ago · 1 revisions