HowTo Talk:Contents - Revision history

SharkD: /* External links? */ new section

2010-07-26T17:11:57Z

External links?: new section

SharkD: add heading

2010-07-26T17:11:10Z

add heading

Reactor: /* The Line Between Knowledgebase and Tutorial, v2 */

2009-08-16T06:09:15Z

The Line Between Knowledgebase and Tutorial, v2

Eddie: /* The Line Between Knowledgebase and Tutorial */

2007-12-29T00:34:44Z

The Line Between Knowledgebase and Tutorial

Reactor: New section: The Line Between Knowledgebase and Tutorial

2007-12-28T13:43:18Z

New section: The Line Between Knowledgebase and Tutorial

Reactor: /* Basic article suggestions */

2007-12-28T13:18:14Z

Basic article suggestions

Hymyly: /* Basic article suggestions */

2007-11-25T23:09:41Z

Basic article suggestions

Hymyly: /* Basic article suggestions */ Suggested advanced topics

2007-11-25T22:51:23Z

Basic article suggestions: Suggested advanced topics

Wound: /* Basic article suggestions */ corrected signing style

2007-11-21T19:34:04Z

Basic article suggestions: corrected signing style

Wound: /* Basic article suggestions */ coding: best practices

2007-11-21T19:28:18Z

Basic article suggestions: coding: best practices

← Older revision		Revision as of 17:11, 26 July 2010
Line 54:		Line 54:

	I think the articles listed under Troubleshooting are really more of a Knowledgebase-y sort than HowTo. They are not (or will not likely be) step by step guides, but more like short "this is what is happening" articles. I was planning on moving them, but wanted to get some input before I did.--[[User:Reactor\|Reactor]] 06:09, 16 August 2009 (UTC)		I think the articles listed under Troubleshooting are really more of a Knowledgebase-y sort than HowTo. They are not (or will not likely be) step by step guides, but more like short "this is what is happening" articles. I was planning on moving them, but wanted to get some input before I did.--[[User:Reactor\|Reactor]] 06:09, 16 August 2009 (UTC)
		+
		+	== External links? ==
		+
		+	Is it OK to add external links to this article? [[User:SharkD\|SharkD]] 17:11, 26 July 2010 (UTC)

← Older revision		Revision as of 17:11, 26 July 2010
Line 1:		Line 1:
		+	====Location of discussions====
	Please hold discussions regarding content of the [[HowTo:Contents]] page here.		Please hold discussions regarding content of the [[HowTo:Contents]] page here.

← Older revision		Revision as of 06:09, 16 August 2009
Line 50:		Line 50:

	:Categories can be nested to form a hierarchical tree. If you edit a category and add a category to it, you make it a child of that category. As content is added to the wiki I have no doubt there will be some restructuring and moving things around. For the time being it's mostly about getting content into the wiki. Thanks for all your efforts so far. [[User:Eddie\|Eddie]] 00:34, 29 December 2007 (UTC)		:Categories can be nested to form a hierarchical tree. If you edit a category and add a category to it, you make it a child of that category. As content is added to the wiki I have no doubt there will be some restructuring and moving things around. For the time being it's mostly about getting content into the wiki. Thanks for all your efforts so far. [[User:Eddie\|Eddie]] 00:34, 29 December 2007 (UTC)
		+
		+
		+	I think the articles listed under Troubleshooting are really more of a Knowledgebase-y sort than HowTo. They are not (or will not likely be) step by step guides, but more like short "this is what is happening" articles. I was planning on moving them, but wanted to get some input before I did.--[[User:Reactor\|Reactor]] 06:09, 16 August 2009 (UTC)

← Older revision		Revision as of 00:34, 29 December 2007
Line 48:		Line 48:
	To think of categories and tutorial ideas, I started thinking of Things I Wish I'd Known Before I Spent A Long Time on. Some of the things I added are probably closer to Knowledgebase items, and other things are covered in the documentation. I guess my question is mostly an organizational one. I find it much easier to process things if I can envision the categories they fit under. Are the categories I added ok? There are lots of ways to sort things, and I was thinking about how tags are used on some photo sites. I can't help but wonder if something relational like that would make it easier to navigate than a list?		To think of categories and tutorial ideas, I started thinking of Things I Wish I'd Known Before I Spent A Long Time on. Some of the things I added are probably closer to Knowledgebase items, and other things are covered in the documentation. I guess my question is mostly an organizational one. I find it much easier to process things if I can envision the categories they fit under. Are the categories I added ok? There are lots of ways to sort things, and I was thinking about how tags are used on some photo sites. I can't help but wonder if something relational like that would make it easier to navigate than a list?
	--[[User:Reactor\|Reactor]] 13:43, 28 December 2007 (UTC)		--[[User:Reactor\|Reactor]] 13:43, 28 December 2007 (UTC)
		+
		+	:Categories can be nested to form a hierarchical tree. If you edit a category and add a category to it, you make it a child of that category. As content is added to the wiki I have no doubt there will be some restructuring and moving things around. For the time being it's mostly about getting content into the wiki. Thanks for all your efforts so far. [[User:Eddie\|Eddie]] 00:34, 29 December 2007 (UTC)

