CSC/ECE 517 Fall 2016/M1653 Implement HTML form validation - Revision history

Ysun34: /* Project description */

2016-11-05T05:44:38Z

Project description

← Older revision		Revision as of 05:44, 5 November 2016
Line 41:		Line 41:

	===Implemented steps===		===Implemented steps===
			*Change using enum to bitflags that represents each possible validity check in <code>ValidityState</code>.
			[[File:Bitflags.JPG]]

	*Defined a trait <code>Validatable</code> in <code>validation.rs</code> file that contains methods to be used for validating an html element.		*Defined a trait <code>Validatable</code> in <code>validation.rs</code> file that contains methods to be used for validating an html element.
	[[File:Validation.JPG]]		[[File:Validation.JPG]]

Ysun34: /* Project description */

2016-11-05T05:41:55Z

Project description

← Older revision		Revision as of 05:41, 5 November 2016
Line 42:		Line 42:
	===Implemented steps===		===Implemented steps===
	*Defined a trait <code>Validatable</code> in <code>validation.rs</code> file that contains methods to be used for validating an html element.		*Defined a trait <code>Validatable</code> in <code>validation.rs</code> file that contains methods to be used for validating an html element.
	[[File:~~Validatable~~.~~PNG~~]]		[[File:Validation.JPG]]

	*The traits for different form elements like Input text, Input submit, Input Button, Input Image are defined in htmlInputElement.rs		*The traits for different form elements like Input text, Input submit, Input Button, Input Image are defined in htmlInputElement.rs
	[[File:Inputelement.~~PNG~~]]		[[File:Inputelement.JPG]]

	*The code below will check the type of elements from the form and if they are input elements then it will call the <code>is_instance_validatable</code> function to check the validation.		*The code below will check the type of elements from the form and if they are input elements then it will call the <code>is_instance_validatable</code> function to check the validation.
	[[File:Formelement.~~PNG~~]]		[[File:Formelement.JPG]]

	===Challenges faced===		===Challenges faced===

Ysun34: /* Design patterns & o-o practices */

2016-11-05T05:29:55Z

Design patterns & o-o practices

← Older revision		Revision as of 05:29, 5 November 2016
Line 59:		Line 59:

	=='''Design patterns & o-o practices'''==		=='''Design patterns & o-o practices'''==
	This project is to add some features to servo, so we were not supposed to change the design of original servo project. Throughout the development process, we tried to follow good o-o practices by following DRY, giving the elements and functions the correct names and we tried and maintained the servo and rust coding standards.		This project is to add some features to servo, so we were not supposed to change the design of original servo project. However, after further discuss with servo project member, we found a disadvantage of the original design of using enum. Therefore we have made an agreement on changing this into using bitflags. Throughout the development process, we tried to follow good o-o practices by following DRY, giving the elements and functions the correct names and we tried and maintained the servo and rust coding standards.

	=='''Test'''==		=='''Test'''==

Mshaikh at 20:16, 3 November 2016

2016-11-03T20:16:12Z

← Older revision		Revision as of 20:16, 3 November 2016
Line 75:		Line 75:
	./mach build -d		./mach build -d

	No error showed up, servo worked as expected with new code.		No error showed up, servo worked as expected with the new code.
	===Test from UI===		===Test from UI===
	At this stage, the project can't be tested from UI. There are still some subsequent steps to be implemented after this.		At this stage, the project can't be tested from UI. There are still some subsequent steps to be implemented after this.

	===For reviewers===		===For reviewers===
	In addition to the ~~reason~~ mentioned above, servo is a browser ~~but~~ not a web application. Therefore it can't be deployed on the cloud server. All these would make it hard for reviewers to test the correctness of code at this time.		In addition to the reasons mentioned above, the servo is a web browser and not a web application. Therefore it can't be deployed on the cloud server. All these would make it hard for reviewers to test the correctness of code at this time.

	=='''References'''==		=='''References'''==
	<references />		<references />

Ysun34: /* Test from ui */

2016-10-31T23:16:29Z

Test from ui

← Older revision		Revision as of 23:16, 31 October 2016
Line 76:		Line 76:

	No error showed up, servo worked as expected with new code.		No error showed up, servo worked as expected with new code.
	===Test from ui===		===Test from UI===
	At this stage, the project can't be tested from UI. There are still some subsequent steps to be implemented after this.		At this stage, the project can't be tested from UI. There are still some subsequent steps to be implemented after this.

	===For reviewers===		===For reviewers===
	In addition to the reason mentioned above, servo is a browser but not a web application. Therefore it can't be deployed on the cloud server. All these would make it hard for reviewers to test the correctness of code at this time.		In addition to the reason mentioned above, servo is a browser but not a web application. Therefore it can't be deployed on the cloud server. All these would make it hard for reviewers to test the correctness of code at this time.

