== Introduction ==
Under ConstructionFUEL (Firefox User Extension Library) is a JavaScript Library designed to help developers build extensions using terminology and interfaces that are familiar to them. It will be usable in Firefox 1.5-3.0.FUEL is about making it easier for extension developers to be productive, by minimizing some of the XPCOM formality and adding some "modern" JavaScript ideas. We want to start with areas that will provide the most benefit.[http://wiki.mozilla.org/FUEL source]
== Project Description The People ==
Description should be no longer than a paragraph. Include links to any relevant on-line resources. For example, http://google.com or * [[httpUser://developerSamer.mozilla.org MDCZiadeh|Samer Ziadeh]].
== Project LeaderTODO ==* At the moment FUEL is manually added to the build (ssee below). It will be much easier if the build script did it for us :) ==
Name(== Project Details ==At the moment FUEL only works on Firefox3. This project is dedicated in back porting FUEL to make it work with Firefox2 == fuelApplication.js =='''fuelApplication.js''' is located in '''mozilla/browser/fuel/src''' and will be the main file that will undergo the changes.You can get the latest update of it [http://www.samerziadeh.com/mozilla/fuelApplication.js here]. It's) just a plain text file, it doesn't have the fancy change revision. Below are the list of primary people working on the projectfunctions I tested with and what did and didn't work. If you want <b><font style="font-size:120%">Working:</font></b>* Console<b><font style="font-size:120%">Not Working:</font></b>* Bookmarks == Build Instructions ==We need to join create a project as leader, discuss with other leaders firstdirectory to throw the mozilla source in.<pre>mkdir mozilla-1.8-branchcd mozilla-1.8-branch</pre> This will fetch the ''client.mk'' file from mozilla.''client. Include links mk'' contains info on how to personal pages within wikiconfigure the build tree to configure any productthe ''-r MOZILLA_1_8_BRANCH'' specifies to the server that we want the ''client.mk'' file from the 1.8 branch<pre>cvs -d :pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -r MOZILLA_1_8_BRANCH mozilla/client.mk</pre>
== Project Contributor(s) ==
Name(s) of people casually working on Now we need to create the project, or who have contributed significant help''.mozconfig'' file. Include links It contains parameters for ''client.mk'' on how to personal pages within wikicheckout and build.The last ''ac_add_options'' line is not needed for non Mac machines.<pre>cd mozillacat > .mozconfig << MOZCONFIG# Options for client.mk.mk_add_options MOZ_CO_PROJECT=browsermk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdirmk_add_options MOZ_MAKE_FLAGS="-s -j4"
NOTE: only Project Leader# Options for 'configure' (ssame as command-line options) should add names here. You '''can’t''' add your own name to the Contributor listac_add_options --enable-application=browserac_add_options --enable-debugac_add_options --enable-testsac_add_options --with-macos-sdk=/Developer/SDKs/MacOSX10.4u.sdkMOZCONFIG</pre>
After creating the MozConfig file we can begin downloading the source. <small>(around 220mb)</small><pre>make -f client.mk checkout</pre> Now we can start building firefox.<pre>make -f client.mk build</pre>When finished the firefox executable is found in the following directories* xp/*nix: mozilla/dist/bin/firefox* mac: mozilla/dist/bin/Something.app/Contents/MacOs/firefox To download FUEL navigate to ''../mozilla''<pre>cd ..cvs -d :pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co mozilla/browser/fuel</pre> Now that we have acquired the fuel source we need to modify the ''browser/Makefile.in'' to let the build know about the addition<pre>cd mozilla/browservi Makefile.in</pre>* Go to the line starting with DIRS* Append fuel to the end of it<pre>DIRS == Project Details ==base components locales extensions themes app fuel</pre>
Provides more depth than The build script doesn't generate the Project Description. This fuel part automatically, which is why fuel is fetched after the place for technical discussions, project specs, or other detailsbuild is done. If this gets very longThe following steps will force the generation of the makefiles manually, you might consider breaking this part into multiple pages and linking to themthen rebuild fuel and app<pre>cd ../objdir../build/autoconf/make-makefiles browser/fuelmake -C browser/fuelmake -C browser/app</pre>
== Project News ==and there you have it, FUEL is now built into ff2
This is where your regular updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc.== Links ==
Put detailed technical information into the Project Details page (i* [http://samermozilla.eblogspot., update it as you go), and save this section for news about participation in the projectcom/ Samer's Blog]* [http://quality.mozilla.org/en/node/452 How To Build a Mozilla Tree]* [http://wiki.mozilla.org/FUEL FUEL]* [http://developer.mozilla.org/en/docs/FUEL FUEL docs]* [https://bugzilla.mozilla.org/show_bug.cgi?id=390335 bug #390335]* [http://mxr.mozilla.org/seamonkey/find?string=fuel%2Ftest%2Fbrowser_&tree=seamonkey FUEL JS Test Files]
