Talk:Main Page - Revision history

Mcfloy at 18:56, 27 December 2017

2017-12-27T18:56:55Z

← Older revision		Revision as of 18:56, 27 December 2017
Line 2:		Line 2:

	For example:		For example:
	* '''Naming the templates''': ~~Some templates~~ have no ''s'' ~~in their name (like ''Blip function'') whereas ''Blips colours'' have two. For now i'll just format it so the type keep in singular form and put the function~~ with ~~an "s". '''I'll put a list of wiki~~ pages ~~that will be no longer useful~~ and ~~that must be deleted'''~~		* '''Naming the templates''': Defining a type must have the ''definition'' suffix with 2 pages (one for functions and one for properties)
	* '''Add a 'c' at the end of your template name if it's a ~~clientside function~~'''~~: We could also put a suffix on each template names for that but that'll create a lot of redirects for now.~~		* '''Add a 'c' at the end of your template name if it's a client-side definition'''
	* '''Sorting the functions and properties alphabetically''': Keep the types with themselves, but sort them alphabetically so it's simpler to look at a function in all this mess. If you see that you're using a template and you can't sort them perfectly, create a new template.		* '''Sorting the functions and properties alphabetically''': Keep the types with themselves, but sort them alphabetically so it's simpler to look at a function in all this mess. If you see that you're using a template and you can't sort them perfectly, create a new template.
	* '''Mother-class always last''': As some classes are inherited (like Player), the mother class shall be put at last. (For example every properties of Entity must be listed after properties of Player)		* '''Mother-class always last''': As some classes are inherited (like Player), the mother class shall be put at last. (For example every properties of Entity must be listed after properties of Player)

Mcfloy: It's more logical to put the mother-class after as the constructor must be the first function.

2017-12-27T15:48:30Z

It's more logical to put the mother-class after as the constructor must be the first function.

← Older revision		Revision as of 15:48, 27 December 2017
Line 5:		Line 5:
	* '''Add a 'c' at the end of your template name if it's a clientside function''': We could also put a suffix on each template names for that but that'll create a lot of redirects for now.		* '''Add a 'c' at the end of your template name if it's a clientside function''': We could also put a suffix on each template names for that but that'll create a lot of redirects for now.
	* '''Sorting the functions and properties alphabetically''': Keep the types with themselves, but sort them alphabetically so it's simpler to look at a function in all this mess. If you see that you're using a template and you can't sort them perfectly, create a new template.		* '''Sorting the functions and properties alphabetically''': Keep the types with themselves, but sort them alphabetically so it's simpler to look at a function in all this mess. If you see that you're using a template and you can't sort them perfectly, create a new template.
	* '''Mother-class always ~~first~~''': As some classes are inherited (like Player), the mother class shall be put at ~~first~~. (For example every properties of Entity must be listed ~~before~~ properties of Player)		* '''Mother-class always last''': As some classes are inherited (like Player), the mother class shall be put at last. (For example every properties of Entity must be listed after properties of Player)

Mcfloy: Rules for contributing on this wiki. (Community things, you must share your tips on contributing well here)

2017-12-27T15:46:04Z

Rules for contributing on this wiki. (Community things, you must share your tips on contributing well here)

New page

We should have some rules about contributing on the Wiki, just to format it in a proper ways.

For example:
* '''Naming the templates''': Some templates have no ''s'' in their name (like ''Blip function'') whereas ''Blips colours'' have two. For now i'll just format it so the type keep in singular form and put the function with an "s". '''I'll put a list of wiki pages that will be no longer useful and that must be deleted'''
* '''Add a 'c' at the end of your template name if it's a clientside function''': We could also put a suffix on each template names for that but that'll create a lot of redirects for now.
* '''Sorting the functions and properties alphabetically''': Keep the types with themselves, but sort them alphabetically so it's simpler to look at a function in all this mess. If you see that you're using a template and you can't sort them perfectly, create a new template.
* '''Mother-class always first''': As some classes are inherited (like Player), the mother class shall be put at first. (For example every properties of Entity must be listed before properties of Player)