Development:Coding - Revision history

Tsala: /* Usability */ rewording

2010-05-14T08:00:52Z

Usability: rewording

← Older revision		Revision as of 08:00, 14 May 2010
Line 67:		Line 67:
	==Usability==		==Usability==

	See: [[Development:~~Moodle_User_Interface_Guidelines~~\|~~Moodle User~~ Interface Guidelines]] (~~being produced summer 2009~~)		See [[Development:Interface_guidelines\| Interface Guidelines]] (under construction)
	* Implementing user interfaces: [[Development:Interface_guidelines\| Interface Guidelines]]

	==Performance==		==Performance==

Mudrd8mz: /* Internationalisation */

2010-04-02T15:06:21Z

Internationalisation

← Older revision		Revision as of 15:06, 2 April 2010
Line 55:		Line 55:
	Moodle works in over 84 languages because we pay great attention to keeping the language strings and locale information separate from the code, in language packs.		Moodle works in over 84 languages because we pay great attention to keeping the language strings and locale information separate from the code, in language packs.

	The default language for all code and documentation, however, is English (AU).		The default language for all code, comments and documentation, however, is English (AU).

	Full details: [[Development:Internationalisation\|Moodle Internationalisation]]		Full details: [[Development:Internationalisation\|Moodle Internationalisation]]

Mudrd8mz: /* Internationalisation */

2010-04-02T14:48:36Z

Internationalisation

← Older revision		Revision as of 14:48, 2 April 2010
Line 53:		Line 53:
	==Internationalisation==		==Internationalisation==

	Moodle works in over 81 languages because we pay great attention to keeping the language strings and locale information separate from the code, in language packs.		Moodle works in over 84 languages because we pay great attention to keeping the language strings and locale information separate from the code, in language packs.

	The default language for all code and documentation, however, is English (AU).		The default language for all code and documentation, however, is English (AU).

Tsala: category edit

2009-11-26T17:23:43Z

category edit

← Older revision		Revision as of 17:23, 26 November 2009
Line 107:		Line 107:


	~~[[Category:Developer\|Coding]]~~
	[[Category:Coding guidelines\|Coding]]		[[Category:Coding guidelines\|Coding]]

Tsala: category

2009-11-26T17:21:48Z

TimHunt: /* Performance */

2009-11-26T14:50:25Z

Performance

← Older revision		Revision as of 14:50, 26 November 2009
Line 76:		Line 76:
	The most important property is scalability, so a small increase in the number of users, courses, activities in a course, and so on, only causes a correspondingly small increase in server load.		The most important property is scalability, so a small increase in the number of users, courses, activities in a course, and so on, only causes a correspondingly small increase in server load.

	For more information and advice, see [[Development:Performance]].		For more information and advice, see [[Development:Performance and scalability\|Performance and scalability]].


	==Database==		==Database==

TimHunt at 14:46, 26 November 2009

2009-11-26T14:46:47Z

← Older revision		Revision as of 14:46, 26 November 2009
Line 69:		Line 69:
	See: [[Development:Moodle_User_Interface_Guidelines\|Moodle User Interface Guidelines]] (being produced summer 2009)		See: [[Development:Moodle_User_Interface_Guidelines\|Moodle User Interface Guidelines]] (being produced summer 2009)
	* Implementing user interfaces: [[Development:Interface_guidelines\| Interface Guidelines]]		* Implementing user interfaces: [[Development:Interface_guidelines\| Interface Guidelines]]

			==Performance==

			The load any Moodle site can cope with will, of course, depend on the server and network hardware that it is running on.

			The most important property is scalability, so a small increase in the number of users, courses, activities in a course, and so on, only causes a correspondingly small increase in server load.

			For more information and advice, see [[Development:Performance]].


	==Database==		==Database==

TimHunt: /* XHTML */

2009-11-13T10:37:43Z

XHTML

← Older revision		Revision as of 10:37, 13 November 2009
Line 33:		Line 33:
	Any single script (in Moodle core or a third party module) can introduce a vulnerability to thousands of sites, so it's important that all developers strictly follow our [[Development:Security\|Moodle security guidelines]].		Any single script (in Moodle core or a third party module) can introduce a vulnerability to thousands of sites, so it's important that all developers strictly follow our [[Development:Security\|Moodle security guidelines]].

	==XHTML==		==XHTML and CSS==

	It's important that Moodle produces strict, well-formed XHTML code, compliant with all common accessibility guidelines (such as W3C WAG).		It's important that Moodle produces strict, well-formed XHTML code, compliant with all common accessibility guidelines (such as W3C WAG).

			CSS should be used for layout. Moodle comes with several themes installed. The 'standard' theme, which should be a plain theme suitable to act as a building block for other themes. That should contain the minimal styling to make Moodle look OK and be function. Then Moodle comes with several other default themes that look good and demonstrate various techniques for building themes.

	This helps consistency across browsers in a nicely-degrading way (especially those using non-visual or mobile browsers), as well as improving life for theme designers.		This helps consistency across browsers in a nicely-degrading way (especially those using non-visual or mobile browsers), as well as improving life for theme designers.

Josepuib at 21:50, 25 August 2009

2009-08-25T21:50:49Z

← Older revision		Revision as of 21:50, 25 August 2009
Line 21:		Line 21:
	Consistent coding style is important in any development project, and particularly so when many developers are involved. A standard style helps to ensure that the code is easier to read and understand, which helps overall quality.		Consistent coding style is important in any development project, and particularly so when many developers are involved. A standard style helps to ensure that the code is easier to read and understand, which helps overall quality.

	Writing your code in this way ~~will ensure your code~~ is an important step to having your code accepted by the Moodle community.		Writing your code in this way is an important step to having your code accepted by the Moodle community.

	Our [[Development:Coding_style\|Moodle coding style]] document explains this standard.		Our [[Development:Coding_style\|Moodle coding style]] document explains this standard.

Pilpi: /* Usability */

2009-06-29T16:39:51Z

Usability

← Older revision		Revision as of 16:39, 29 June 2009
Line 66:		Line 66:

	See: [[Development:Moodle_User_Interface_Guidelines\|Moodle User Interface Guidelines]] (being produced summer 2009)		See: [[Development:Moodle_User_Interface_Guidelines\|Moodle User Interface Guidelines]] (being produced summer 2009)
	* ~~The preceding~~ [[Development:Interface_guidelines\| Interface Guidelines]]		* Implementing user interfaces: [[Development:Interface_guidelines\| Interface Guidelines]]

	==Database==		==Database==

← Older revision		Revision as of 17:21, 26 November 2009
Line 108:		Line 108:

	[[Category:Developer\|Coding]]		[[Category:Developer\|Coding]]
			[[Category:Coding guidelines\|Coding]]

	[[es:Manual de Estilo de Código]]		[[es:Manual de Estilo de Código]]