OOP Introduction - Revision history

IManGaaX at 05:52, 6 November 2023

2023-11-06T05:52:34Z

← Older revision		Revision as of 05:52, 6 November 2023
Line 45:		Line 45:
	player.dimension = player.dimension + 1 -- increment dimension		player.dimension = player.dimension + 1 -- increment dimension
	end		end
	~~setTimer~~(incrementDimension, 60*1000, 10) -- set a timer for sixty thousand milliseconds, sixty seconds, one minute		Timer(incrementDimension, 60*1000, 10) -- set a timer for sixty thousand milliseconds, sixty seconds, one minute
	</syntaxhighlight>		</syntaxhighlight>
	This code would take a random player and move them to the next dimension every minute for the next ten minutes.		This code would take a random player and move them to the next dimension every minute for the next ten minutes.

IManGaaX at 05:49, 6 November 2023

2023-11-06T05:49:12Z

← Older revision		Revision as of 05:49, 6 November 2023
Line 26:		Line 26:
	Instead of the code before, the code could be replaced with this:		Instead of the code before, the code could be replaced with this:
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	local vehicle = ~~createVehicle~~(411, 0, 0, 3)		local vehicle = Vehicle(411, 0, 0, 3)
	vehicle:setDamageProof(true)		vehicle:setDamageProof(true)
	vehicle:setFrozen(true)		vehicle:setFrozen(true)

Thisdp at 03:52, 3 February 2021

2021-02-03T03:52:57Z

← Older revision		Revision as of 03:52, 3 February 2021
Line 95:		Line 95:

	[[hu:OOP Introduction]]		[[hu:OOP Introduction]]
	[[zh-cn:~~OOP Introduction~~]]		[[zh-cn:OOP介绍]]

Thisdp at 03:52, 3 February 2021

2021-02-03T03:52:38Z

← Older revision		Revision as of 03:52, 3 February 2021
Line 95:		Line 95:

	[[hu:OOP Introduction]]		[[hu:OOP Introduction]]
			[[zh-cn:OOP Introduction]]

Qaisjp: tweak text

2019-09-07T08:44:01Z

tweak text

