|
|
| (7 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| | {{JSDT-Debug}} | | {{JSDT-Debug}} |
| − |
| |
| − | {{warning|Experimental Project|The JSDT Crossfire project is in the experimental phase and is not part of any official release. To test the support you must build the bundle from source and use the latest source code for [http://code.google.com/p/fbug/source/checkout Firebug / Crossfire]}}
| |
| | | | |
| | == Overview == | | == Overview == |
| − | Support for remote [http://getfirebug.com/wiki/index.php/Main_Page Firebug] using the [http://getfirebug.com/wiki/index.php/Crossfire_Protocol_Reference Crossfire protocol] is available in the JSDT development bundles and is provided to allow remote debugging of JavaScript using [http://getfirebug.com/wiki/index.php/Main_Page Firebug] via [http://getfirebug.com/wiki/index.php/Crossfire Crossfire]. | + | Support for remote [https://github.com/firebug Firebug] using the [https://github.com/mrennie/crossfire/wiki/Crossfire%20Protocol%20Reference Crossfire protocol] is available in the JSDT development bundles and is provided to allow remote debugging of JavaScript using [https://github.com/firebug Firebug] via [https://github.com/mrennie/crossfire Crossfire]. |
| | | | |
| | The bundles provided by JSDT debug for the Firebug / Crossfire support include: | | The bundles provided by JSDT debug for the Firebug / Crossfire support include: |
| | | | |
| − | *[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/development/org.eclipse.wst.jsdt.debug.crossfire/?root=WebTools_Project org.eclipse.wst.jsdt.debug.crossfire] - the core Crossfire implementation, provides the Crossfire-specific implementation of [[JSDT/Debug/JavaScript Debug Interface|JSDI]] | + | *[http://git.eclipse.org/c/jsdt/webtools.jsdt.debug.git/tree/bundles/org.eclipse.wst.jsdt.debug.crossfire org.eclipse.wst.jsdt.debug.crossfire] - the core Crossfire implementation, provides the Crossfire-specific implementation of [[JSDT/Debug/JavaScript Debug Interface|JSDI]] |
| − | | + | |
| − | == Setting up a Crossfire Development Workspace ==
| + | |
| − | | + | |
| − | ==== Create a Development Profile ====
| + | |
| − | #Download your desired version of the source from http://fbug.googlecode.com/svn/
| + | |
| − | #Create a Firefox profile.
| + | |
| − | #Start Firefox with the following argument ''-ProfileManager'' - the profile manager will open up allowing you to select or create a profile
| + | |
| − | #Create a new profile, make a note of the location that profile information will be stored in
| + | |
| − | | + | |
| − | Once done you should have a new profile with your chosen name in your Mozilla directory. For example, in Linux the following
| + | |
| − | directory is created: ''/home//.mozilla/firefox/'' and in Windows 7: ''<user root>\AppData\Local\Mozilla\Firefox\Profiles''. More information on profiles can be found at [http://kb.mozillazine.org/Profile_Manager Mozillazine].
| + | |
| − | | + | |
| − | ==== Finding Extension IDs ====
| + | |
| − | The next step requires you to find the ids of the extensions we want to load from source. To do so we have to look in the ''install.rdf''
| + | |
| − | files for each of the extensions. The ''install.rdf'' file is located in the root of the extension source, for example [http://fbug.googlecode.com/svn/branches/firebug1.6/install.rdf] is the ''install.rdf'' for the 1.6 branch of Firebug.
| + | |
| − | | + | |
| − | To collect the ID, open the ''install.rdf'' file in the directory of the extension you want to install (root, firebug, crossfire)
| + | |
| − | and look for the ID in the section:
| + | |
| − | <pre>
| + | |
| − | <Description about="urn:mozilla:install-manifest">
| + | |
| − | <em:id>crossfire@almaden.ibm.com</em:id>
| + | |
| − | <em:name>Crossfire</em:name
| + | |
| − | </pre>
| + | |
| | | | |
| − | ==== Create an Extension Link ==== | + | == Resources == |
| − | Remembering the location of your new development profile, and with the ids of the extensions we want to be installed, we now must create link files to tell Firefox
| + | |
| − | where to find your extensions.
| + | |
| | | | |
| − | We can do this as follows:
| + | The [https://github.com/mrennie/crossfire/wiki Github wiki] for Crossfire contains all the information you could ever want. |
| − | #Open your profile directory, for example /home//.mozilla/firefox/h34h5.dev
| + | |
| − | #Open the extensions subdirectory (create it if it doesn't exist), for example /home//.mozilla/firefox/h34h5.dev/extensions
| + | |
| − | #Create a new file named using the extension id (eg: "crossfire@almaden.ibm.com"). Don't add any file extension.
| + | |
| − | #Inside the file put a single line containing the absolute path to your source extension
| + | |
| − |
| + | |
| − | ==== Finish Up ====
| + | |
| − | #Start Firefox with your new development profile and ensure your extensions have been installed properly.
| + | |
| − | #Start firefox with either ''-ProfileManager'' (and select your profile) or with ''-P''
| + | |
| − | #Check the "add-ons" menu to see if your extension installed correctly
| + | |
