9
edits
No edit summary |
|||
| Line 8: | Line 8: | ||
newgroup thread to start a constructive discussion. | newgroup thread to start a constructive discussion. | ||
== | == List of claims == | ||
Feel free to add items to the | Feel free to add items to the list below : | ||
=== Few error messages === | === Few error messages === | ||
*<b>Description</b> | |||
When creating a package, firefox will fail silently if their's a<br> | |||
When creating a package, firefox will fail silently if their's a | |||
syntax error in one of the package description files. | syntax error in one of the package description files. | ||
*<b>Impact</b> | |||
Firefox, Packaging | Firefox, Packaging | ||
*<b>Solutions, workarounds</b> | |||
Is there an option to make firefox more verbose ? | Is there an option to make firefox more verbose ? | ||
*<b>Improvements</b> | |||
Make the extension module more defensive. | Make the extension module more defensive. | ||
Add meaningfull messages. | Add meaningfull messages. | ||
| Line 34: | Line 30: | ||
=== No simple option === | === No simple option === | ||
*<b>Description</b> | |||
Currently, the requirements for setting up the project are very elaborate. | Currently, the requirements for setting up the project are very elaborate. | ||
There are too many boiler-plate items on the check list that have to be successfully completed. | There are too many boiler-plate items on the check list that have to be successfully completed. | ||
All of which can be assumed (see Ruby on Rails philosophy) but are potential blockers for new developers who silently pass up XUL because it looked like a lot of unnecessary pain. | All of which can be assumed (see Ruby on Rails philosophy) but are potential blockers for new developers who silently pass up XUL because it looked like a lot of unnecessary pain. | ||
*<b>Impact</b> | |||
XUL Runner apps. Mozilla/Firefox extensions. | XUL Runner apps. Mozilla/Firefox extensions. | ||
*<b>Solutions, workarounds</b> | |||
None | None | ||
*<b>Improvements</b> | |||
Why can't it be as simple as passing a jar file to xulrunner/firefox bin | Why can't it be as simple as passing a jar file to xulrunner/firefox bin | ||
on the command-line - the same way you pass a jar file to java bin. | on the command-line - the same way you pass a jar file to java bin. | ||
| Line 55: | Line 47: | ||
=== Privileges / Security barrier === | === Privileges / Security barrier === | ||
*<b>Description</b> | |||
When one's developping a XUL app, he will soon face privilege issues. | When one's developping a XUL app, he will soon face privilege issues. | ||
actually, many access to deep Mozilla functionnalities (as interacting with XPCOM) | actually, many access to deep Mozilla functionnalities (as interacting with XPCOM) | ||
| Line 67: | Line 58: | ||
Moreover, locally installed applications (extensions) have a special status, | Moreover, locally installed applications (extensions) have a special status, | ||
will full privileges that no remote application could ever get. | will full privileges that no remote application could ever get. | ||
Mozilla already embeds a signing facilities [http://www.mozilla.org/projects/security/components/signed-scripts.html | Mozilla already embeds a signing facilities [http://www.mozilla.org/projects/security/components/signed-scripts.html signing facilities] | ||
Signed scripts or signed applications should be able to execute with full privileges, | Signed scripts or signed applications should be able to execute with full privileges, | ||
without prior installation. | without prior installation. | ||
| Line 74: | Line 65: | ||
as we already have for XUL extenstions. | as we already have for XUL extenstions. | ||
*<b>Impact</b> | |||
Remote applications. | |||
*<b>Links</b> | |||
This point is already being discussed [[XUL:Remove_Privilege| here]] | |||
=== | === The developper mode === | ||
TODO (javascript on sidebar, setsome flags, no xul cache, ...) | |||
edits