← Older revision		Revision as of 08:44, 7 September 2019
Line 1:		Line 1:
	{{Note\|If you've contributed by editing and tweaking this forum page, if you've benefited from this tutorial, or if you have anything to say; please give me feedback in the forum link provided ~~on the left~~.}}		{{Note\|If you've contributed by editing and tweaking this forum page, if you've benefited from this tutorial, or if you have anything to say; please give me feedback in the forum link provided below.}}
	This is a scripting tutorial explaining to you what object orientated programming is and teaching you how to use the OOP features of MTA. This was originally created by [[User:Qais\|qaisjp]] ([[User talk:Qais\|talk]]) 22:48, 8 June 2014 (UTC). [http://forum.mtasa.com/viewtopic.php?f=148&t=76388 Forum post.]		This is a scripting tutorial explaining to you what object orientated programming is and teaching you how to use the OOP features of MTA. This was originally created by [[User:Qais\|qaisjp]] ([[User talk:Qais\|talk]]) 22:48, 8 June 2014 (UTC). [http://forum.mtasa.com/viewtopic.php?f=148&t=76388 Forum post.]

Qaisjp: prefer normal note

2019-09-07T08:43:49Z

prefer normal note

← Older revision		Revision as of 08:43, 7 September 2019
Line 1:		Line 1:
	{{~~Note_box~~\|If you've contributed by editing and tweaking this forum page, if you've benefited from this tutorial, or if you have anything to say; please give me feedback in the forum link provided on the left.}}		{{Note\|If you've contributed by editing and tweaking this forum page, if you've benefited from this tutorial, or if you have anything to say; please give me feedback in the forum link provided on the left.}}
	This is a scripting tutorial explaining to you what object orientated programming is and teaching you how to use the OOP features of MTA. This was originally created by [[User:Qais\|qaisjp]] ([[User talk:Qais\|talk]]) 22:48, 8 June 2014 (UTC). [http://forum.mtasa.com/viewtopic.php?f=148&t=76388 Forum post.]		This is a scripting tutorial explaining to you what object orientated programming is and teaching you how to use the OOP features of MTA. This was originally created by [[User:Qais\|qaisjp]] ([[User talk:Qais\|talk]]) 22:48, 8 June 2014 (UTC). [http://forum.mtasa.com/viewtopic.php?f=148&t=76388 Forum post.]

Surge: /* Introduction to OOP */

2018-12-03T19:22:00Z

Introduction to OOP

← Older revision		Revision as of 19:22, 3 December 2018
Line 22:		Line 22:

	Problem children are weird things. You can't do all the functions mentioned in (actually, all elements don't allow the full assortment of functions to be applied to them, but I've especially mentioned a few of them) in the "Element functions" section of the functions list, but you can do destroyElement() on them.		Problem children are weird things. You can't do all the functions mentioned in (actually, all elements don't allow the full assortment of functions to be applied to them, but I've especially mentioned a few of them) in the "Element functions" section of the functions list, but you can do destroyElement() on them.
	There are children of classes, for example, with players, the system goes like: ''Element -> Ped -> Player". All Players are Peds and all Peds are Elements. Not all Peds are Players, and certainly not all Elements are Players. The main point here is that almost everything that you can create or retrieve and then reuse later use a class.		There are children of classes, for example, with players, the system goes like: "''Element -> Ped -> Player''". All Players are Peds and all Peds are Elements. Not all Peds are Players, and certainly not all Elements are Players. The main point here is that almost everything that you can create or retrieve and then reuse later use a class.

	Instead of the code before, the code could be replaced with this:		Instead of the code before, the code could be replaced with this:

Surge: /* Introduction to OOP */

2018-12-03T16:52:30Z

Introduction to OOP

← Older revision		Revision as of 16:52, 3 December 2018
Line 15:		Line 15:
	More often than not, you know what you're dealing with. The variable almost always links back to the type, you would name a vehicle that exploded as '''explodedVehicle''', or at-least in context you would understand that '''exploded''' implies a vehicle when in the '''onVehicleExplode''' event. So you have to write a long function ''and'' refer to the vehicle manually when working procedurally. Painful. Object orientated programming is very different to this and works with each "object" individually. Instead of having to call a function and referencing it inside the call, you actually call the function INSIDE the class.		More often than not, you know what you're dealing with. The variable almost always links back to the type, you would name a vehicle that exploded as '''explodedVehicle''', or at-least in context you would understand that '''exploded''' implies a vehicle when in the '''onVehicleExplode''' event. So you have to write a long function ''and'' refer to the vehicle manually when working procedurally. Painful. Object orientated programming is very different to this and works with each "object" individually. Instead of having to call a function and referencing it inside the call, you actually call the function INSIDE the class.

	You probably think everything you can create and pass to functions are elements. A vehicle is an element. A player is an element. Anything that is an element is also a class. Connections create an instance of a class, but "'''connection'''" isn't an element, it's an instance - an object. Throughout the tutorial when I say ''object'', I don't mean [[createObject]] (unless I actually mention it, but to make things clearer I will avoid mentioning physical objects as I write this article. Here is a fancy venn diagram I created to show the simple organisation of classes and elements.		You probably think everything you can create and pass to functions are elements. A vehicle is an element. A player is an element. Anything that is an element is also a class. Connections create an instance of a class, but "'''connection'''" isn't an element, it's an instance - an object. Throughout the tutorial when I say ''object'', I don't mean [[createObject]] (unless I actually mention it), but to make things clearer I will avoid mentioning physical objects as I write this article. Here is a fancy venn diagram I created to show the simple organisation of classes and elements.
	[[File:Classes,_Elements_and_Problem_children.png\|500px\|left\|venn diagram]]		[[File:Classes,_Elements_and_Problem_children.png\|500px\|left\|venn diagram]]
	The functions on the left are sorted to show what kind of category the returned value rests in. We've got Classes, Elements and "Problem children".		The functions on the left are sorted to show what kind of category the returned value rests in. We've got Classes, Elements and "Problem children".

Surge at 14:05, 3 December 2018

2018-12-03T14:05:29Z

← Older revision		Revision as of 14:05, 3 December 2018
Line 93:		Line 93:
	[[Category:Incomplete]]		[[Category:Incomplete]]
	[[Category:Tutorials]]		[[Category:Tutorials]]

			[[hu:OOP Introduction]]

Qaisjp: /* Understanding the documentation */ update e.g

2016-08-07T19:01:59Z

Understanding the documentation: update e.g

← Older revision		Revision as of 19:01, 7 August 2016
Line 75:		Line 75:
	The documentation for the OOP syntax intends to be very simplistic and is supported by the procedural syntax. To keep things simple, everything is consistently formatted in a certain way.		The documentation for the OOP syntax intends to be very simplistic and is supported by the procedural syntax. To keep things simple, everything is consistently formatted in a certain way.
	<section name="Example" class="generic" show="true">		<section name="Example" class="generic" show="true">
	{{OOP\|~~This function has been dropped in favour of~~ [[~~setPlayerHudComponentVisible~~]] \|[[~~player~~]]~~.getRandom~~\|~~random~~\|~~isPlayerHudComponentVisible~~}}		{{OOP\|Set the variable to nil to execute [[removePedFromVehicle]]\|[[ped]]:warpIntoVehicle\|vehicle\|getPedOccupiedVehicle}}
	</section>		</section>