← Older revision		Revision as of 13:43, 28 December 2007
Line 43:		Line 43:
	* I'd also like complicated topics for advanced users, such as how to make realistic clouds, how to generate good textures, how to use SDL to simulate a cellular automaton creating blood stains, etc... '''[[User:Hymyly\|Hymyly]]'''<sup>[[Special:Contributions/Hymyly\|was here]]</sup> ([[User talk:Hymyly\|poke]]) 22:51, 25 November 2007 (UTC)		* I'd also like complicated topics for advanced users, such as how to make realistic clouds, how to generate good textures, how to use SDL to simulate a cellular automaton creating blood stains, etc... '''[[User:Hymyly\|Hymyly]]'''<sup>[[Special:Contributions/Hymyly\|was here]]</sup> ([[User talk:Hymyly\|poke]]) 22:51, 25 November 2007 (UTC)
	*:Oh, and since I'm one of those nerdy maths people i would be happy to have detailed descriptions on how Povray does its job. For example, what a normal map really is, how the texture warps are calculated... In short, everything that would be required to porgramme your own raytracer. (This might belong to the Knowledgebase though...) '''[[User:Hymyly\|Hymyly]]'''<sup>[[Special:Contributions/Hymyly\|was here]]</sup> ([[User talk:Hymyly\|poke]]) 23:09, 25 November 2007 (UTC)		*:Oh, and since I'm one of those nerdy maths people i would be happy to have detailed descriptions on how Povray does its job. For example, what a normal map really is, how the texture warps are calculated... In short, everything that would be required to porgramme your own raytracer. (This might belong to the Knowledgebase though...) '''[[User:Hymyly\|Hymyly]]'''<sup>[[Special:Contributions/Hymyly\|was here]]</sup> ([[User talk:Hymyly\|poke]]) 23:09, 25 November 2007 (UTC)
		+
		+	== The Line Between Knowledgebase and Tutorial ==
		+
		+	To think of categories and tutorial ideas, I started thinking of Things I Wish I'd Known Before I Spent A Long Time on. Some of the things I added are probably closer to Knowledgebase items, and other things are covered in the documentation. I guess my question is mostly an organizational one. I find it much easier to process things if I can envision the categories they fit under. Are the categories I added ok? There are lots of ways to sort things, and I was thinking about how tags are used on some photo sites. I can't help but wonder if something relational like that would make it easier to navigate than a list?
		+	--[[User:Reactor\|Reactor]] 13:43, 28 December 2007 (UTC)

@@ Line 31: / Line 31: @@
 ::I suggest sub sections about coding containing best practices for keeping complex PoV scripts not only readable, but as well manageable, safe and reusable. Like good use of variables, scopes, functions, macros and inline files. The PovDoc is a bit brief on that. It's so important especially for larger projects and for beginners, because the current version of the language allows terribly hard to debug constructions, that look perfectly ok. I volunteer to contribute to that.
 ::[[User:Wound|Wound]] 19:28, 21 November 2007 (UTC)
 * Documentation Errata &ndash; the PovDocs contain a scattering of typos, and probably other mistakes as well. I believe these are corrected reasonably promptly when reported, but compiling outstanding errors in one place would allow them to be fixed in batches rather than piecemeal. Should this one be part of the Knowledge Base?
 ::Yes. I don't see why not. Problems will probably be reported all over the place and regulars will need to consolidate them according to policy guidelines, but that's par for the course with a Wiki. :) [[User:Eddie|Eddie]] 21:21, 17 November 2007 (UTC)
 * How-tos can be divided into technical how-tos, and artistic how-tos. ''Technical:'' How to animate; move an object; use CSG; use macros; use blobs; how to plan a complex scene, &hellip; ''Artistic:'' choosing good colours, choosing the right lighting, using the right camera settings, &hellip;
 * ''Program'' coding style guide - that is, how PoVRay itself is coded. Compiling tips. ? Not so sure about these ones. Probably less vital.
 [[User:Simon Smith|Simon Smith]] 21:08, 17 November 2007 (UTC) (updated, errata idea added)

← Older revision		Revision as of 23:09, 25 November 2007
Line 40:		Line 40:

	* I'd also like complicated topics for advanced users, such as how to make realistic clouds, how to generate good textures, how to use SDL to simulate a cellular automaton creating blood stains, etc... '''[[User:Hymyly\|Hymyly]]'''<sup>[[Special:Contributions/Hymyly\|was here]]</sup> ([[User talk:Hymyly\|poke]]) 22:51, 25 November 2007 (UTC)		* I'd also like complicated topics for advanced users, such as how to make realistic clouds, how to generate good textures, how to use SDL to simulate a cellular automaton creating blood stains, etc... '''[[User:Hymyly\|Hymyly]]'''<sup>[[Special:Contributions/Hymyly\|was here]]</sup> ([[User talk:Hymyly\|poke]]) 22:51, 25 November 2007 (UTC)
		+	*:Oh, and since I'm one of those nerdy maths people i would be happy to have detailed descriptions on how Povray does its job. For example, what a normal map really is, how the texture warps are calculated... In short, everything that would be required to porgramme your own raytracer. (This might belong to the Knowledgebase though...) '''[[User:Hymyly\|Hymyly]]'''<sup>[[Special:Contributions/Hymyly\|was here]]</sup> ([[User talk:Hymyly\|poke]]) 23:09, 25 November 2007 (UTC)

← Older revision		Revision as of 22:51, 25 November 2007
Line 38:		Line 38:

	:POV-Ray coding style and most importantly some documentation on how the existing code is structured will be totally vital during 4.0 rewrite. [[User:Nicolas\|Nicolas]] 03:33, 11 November 2007 (UTC)		:POV-Ray coding style and most importantly some documentation on how the existing code is structured will be totally vital during 4.0 rewrite. [[User:Nicolas\|Nicolas]] 03:33, 11 November 2007 (UTC)
		+
		+	* I'd also like complicated topics for advanced users, such as how to make realistic clouds, how to generate good textures, how to use SDL to simulate a cellular automaton creating blood stains, etc... '''[[User:Hymyly\|Hymyly]]'''<sup>[[Special:Contributions/Hymyly\|was here]]</sup> ([[User talk:Hymyly\|poke]]) 22:51, 25 November 2007 (UTC)

@@ Line 29: / Line 29: @@
 * Common PoVRay coding errors (such as the fact that variable and colour names are case sensitive, the fact that rotatation always works around the origin, and the fact that the order in which you rotate things matters and other things that commonly trip people up.) Debugging tips for tracking these errors down.
 * Coding and scene development tips (such as: when laying out a scene, use simple placeholder objects in distinctive colours to ensure you have the layout right, and only then start using complex objects.)
-::I suggest sub sections about coding containing best practices for keeping complex PoV scripts not only readable, but as well manageable, safe and reusable. Like good use of variables, scopes, functions, macros and inline files. The PovDoc is a bit brief on that. It's so important especially for larger projects and for beginners, because the current version of the language allows terribly hard to debug constructions, that look perfectly ok. I volunteer to contribute to that.--[[User:Wound|Wound]] 19:28, 21 November 2007 (UTC)
+::I suggest sub sections about coding containing best practices for keeping complex PoV scripts not only readable, but as well manageable, safe and reusable. Like good use of variables, scopes, functions, macros and inline files. The PovDoc is a bit brief on that. It's so important especially for larger projects and for beginners, because the current version of the language allows terribly hard to debug constructions, that look perfectly ok. I volunteer to contribute to that.
 * Documentation Errata &ndash; the PovDocs contain a scattering of typos, and probably other mistakes as well. I believe these are corrected reasonably promptly when reported, but compiling outstanding errors in one place would allow them to be fixed in batches rather than piecemeal. Should this one be part of the Knowledge Base?
 ::Yes. I don't see why not. Problems will probably be reported all over the place and regulars will need to consolidate them according to policy guidelines, but that's par for the course with a Wiki. :) [[User:Eddie|Eddie]] 21:21, 17 November 2007 (UTC)