Ysun34: /* Test */

2016-10-31T23:16:17Z

Test

← Older revision		Revision as of 23:16, 31 October 2016
Line 76:		Line 76:

	No error showed up, servo worked as expected with new code.		No error showed up, servo worked as expected with new code.
			===Test from ui===
			At this stage, the project can't be tested from UI. There are still some subsequent steps to be implemented after this.
	===For reviewers===		===For reviewers===
	~~So far this project only contains initial steps~~, the ~~whole HTML form validation will be implemented after subsequent steps~~. So it ~~would be~~ hard for reviewers to test the correctness of code at this time.		In addition to the reason mentioned above, servo is a browser but not a web application. Therefore it can't be deployed on the cloud server. All these would make it hard for reviewers to test the correctness of code at this time.

	=='''References'''==		=='''References'''==
	<references />		<references />

Ysun34: fix some grammar mistakes

2016-10-31T22:57:32Z

fix some grammar mistakes

← Older revision		Revision as of 22:57, 31 October 2016
Line 1:		Line 1:
	[https://servo.org Servo] is a modern high performance web browser developed by Mozilla with Samsung porting it on android and arm processors<ref>https://en.wikipedia.org/wiki/Servo_(layout_engine)</ref>. The source code is written in the [https://www.rust-lang.org/en-US/ rust] programming language, which is a ~~new~~ developed system level programming language. The major advantage of rust language is that it is thread-safe<ref>https://www.rust-lang.org/en-US/</ref>. This project implements ~~html~~ form validation on servo browser.		[https://servo.org Servo] is a modern high-performance web browser developed by Mozilla with Samsung porting it on android and arm processors<ref>https://en.wikipedia.org/wiki/Servo_(layout_engine)</ref>. The source code is written in the [https://www.rust-lang.org/en-US/ rust] programming language, which is a newly developed system level programming language. The major advantage of rust language is that it is thread-safe<ref>https://www.rust-lang.org/en-US/</ref>. This project implements HTML form validation on servo browser.

	=='''Introduction'''==		=='''Introduction'''==
	The [https://en.wikipedia.org/wiki/HTML5 HTML5]is a markup language used for content organizing and showing on the World Wide Web<ref>https://en.wikipedia.org/wiki/HTML5</ref>. It defines set of ~~specification~~ which users needs to follow to make web pages HTML5 compliant. In HTML 5 there is a major type of element which is form element. When user trying to submit their form, the system should be able to check the validation status of this form and decide whether accept this form or reject the request. HTML provides such mechanism. Using this mechanism will allow the system to check whether the contents of forms are validated before it is allowed to submit. [https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo] currently implements validation check for some of the form element types. The objective of this project is to define and implement validation check function and implement validate step for these HTML5 form elements.		The [https://en.wikipedia.org/wiki/HTML5 HTML5]is a markup language used for content organizing and showing on the World Wide Web<ref>https://en.wikipedia.org/wiki/HTML5</ref>. It defines a set of specifications which users needs to follow to make web pages HTML5 compliant. In HTML 5 there is a major type of element which is form element. When user trying to submit their form, the system should be able to check the validation status of this form and decide whether accept this form or reject the request. HTML provides such mechanism. Using this mechanism will allow the system to check whether the contents of forms are validated before it is allowed to submit. [https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo] currently implements validation check for some of the form element types. The objective of this project is to define and implement validation check function and implement validate step for these HTML5 form elements.

	===Servo===		===Servo===
	[https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo] is an open source prototype web browser layout engine that is being developed by Mozilla Research. Its source code can be found [https://github.com/servo/servo here]. Current browser engines are mostly based on single-~~threaded~~ model. ~~Motivation~~ behind building servo web browser is to build a highly parallel and reliable environment, where different components (such as rendering, layout, HTML parsing, image decoding, etc.) can be handled by fine-grained, isolated tasks.		[https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo] is an open source prototype web browser layout engine that is being developed by Mozilla Research. Its source code can be found [https://github.com/servo/servo here]. Current browser engines are mostly based on the single-thread model. The motivation behind building servo web browser is to build a highly parallel and reliable environment, where different components (such as rendering, layout, HTML parsing, image decoding, etc.) can be handled by fine-grained, isolated tasks.

	===Rust===		===Rust===
	[http://doc.rust-lang.org/book/README.html Rust] is an open source ~~systems~~ programming language developed by Mozilla. Rust is a language suited for creating a highly concurrent and safe ~~systems~~. In performance and syntax, rust is similar to C++ but semantically it is very different. Rust emphasis is on speed, safety and control of memory layout<ref>https://en.wikipedia.org/wiki/Rust_(programming_language)</ref>.		[http://doc.rust-lang.org/book/README.html Rust] is an open source system programming language developed by Mozilla. Rust is a language suited for creating a highly concurrent and safe system. In performance and syntax, rust is similar to C++ but semantically it is very different. Rust emphasis is on speed, safety and control of memory layout<ref>https://en.wikipedia.org/wiki/Rust_(programming_language)</ref>.

	=='''Project description'''==		=='''Project description'''==
Line 22:		Line 22:
	libssl-dev libglfw-dev		libssl-dev libglfw-dev

	* We then forked the original repository ~~from servo~~ and cloned the forked repository on our local machines and then compiled and ran the servo browser.		* We then forked the original servo repository and cloned the forked repository on our local machines and then compiled and ran the servo browser.

	cd servo		cd servo
Line 59:		Line 59:

	=='''Design patterns & o-o practices'''==		=='''Design patterns & o-o practices'''==
	This project is to add some features to servo, so we were not supposed to change the design of original servo project. Throughout the development process we tried to follow good o-o practices by following DRY, giving the elements and functions the correct names and we tried and maintained the servo and rust coding standards.		This project is to add some features to servo, so we were not supposed to change the design of original servo project. Throughout the development process, we tried to follow good o-o practices by following DRY, giving the elements and functions the correct names and we tried and maintained the servo and rust coding standards.

	=='''Test'''==		=='''Test'''==
Line 70:		Line 70:
	When we ran tidy we got 20 code style errors and we fixed all the errors.		When we ran tidy we got 20 code style errors and we fixed all the errors.
	===Compile test===		===Compile test===
	After adding code, we compiled the servo by following command		After adding code, we compiled the servo by the following command

	cd servo		cd servo

Ysun34: /* Testing */

2016-10-29T23:30:31Z

Testing

← Older revision		Revision as of 23:30, 29 October 2016
Line 61:		Line 61:
	This project is to add some features to servo, so we were not supposed to change the design of original servo project. Throughout the development process we tried to follow good o-o practices by following DRY, giving the elements and functions the correct names and we tried and maintained the servo and rust coding standards.		This project is to add some features to servo, so we were not supposed to change the design of original servo project. Throughout the development process we tried to follow good o-o practices by following DRY, giving the elements and functions the correct names and we tried and maintained the servo and rust coding standards.

	=='''~~Testing~~'''==		=='''Test'''==
	===~~Testing~~ with tidy===		===Test with tidy===
	Servo has its own code standard. We managed to meet its code standard by using the following command to run code style check.		Servo has its own code standard. We managed to meet its code standard by using the following command to run code style check.

Line 69:		Line 69:

	When we ran tidy we got 20 code style errors and we fixed all the errors.		When we ran tidy we got 20 code style errors and we fixed all the errors.
			===Compile test===
			After adding code, we compiled the servo by following command

			cd servo
			./mach build -d

			No error showed up, servo worked as expected with new code.
			===For reviewers===
			So far this project only contains initial steps, the whole HTML form validation will be implemented after subsequent steps. So it would be hard for reviewers to test the correctness of code at this time.

	=='''References'''==		=='''References'''==
	<references />		<references />

Ysun34: moved M1653 Implement HTML form validation to CSC/ECE 517 Fall 2016/M1653 Implement HTML form validation

2016-10-29T18:20:44Z

moved M1653 Implement HTML form validation to CSC/ECE 517 Fall 2016/M1653 Implement HTML form validation

← Older revision	Revision as of 18:20, 29 October 2016
(No difference)

Mshaikh: /* Testing */

2016-10-29T05:00:34Z

Testing

← Older revision		Revision as of 05:00, 29 October 2016
Line 69:		Line 69:

	When we ran tidy we got 20 code style errors and we fixed all the errors.		When we ran tidy we got 20 code style errors and we fixed all the errors.

	~~===Testing with ui===~~

	~~We created a test form to check our validation function.~~

	=='''References'''==		=='''References'''==
	<references />		<references />