CSC/ECE 517 Fall 2014/oss M1453 sst - Revision history

Srmuchha: /* Work done in Part 1 */

2014-11-11T01:32:47Z

Work done in Part 1

← Older revision		Revision as of 01:32, 11 November 2014
Line 143:		Line 143:
	The following two files were modified to include the new code.		The following two files were modified to include the new code.

	:*'''[https://github.com/shanil-puri/servo/blob/~~master~~/components/compositing/constellation.rs constellation.rs]'''		:*'''[https://github.com/shanil-puri/servo/blob/ServoExitDevtools/components/compositing/constellation.rs constellation.rs]'''
	:*'''[https://github.com/shanil-puri/servo/blob/~~master~~/components/devtools/lib.rs devtools/lib.rs]'''		:*'''[https://github.com/shanil-puri/servo/blob/ServoExitDevtools/components/devtools/lib.rs devtools/lib.rs]'''

	==Future Scope==		==Future Scope==

Traut: /* Developer tools */

2014-10-27T06:33:41Z

Developer tools

← Older revision		Revision as of 06:33, 27 October 2014
Line 6:		Line 6:

	===Developer tools===		===Developer tools===
	The Mozilla debugging protocol allows a debugger to connect to a browser, discover what sorts of things are present to debug or inspect, select [http://en.wikipedia.org/wiki/JavaScript JavaScript] threads to watch, and observe and modify their execution. The protocol provides a unified view of JavaScript, [http://en.wikipedia.org/wiki/Document_Object_Model DOM] nodes, [http://en.wikipedia.org/wiki/Cascading_Style_Sheets CSS] rules, and the other technologies used in client-side web applications. The protocol ought to be sufficiently general to be extended for use with other sorts of clients (profilers, say) and servers (mail readers; random XULrunner applications). <ref name="Remote debugging tools in Mozilla">https://wiki.mozilla.org/Remote_Debugging_Protocol</ref>		The Mozilla debugging protocol allows a debugger to connect to a browser, discover what sorts of things are present to debug or inspect, select [http://en.wikipedia.org/wiki/JavaScript JavaScript] threads to watch, and observe and modify their execution. The protocol provides a unified view of JavaScript, [http://en.wikipedia.org/wiki/Document_Object_Model DOM] nodes, [http://en.wikipedia.org/wiki/Cascading_Style_Sheets CSS] rules, and the other technologies used in client-side web applications. The protocol ought to be sufficiently general to be extended for use with other sorts of clients (profilers, say) and servers (mail readers; random [https://developer.mozilla.org/en-US/docs/Mozilla/Projects/XULRunner XULrunner] applications). <ref name="Remote debugging tools in Mozilla">https://wiki.mozilla.org/Remote_Debugging_Protocol</ref>

	All communication between debugger (client) and browser (server) is in the form of [http://en.wikipedia.org/wiki/JSON JSON] objects. This makes the protocol directly readable by humans, capable of graceful evolution, and easy to implement using stock libraries. In particular, it should be easy to create mock implementations for testing and experimentation.		All communication between debugger (client) and browser (server) is in the form of [http://en.wikipedia.org/wiki/JSON JSON] objects. This makes the protocol directly readable by humans, capable of graceful evolution, and easy to implement using stock libraries. In particular, it should be easy to create mock implementations for testing and experimentation.

Traut: /* Background Information */

2014-10-27T06:32:21Z

Background Information

← Older revision		Revision as of 06:32, 27 October 2014
Line 3:		Line 3:

	==Background Information==		==Background Information==
	Firefox supports remote debugging - i.e. communicating with an arbitrary server that implements a protocol for exposing information about web content. Servo implements a very basic developer tools server that currently supports executing JS remotely and investigating the [http://en.wikipedia.org/wiki/Document_Object_Model DOM] tree in the document inspector. We want to expand these capabilities by allowing remote modification of the DOM tree, better JS console integration (exposing historical and real-time exceptions), and enabling server->client messages that are not responses to client->server messages.		Firefox supports remote debugging - i.e. communicating with an arbitrary server that implements a protocol for exposing information about web content. Servo implements a very basic developer tools server that currently supports executing JS remotely and investigating the [http://en.wikipedia.org/wiki/Document_Object_Model DOM] tree in the document inspector. We want to expand these capabilities by allowing remote modification of the [http://en.wikipedia.org/wiki/Document_Object_Model DOM] tree, better JS console integration (exposing historical and real-time exceptions), and enabling server->client messages that are not responses to client->server messages.

	===Developer tools===		===Developer tools===

Traut: /* Background Information */

2014-10-27T06:31:56Z

Background Information

← Older revision		Revision as of 06:31, 27 October 2014
Line 3:		Line 3:

	==Background Information==		==Background Information==
	Firefox supports remote debugging - i.e. communicating with an arbitrary server that implements a protocol for exposing information about web content. Servo implements a very basic developer tools server that currently supports executing JS remotely and investigating the DOM tree in the document inspector. We want to expand these capabilities by allowing remote modification of the DOM tree, better JS console integration (exposing historical and real-time exceptions), and enabling server->client messages that are not responses to client->server messages.		Firefox supports remote debugging - i.e. communicating with an arbitrary server that implements a protocol for exposing information about web content. Servo implements a very basic developer tools server that currently supports executing JS remotely and investigating the [http://en.wikipedia.org/wiki/Document_Object_Model DOM] tree in the document inspector. We want to expand these capabilities by allowing remote modification of the DOM tree, better JS console integration (exposing historical and real-time exceptions), and enabling server->client messages that are not responses to client->server messages.

	===Developer tools===		===Developer tools===

Traut: /* Installing dependencies for Servo */

2014-10-27T06:30:23Z

Installing dependencies for Servo

← Older revision		Revision as of 06:30, 27 October 2014
Line 40:		Line 40:
	===Installing dependencies for Servo===		===Installing dependencies for Servo===
	The following are the commands to install dependencies for servo on different platforms:<ref name="Installing servo">https://github.com/servo/servo</ref>		The following are the commands to install dependencies for servo on different platforms:<ref name="Installing servo">https://github.com/servo/servo</ref>

	On OS X (homebrew):		On OS X (homebrew):
	brew install automake pkg-config python glfw3 cmake		brew install automake pkg-config python glfw3 cmake

Traut: /* Installing dependencies for Servo */

2014-10-27T06:30:03Z

Installing dependencies for Servo

← Older revision		Revision as of 06:30, 27 October 2014
Line 39:		Line 39:
	==Project Description==		==Project Description==
	===Installing dependencies for Servo===		===Installing dependencies for Servo===
	The following are the commands to install dependencies for servo on different platforms:<ref name=Installing servo>https://github.com/servo/servo</ref>		The following are the commands to install dependencies for servo on different platforms:<ref name="Installing servo">https://github.com/servo/servo</ref>
	On OS X (homebrew):		On OS X (homebrew):
	brew install automake pkg-config python glfw3 cmake		brew install automake pkg-config python glfw3 cmake

Traut: /* Installing dependencies for Servo */

2014-10-27T06:27:24Z

Installing dependencies for Servo

← Older revision		Revision as of 06:27, 27 October 2014
Line 39:		Line 39:
	==Project Description==		==Project Description==
	===Installing dependencies for Servo===		===Installing dependencies for Servo===
			The following are the commands to install dependencies for servo on different platforms:<ref name=Installing servo>https://github.com/servo/servo</ref>
	On OS X (homebrew):		On OS X (homebrew):
	brew install automake pkg-config python glfw3 cmake		brew install automake pkg-config python glfw3 cmake
Line 70:		Line 71:
	On Arch Linux:		On Arch Linux:
	sudo pacman -S base-devel git python2 python2-virtualenv mesa glfw ttf-font cmake		sudo pacman -S base-devel git python2 python2-virtualenv mesa glfw ttf-font cmake

	~~Reference :https://github.com/servo/servo~~

	===Building Servo===		===Building Servo===

Traut: /* Rust */

2014-10-27T06:23:33Z

Rust

← Older revision		Revision as of 06:23, 27 October 2014
Line 36:		Line 36:

	If you used the Windows installer, just re-run the .exe and it will give you an uninstall option.		If you used the Windows installer, just re-run the .exe and it will give you an uninstall option.


	~~Reference : http://doc.rust-lang.org~~

	~~Download Rust at: http://www.rust-lang.org/~~

	==Project Description==		==Project Description==

Traut: /* Developer tools */

2014-10-27T06:22:22Z

Developer tools

← Older revision		Revision as of 06:22, 27 October 2014
Line 6:		Line 6:

	===Developer tools===		===Developer tools===
	The Mozilla debugging protocol allows a debugger to connect to a browser, discover what sorts of things are present to debug or inspect, select [http://en.wikipedia.org/wiki/JavaScript JavaScript] threads to watch, and observe and modify their execution. The protocol provides a unified view of JavaScript, [http://en.wikipedia.org/wiki/Document_Object_Model DOM] nodes, [http://en.wikipedia.org/wiki/Cascading_Style_Sheets CSS] rules, and the other technologies used in client-side web applications. The protocol ought to be sufficiently general to be extended for use with other sorts of clients (profilers, say) and servers (mail readers; random XULrunner applications).		The Mozilla debugging protocol allows a debugger to connect to a browser, discover what sorts of things are present to debug or inspect, select [http://en.wikipedia.org/wiki/JavaScript JavaScript] threads to watch, and observe and modify their execution. The protocol provides a unified view of JavaScript, [http://en.wikipedia.org/wiki/Document_Object_Model DOM] nodes, [http://en.wikipedia.org/wiki/Cascading_Style_Sheets CSS] rules, and the other technologies used in client-side web applications. The protocol ought to be sufficiently general to be extended for use with other sorts of clients (profilers, say) and servers (mail readers; random XULrunner applications). <ref name="Remote debugging tools in Mozilla">https://wiki.mozilla.org/Remote_Debugging_Protocol</ref>

	All communication between debugger (client) and browser (server) is in the form of [http://en.wikipedia.org/wiki/JSON JSON] objects. This makes the protocol directly readable by humans, capable of graceful evolution, and easy to implement using stock libraries. In particular, it should be easy to create mock implementations for testing and experimentation.		All communication between debugger (client) and browser (server) is in the form of [http://en.wikipedia.org/wiki/JSON JSON] objects. This makes the protocol directly readable by humans, capable of graceful evolution, and easy to implement using stock libraries. In particular, it should be easy to create mock implementations for testing and experimentation.

	The protocol operates at the JavaScript level, not at the [http://en.wikipedia.org/wiki/C%2B%2B C++] or machine level, and assumes that the JavaScript implementation itself is healthy and responsive. The JavaScript program being executed may well have gone wrong, but the JavaScript implementation's internal state must not be corrupt. Bugs in the implementation may cause the debugger to fail; bugs in the interpreted program must not.		The protocol operates at the JavaScript level, not at the [http://en.wikipedia.org/wiki/C%2B%2B C++] or machine level, and assumes that the JavaScript implementation itself is healthy and responsive. The JavaScript program being executed may well have gone wrong, but the JavaScript implementation's internal state must not be corrupt. Bugs in the implementation may cause the debugger to fail; bugs in the interpreted program must not.

	~~Reference: https://wiki.mozilla.org/Remote_Debugging_Protocol~~

	'''Setting up remote debugging'''		'''Setting up remote debugging'''

Traut: /* Rust */

2014-10-27T06:20:03Z

Rust

← Older revision		Revision as of 06:20, 27 October 2014
Line 31:		Line 31:
	There are a number of ways to install Rust, but the easiest is to use the rustup script. If you're on Linux or a Mac, all you need to do is this:		There are a number of ways to install Rust, but the easiest is to use the rustup script. If you're on Linux or a Mac, all you need to do is this:
	$ curl -s https://static.rust-lang.org/rustup.sh \| sudo sh		$ curl -s https://static.rust-lang.org/rustup.sh \| sudo sh
	(If you're concerned about curl \| sudo sh, check references).<ref name="building-from-source">https://github.com/rust-lang/rust~~#building-from-source~~</ref><ref name="lang-install">http://www.rust-lang.org/install.html</ref>		(If you're concerned about curl \| sudo sh, check references).<ref name="building-from-source">https://github.com/rust-lang/rust</ref><ref name="lang-install">http://www.rust-lang.org/install.html</ref>
	If you're on Windows, please download either the 32-bit installer or the 64-bit installer and run it.		If you're on Windows, please download either the 32-bit installer or the 64-bit installer and run it.