Search results
Jump to navigation
Jump to search
- * [[UFO-Scripts]] * [[UFO-Scripts/Datatypes|Datatypes]]904 bytes (121 words) - 13:37, 2 September 2015
- ...e]]). These files include the [[UFO-Scripts/ui/*.ufo|menu definitions]], [[UFO-Scripts/weapon_*.ufo|weapon definitions]] and a lot more. You might first have to e Make sure, that you looked into the [[Coding/Guidelines|coding guidelines]] before submitting patches.3 KB (429 words) - 15:09, 27 January 2016
- See also [[Coding/Guidelines#Documenting_code|Coding/Guidelines -> Documenting code]].563 bytes (78 words) - 19:51, 29 April 2007
- ...log]] available. Please also have a look at the [[Coding guidelines|coding guidelines]].3 KB (499 words) - 20:03, 10 October 2015
- ...how a "noncommercial" Creative Commons license relates to e.g. the license guidelines of the Debian distribution. i.e. can stuff with that license be shipped wit ...the least restrictive of the licenses, adheres to the Debian Free Software Guidelines due to the license's anti-DRM provisions and its requirement in section 4a6 KB (1,060 words) - 20:56, 23 January 2008
- Using the ufox build-functions requires you to adhere to the following guidelines:4 KB (602 words) - 06:29, 28 January 2016
- The following numbers are rough guidelines for the various upper limits. They are already a bit dated now and by no me7 KB (1,071 words) - 19:37, 1 May 2014
- ...for Destructavator contributed music, making it compatible with OSS/Debian guidelines.</li>25 KB (3,837 words) - 14:55, 8 May 2010
- These are guidelines about whitespace usage between the function name and the left bracket that12 KB (1,880 words) - 14:43, 27 December 2010
- ** General fixes and improvements (reduced scope, const variables and coding guidelines).23 KB (3,497 words) - 21:40, 25 December 2015