Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 62 lines (43 sloc) 2.36 kB
787d09d @janodvarko Append readme file
janodvarko authored
1 Firebug
2 =======
2aa58d9 @janodvarko Update readme file
janodvarko authored
3 *Web Development Evolved* [getfirebug.com](getfirebug.com)
787d09d @janodvarko Append readme file
janodvarko authored
4
fa624c5 @janodvarko Update readme
janodvarko authored
5 [Download](https://addons.mozilla.org/en-US/firefox/addon/firebug/)
787d09d @janodvarko Append readme file
janodvarko authored
6
7
fa624c5 @janodvarko Update readme
janodvarko authored
8 Source Repository Structure
9 ---------------------------
787d09d @janodvarko Append readme file
janodvarko authored
10 See [more](http://getfirebug.com/wiki/index.php/Source) information about Firebug
11 repository structure.
12
13
14 * **extension** Firebug extension directory.
15 * **tests** Firebug automated test files and test harness.
16 * **trace** Firebug tracing console.
17
18
19 Build Firebug XPI
20 -----------------
21 In order to build Firebug *.xpi package run following in your command line
2aa58d9 @janodvarko Update readme file
janodvarko authored
22 (you need [Apache Ant](http://ant.apache.org/))
787d09d @janodvarko Append readme file
janodvarko authored
23
24 $ cd firebug/extension
25 $ ant
26
fa624c5 @janodvarko Update readme
janodvarko authored
27 The *.xpi file should be located within `./release` directory.
787d09d @janodvarko Append readme file
janodvarko authored
28
29
30 Run Firebug From Source
31 -----------------------
2aa58d9 @janodvarko Update readme file
janodvarko authored
32 The *extension* directory directly contains Firebug extension files and so, you can run
33 Firebug directly from it. This is the recommended way how to quickly test your code
34 changes and provide a patch.
787d09d @janodvarko Append readme file
janodvarko authored
35
fa624c5 @janodvarko Update readme
janodvarko authored
36 1. Locate your Firefox [profile folder](http://kb.mozillazine.org/Profile_folder)
37 2. Open `extensions/` folder, create if it doesn't exist.
38 3. Create a new text file and put the full path to your development folder inside.
39 (e.g. `C:\firebug\extension\` or `~/firebug/extension/`). Windows users should retain the OS'
787d09d @janodvarko Append readme file
janodvarko authored
40 slash direction, and everyone should remember to include a closing slash and remove any
41 trailing spaces.
fa624c5 @janodvarko Update readme
janodvarko authored
42 4. Save the file with Firebug ID as it's name `firebug@software.joehewitt.com`
787d09d @janodvarko Append readme file
janodvarko authored
43
44
14ec687 @janodvarko Update readme file
janodvarko authored
45 Hacking on Firebug
46 ------------------
47 See detailed [instructions](http://www.softwareishard.com/blog/firebug/hacking-on-firebug/)
48 about how to provide a patch to Firebug source.
49
50
fa624c5 @janodvarko Update readme
janodvarko authored
51 Further Resources
52 -----------------
53
54 * Home: [http://getfirebug.com/](http://getfirebug.com/)
55 * Blog: [http://blog.getfirebug.com/](http://blog.getfirebug.com/)
56 * Twitter: [http://twitter.com/#!/firebugnews](http://twitter.com/#!/firebugnews)
57 * Discussion Group: [https://groups.google.com/forum/?fromgroups#!forum/firebug](https://groups.google.com/forum/?fromgroups#!forum/firebug)
58 * Wiki: [http://getfirebug.com/wiki](http://getfirebug.com/wiki/index.php/Main_Page)
59 * Report an Issue: [http://code.google.com/p/fbug/issues/list](http://code.google.com/p/fbug/issues/list)
b60e41f @janodvarko Fix link in readme
janodvarko authored
60 * Firebug Extensions: [http://getfirebug.com/wiki/index.php/Firebug_Extensions](http://getfirebug.com/wiki/index.php/Firebug_Extensions)
787d09d @janodvarko Append readme file
janodvarko authored
61
Something went wrong with that request. Please try again.