Mozilla2:Improving Development Environment: Difference between revisions

The purpose of this page is to bring together the claims from developpers.

The final aim is to ease the work of developpers, and to make mozilla/firefox a great development environment, out of the box.

In this area, you may either point other developpers to a solution  

== Matrix of claims ==

Feel free to add items to the table below :

<table border="1" cellspacing="0" cellpadding="4" >

<tr style="background-color : gray">

      <th>Description</th>

    <td>When creating a package, firefox will fail silently if their's a syntax error in one of the package description files

    <td>Firefox, Packaging</td>

    <td>Is there an option to make firefox more verbose ?</td>

    <td>Make the extension module more defensive, add clear messages

    <td>No simple option</td>

    <td>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. 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.</td>

    <td>XUL Runner apps. Mozilla/Firefox extensions.</td>

    <td>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?</td>

    <td></td>