gecko-dev/devtools/docs/getting-started
Andrea Marchesini c0950f9d8a Bug 1480544 - Allow Console API to log messages on stdout, r=bgrins
This patch introduces 2 new prefs:
- devtools.console.stdout.chrome: if true, console API writes on stdout when
                                  used by chrome code
- devtools.console.stdout.content: console API write on stdout when used by
                                   content code.
2018-11-15 21:47:58 +01:00
..
architecture-overview.md
build.md Bug 1475474 - Fix broken link to Firefox Build page in devtools-docs;r=sole 2018-07-13 09:02:27 +02:00
development-profiles.md Bug 1480544 - Allow Console API to log messages on stdout, r=bgrins 2018-11-15 21:47:58 +01:00
README.md Bug 1408827 - Where is code link broken for DevTools documentation. r=sole 2017-11-20 23:11:15 -04:00
where-is-the-code.md

Getting started

  1. Learn where the code is and about the architecture of the tools.
  2. Set up your machine to build the tools, then configure a development profile.
  3. You can now experiment by changing things and rebuilding, look at the files and directories overview or you could also find something to work on.

Additional documentation

  • MDN Web Docs (also known as MDN) has a lot of information about XUL elements, HTML, JS, DOM, Web APIs, Gecko-specific APIs, and more.
  • DXR is a source code search engine - search for symbols you want to learn about, eg. nsIDocument. Searchfox is an alternative.

It is a good idea to add smart keyword searches for DXR and MDN, so you can search faster.