== Project Name Introduction ==FUEL (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]
Sample Project -- This is a template only!== The People ==
== Project Description ==* [[User:Samer.Ziadeh|Samer Ziadeh]]
Description should be no longer than a paragraph. Include links == TODO ==* At the moment FUEL is manually added to any relevant on-line resourcesthe build (see below). For example, http://google.com or [httpIt will be much easier if the build script did it for us ://developer.mozilla.org MDC].)
== Project Leader(s) Details ==At the moment FUEL only works on Firefox3. This project is dedicated in back porting FUEL to make it work with Firefox2
Name(s) == 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 primary people working on the projectit [http://www.samerziadeh.com/mozilla/fuelApplication.js here]. If you want to join It's just a project as leaderplain text file, discuss with other leaders firstit doesn't have the fancy change revision. Include links to personal pages within wiki
== Project Contributor(s) ==Below are the list of the functions I tested with and what did and didn't work.
Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki<b><font style="font-size:120%">Working:</font></b>* Console<b><font style="font-size:120%">Not Working:</font></b>* Bookmarks
NOTE: only Project Leader(s) should add names here. You '''can’t''' add your own name == Build Instructions ==We need to create a directory to throw the Contributor listmozilla source in.<pre>mkdir mozilla-1.8-branchcd mozilla-1.8-branch</pre>
This will fetch the ''client.mk'' file from mozilla.''client.mk'' contains info on how to configure 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> Now we need to create the ''.mozconfig'' file.It contains parameters for ''client.mk'' on how to checkout 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= Project Details @TOPSRCDIR@/objdirmk_add_options MOZ_MAKE_FLAGS="-s -j4" # Options for 'configure' (same as command-line options).ac_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 = 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]
