874
edits
Labs/Jetpack/JEP/31: Difference between revisions
Jump to navigation
Jump to search
→Undocumented Features: added note about data dirs
(→Packages: added 'packages') |
(→Undocumented Features: added note about data dirs) |
||
| Line 204: | Line 204: | ||
* Modules in cfx-built packages actually have another global injected into them called <tt>packaging</tt>, which gives them access to package metadata and allows them to create sandboxed module loaders whose lifetime isn't tied to the lifetime of the containing XULRunner application. | * Modules in cfx-built packages actually have another global injected into them called <tt>packaging</tt>, which gives them access to package metadata and allows them to create sandboxed module loaders whose lifetime isn't tied to the lifetime of the containing XULRunner application. | ||
* Packages can also have a <tt>data</tt> top-level directory that contains arbitrary static content such as HTML, CSS, images, and so forth. This can be accessed via <tt>packaging.getURLForData()</tt>. | |||
* It's possible to use the <tt>--templatedir</tt> option to <tt>cfx</tt> to use a cfx configuration from an existing extension. | * It's possible to use the <tt>--templatedir</tt> option to <tt>cfx</tt> to use a cfx configuration from an existing extension. | ||