https://wiki.povray.org/api.php?action=feedcontributions&user=Eddie&feedformat=atomPOV-Wiki - User contributions [en]2024-03-28T09:34:26ZUser contributionsMediaWiki 1.35.1https://wiki.povray.org/content?title=User_talk:StephenS&diff=699User talk:StephenS2009-01-24T14:20:11Z<p>Eddie: Added comment.</p>
<hr />
<div>Should wiki cleanup simply delete content or replace with short sentence of why something was deleted?<br />
<br />
Oh and I like:<br />
Anaglyph (red/cyan) pictures :-)<br />
<br />
:That brings up an issue. I've just emailed Chris about the need to come up with a unified approach to dealing with the spam issue. I'm looking at this article about fighting [http://www.mediawiki.org/wiki/Spam_Filter spam] for some guidance. --[[User:Jholsenback|ash]] 13:15, 24 January 2009 (UTC)<br />
<br />
<br />
::Most wikis use a similar policy, which is to make a post on the discussion (talk) page of the page/content you want to delete. If no-one in the community disagrees within several days then it's okay to go ahead and delete the page/content. [[User:Eddie|Eddie]] 14:20, 24 January 2009 (UTC)</div>Eddiehttps://wiki.povray.org/content?title=Documentation_Talk:Contents&diff=471Documentation Talk:Contents2008-01-20T17:37:36Z<p>Eddie: /* Documentation Content */ Added comment.</p>
<hr />
<div>= Planning needed =<br />
We need a list of the wiki page names that every documentation section will have. There are duplicate names, like in [http://www.povray.org/documentation/view/3.6.1/73/ Tutorial: Isosurface Object], [http://www.povray.org/documentation/view/3.6.1/300/ Reference: Isosurface Object], and [http://www.povray.org/documentation/view/3.6.1/531/ Quick reference: Isosurface]. What should the wiki pages for those be called?<br />
<br />
Making them links also helps see which pages are missing.<br />
<br />
[[User:Nicolas|Nicolas]] 19:21, 5 November 2007 (UTC)<br />
<br />
:I intend to import the official POV-Ray documentation into this namespace at some point; I didn't link to this part of the wiki from the navigation bar because it's not really ready for content. Once the docs are imported then folks will be free to offer changes and updates. Note that this will require that the docs in this portion of the wiki be licensed according to the existing POV license (and thus edits must also be).<br />
<br />
:If there is strong enough interest by folks willing to re-write the docs under a free license such as the Creative Commons ones, for example, then I'll split the doc area accordingly.<br />
:[[User:WikiSysop|WikiSysop]] 21:24, 5 November 2007 (UTC)<br />
:: Damn, I totally forgot about licensing issues. So, either existing docs get imported and we're stuck with the POV doc license, or they get rewritten to make them CC... That would need some discussion on the ng's.<br />
:: [[User:Nicolas|Nicolas]] 21:40, 5 November 2007 (UTC)<br />
<br />
=Documentation Content=<br />
In the absence of movement in this area I have created the skeleton of (most of) the documentation as it is laid out in the official documentation. It won't be much longer before the skeleton is complete.<BR>However, I have also started to add [[Documentation:Contents/POV-Ray Reference/Introduction/Notation and Basic Assumptions|content]] and am asking the administrators to please add some classes to (one of) the wiki stylesheets for use in the documentation. So far I have used:<br />
*"keyword" for styling keywords<br />
*"syntax" for styling syntax items<br />
*"location" for styling paths.<br />
Please feel free to create whatever classes you want according to your standards, I will use them as you specify. The above are just preliminary examples and can easily be changed. Also please set the properties as you see fit. I used properties that mimic the original documentation except in color, so as to differentiate between wiki links and documentation items. Again, these are just examples and can easily be changed.<BR><BR>Once you have created the classes, please document them in the [[Help:Editing_Guidelines|Editing Guidelines]] so that people adding documentation will know how to format the content.<BR><BR>Note that I am rewording the content such that it falls under the license of this wiki but retains the original meaning.<BR>[[User:Eddie|Eddie]] 19:07, 6 January 2008 (UTC)<br />
<br />
:Thanks Chris. (You're fast!). I don't see any color, so I'm not sure if it is what you intended or if my browser has a caching issue. Since I cannot see the stylesheet to troubleshoot I will continue in the hopes that things appear as you want them to. [[User:Eddie|Eddie]] 01:40, 8 January 2008 (UTC)<br />
<br />
::Check the [[Documentation:Contents/POV-Ray Reference/Introduction/Notation and Basic Assumptions|content]] page; at least for me it's displaying the colors (and I'm using a different system than I made the changes on). If you still don't see them, make sure the source for the page shows something like <code>@import "/content?title=MediaWiki:Common.css</code>. [[User:Chrisc|chrisc]] 01:49, 8 January 2008 (UTC)<br />
::One thing I've just noticed is that the wiki doesn't allow non-logged-in users to access common.css. Not sure why, but the net result is that folks reading the wiki without logging in won't get the enhanced CSS markup mentioned above. I'll have to fix this, once I've worked out why it's happening. [[User:Chrisc|chrisc]] 00:51, 9 January 2008 (UTC)<br />
<br />
:::It appears to be a permissions issue. Even though I'm logged in I cannot access that style sheet. I'm not familiar with the inner workings of MediaWiki, but it seems there is a problem distinguishing between letting someone view the style sheet as opposed to edit it. I understand that you don't want us regular users to edit it, but without being able to view it, it can't take effect. Thanks for looking into it. [[User:Eddie|Eddie]] 17:40, 12 January 2008 (UTC)<br />
<br />
::::It should be fixed now. [[User:Chrisc|chrisc]] 16:20, 19 January 2008 (UTC)<br />
<br />
:::::Thanks Chris. Good work. [[User:Eddie|Eddie]] 17:37, 20 January 2008 (UTC)</div>Eddiehttps://wiki.povray.org/content?title=Documentation_Talk:Contents&diff=468Documentation Talk:Contents2008-01-12T17:40:15Z<p>Eddie: /* Documentation Content */ Added comment.</p>
<hr />
<div>= Planning needed =<br />
We need a list of the wiki page names that every documentation section will have. There are duplicate names, like in [http://www.povray.org/documentation/view/3.6.1/73/ Tutorial: Isosurface Object], [http://www.povray.org/documentation/view/3.6.1/300/ Reference: Isosurface Object], and [http://www.povray.org/documentation/view/3.6.1/531/ Quick reference: Isosurface]. What should the wiki pages for those be called?<br />
<br />
Making them links also helps see which pages are missing.<br />
<br />
[[User:Nicolas|Nicolas]] 19:21, 5 November 2007 (UTC)<br />
<br />
:I intend to import the official POV-Ray documentation into this namespace at some point; I didn't link to this part of the wiki from the navigation bar because it's not really ready for content. Once the docs are imported then folks will be free to offer changes and updates. Note that this will require that the docs in this portion of the wiki be licensed according to the existing POV license (and thus edits must also be).<br />
<br />
:If there is strong enough interest by folks willing to re-write the docs under a free license such as the Creative Commons ones, for example, then I'll split the doc area accordingly.<br />
:[[User:WikiSysop|WikiSysop]] 21:24, 5 November 2007 (UTC)<br />
:: Damn, I totally forgot about licensing issues. So, either existing docs get imported and we're stuck with the POV doc license, or they get rewritten to make them CC... That would need some discussion on the ng's.<br />
:: [[User:Nicolas|Nicolas]] 21:40, 5 November 2007 (UTC)<br />
<br />
=Documentation Content=<br />
In the absence of movement in this area I have created the skeleton of (most of) the documentation as it is laid out in the official documentation. It won't be much longer before the skeleton is complete.<BR>However, I have also started to add [[Documentation:Contents/POV-Ray Reference/Introduction/Notation and Basic Assumptions|content]] and am asking the administrators to please add some classes to (one of) the wiki stylesheets for use in the documentation. So far I have used:<br />
*"keyword" for styling keywords<br />
*"syntax" for styling syntax items<br />
*"location" for styling paths.<br />
Please feel free to create whatever classes you want according to your standards, I will use them as you specify. The above are just preliminary examples and can easily be changed. Also please set the properties as you see fit. I used properties that mimic the original documentation except in color, so as to differentiate between wiki links and documentation items. Again, these are just examples and can easily be changed.<BR><BR>Once you have created the classes, please document them in the [[Help:Editing_Guidelines|Editing Guidelines]] so that people adding documentation will know how to format the content.<BR><BR>Note that I am rewording the content such that it falls under the license of this wiki but retains the original meaning.<BR>[[User:Eddie|Eddie]] 19:07, 6 January 2008 (UTC)<br />
<br />
:Thanks Chris. (You're fast!). I don't see any color, so I'm not sure if it is what you intended or if my browser has a caching issue. Since I cannot see the stylesheet to troubleshoot I will continue in the hopes that things appear as you want them to. [[User:Eddie|Eddie]] 01:40, 8 January 2008 (UTC)<br />
<br />
::Check the [[Documentation:Contents/POV-Ray Reference/Introduction/Notation and Basic Assumptions|content]] page; at least for me it's displaying the colors (and I'm using a different system than I made the changes on). If you still don't see them, make sure the source for the page shows something like <code>@import "/content?title=MediaWiki:Common.css</code>. [[User:Chrisc|chrisc]] 01:49, 8 January 2008 (UTC)<br />
::One thing I've just noticed is that the wiki doesn't allow non-logged-in users to access common.css. Not sure why, but the net result is that folks reading the wiki without logging in won't get the enhanced CSS markup mentioned above. I'll have to fix this, once I've worked out why it's happening. [[User:Chrisc|chrisc]] 00:51, 9 January 2008 (UTC)<br />
<br />
:::It appears to be a permissions issue. Even though I'm logged in I cannot access that style sheet. I'm not familiar with the inner workings of MediaWiki, but it seems there is a problem distinguishing between letting someone view the style sheet as opposed to edit it. I understand that you don't want us regular users to edit it, but without being able to view it, it can't take effect. Thanks for looking into it. [[User:Eddie|Eddie]] 17:40, 12 January 2008 (UTC)</div>Eddiehttps://wiki.povray.org/content?title=Documentation_Talk:Contents&diff=448Documentation Talk:Contents2008-01-08T01:40:28Z<p>Eddie: /* Documentation Content */ Thanks Chris.</p>
<hr />
<div>= Planning needed =<br />
We need a list of the wiki page names that every documentation section will have. There are duplicate names, like in [http://www.povray.org/documentation/view/3.6.1/73/ Tutorial: Isosurface Object], [http://www.povray.org/documentation/view/3.6.1/300/ Reference: Isosurface Object], and [http://www.povray.org/documentation/view/3.6.1/531/ Quick reference: Isosurface]. What should the wiki pages for those be called?<br />
<br />
Making them links also helps see which pages are missing.<br />
<br />
[[User:Nicolas|Nicolas]] 19:21, 5 November 2007 (UTC)<br />
<br />
:I intend to import the official POV-Ray documentation into this namespace at some point; I didn't link to this part of the wiki from the navigation bar because it's not really ready for content. Once the docs are imported then folks will be free to offer changes and updates. Note that this will require that the docs in this portion of the wiki be licensed according to the existing POV license (and thus edits must also be).<br />
<br />
:If there is strong enough interest by folks willing to re-write the docs under a free license such as the Creative Commons ones, for example, then I'll split the doc area accordingly.<br />
:[[User:WikiSysop|WikiSysop]] 21:24, 5 November 2007 (UTC)<br />
:: Damn, I totally forgot about licensing issues. So, either existing docs get imported and we're stuck with the POV doc license, or they get rewritten to make them CC... That would need some discussion on the ng's.<br />
:: [[User:Nicolas|Nicolas]] 21:40, 5 November 2007 (UTC)<br />
<br />
=Documentation Content=<br />
In the absence of movement in this area I have created the skeleton of (most of) the documentation as it is laid out in the official documentation. It won't be much longer before the skeleton is complete.<BR>However, I have also started to add [[Documentation:Contents/POV-Ray Reference/Introduction/Notation and Basic Assumptions|content]] and am asking the administrators to please add some classes to (one of) the wiki stylesheets for use in the documentation. So far I have used:<br />
*"keyword" for styling keywords<br />
*"syntax" for styling syntax items<br />
*"location" for styling paths.<br />
Please feel free to create whatever classes you want according to your standards, I will use them as you specify. The above are just preliminary examples and can easily be changed. Also please set the properties as you see fit. I used properties that mimic the original documentation except in color, so as to differentiate between wiki links and documentation items. Again, these are just examples and can easily be changed.<BR><BR>Once you have created the classes, please document them in the [[Help:Editing_Guidelines|Editing Guidelines]] so that people adding documentation will know how to format the content.<BR><BR>Note that I am rewording the content such that it falls under the license of this wiki but retains the original meaning.<BR>[[User:Eddie|Eddie]] 19:07, 6 January 2008 (UTC)<br />
<br />
:Thanks Chris. (You're fast!). I don't see any color, so I'm not sure if it is what you intended or if my browser has a caching issue. Since I cannot see the stylesheet to troubleshoot I will continue in the hopes that things appear as you want them to. [[User:Eddie|Eddie]] 01:40, 8 January 2008 (UTC)</div>Eddiehttps://wiki.povray.org/content?title=Documentation_Talk:Contents&diff=441Documentation Talk:Contents2008-01-06T19:10:06Z<p>Eddie: /* Documentation Content */ Administrator assistance needed.</p>
<hr />
<div>= Planning needed =<br />
We need a list of the wiki page names that every documentation section will have. There are duplicate names, like in [http://www.povray.org/documentation/view/3.6.1/73/ Tutorial: Isosurface Object], [http://www.povray.org/documentation/view/3.6.1/300/ Reference: Isosurface Object], and [http://www.povray.org/documentation/view/3.6.1/531/ Quick reference: Isosurface]. What should the wiki pages for those be called?<br />
<br />
Making them links also helps see which pages are missing.<br />
<br />
[[User:Nicolas|Nicolas]] 19:21, 5 November 2007 (UTC)<br />
<br />
:I intend to import the official POV-Ray documentation into this namespace at some point; I didn't link to this part of the wiki from the navigation bar because it's not really ready for content. Once the docs are imported then folks will be free to offer changes and updates. Note that this will require that the docs in this portion of the wiki be licensed according to the existing POV license (and thus edits must also be).<br />
<br />
:If there is strong enough interest by folks willing to re-write the docs under a free license such as the Creative Commons ones, for example, then I'll split the doc area accordingly.<br />
:[[User:WikiSysop|WikiSysop]] 21:24, 5 November 2007 (UTC)<br />
:: Damn, I totally forgot about licensing issues. So, either existing docs get imported and we're stuck with the POV doc license, or they get rewritten to make them CC... That would need some discussion on the ng's.<br />
:: [[User:Nicolas|Nicolas]] 21:40, 5 November 2007 (UTC)<br />
<br />
=Documentation Content=<br />
In the absence of movement in this area I have created the skeleton of (most of) the documentation as it is laid out in the official documentation. It won't be much longer before the skeleton is complete.<BR>However, I have also started to add [[Documentation:Contents/POV-Ray Reference/Introduction/Notation and Basic Assumptions|content]] and am asking the administrators to please add some classes to (one of) the wiki stylesheets for use in the documentation. So far I have used:<br />
*"keyword" for styling keywords<br />
*"syntax" for styling syntax items<br />
*"location" for styling paths.<br />
Please feel free to create whatever classes you want according to your standards, I will use them as you specify. The above are just preliminary examples and can easily be changed. Also please set the properties as you see fit. I used properties that mimic the original documentation except in color, so as to differentiate between wiki links and documentation items. Again, these are just examples and can easily be changed.<BR><BR>Once you have created the classes, please document them in the [[Help:Editing_Guidelines|Editing Guidelines]] so that people adding documentation will know how to format the content.<BR><BR>Note that I am rewording the content such that it falls under the license of this wiki but retains the original meaning.<BR>[[User:Eddie|Eddie]] 19:07, 6 January 2008 (UTC)</div>Eddiehttps://wiki.povray.org/content?title=Documentation_Talk:Contents&diff=440Documentation Talk:Contents2008-01-06T19:07:09Z<p>Eddie: Administrator assistance needed.</p>
<hr />
<div>= Planning needed =<br />
We need a list of the wiki page names that every documentation section will have. There are duplicate names, like in [http://www.povray.org/documentation/view/3.6.1/73/ Tutorial: Isosurface Object], [http://www.povray.org/documentation/view/3.6.1/300/ Reference: Isosurface Object], and [http://www.povray.org/documentation/view/3.6.1/531/ Quick reference: Isosurface]. What should the wiki pages for those be called?<br />
<br />
Making them links also helps see which pages are missing.<br />
<br />
[[User:Nicolas|Nicolas]] 19:21, 5 November 2007 (UTC)<br />
<br />
:I intend to import the official POV-Ray documentation into this namespace at some point; I didn't link to this part of the wiki from the navigation bar because it's not really ready for content. Once the docs are imported then folks will be free to offer changes and updates. Note that this will require that the docs in this portion of the wiki be licensed according to the existing POV license (and thus edits must also be).<br />
<br />
:If there is strong enough interest by folks willing to re-write the docs under a free license such as the Creative Commons ones, for example, then I'll split the doc area accordingly.<br />
:[[User:WikiSysop|WikiSysop]] 21:24, 5 November 2007 (UTC)<br />
:: Damn, I totally forgot about licensing issues. So, either existing docs get imported and we're stuck with the POV doc license, or they get rewritten to make them CC... That would need some discussion on the ng's.<br />
:: [[User:Nicolas|Nicolas]] 21:40, 5 November 2007 (UTC)<br />
<br />
=Documentation Content=<br />
In the absence of movement in this area I have created the skeleton of (most of) the documentation as it is laid out in the official documentation. It won't be much longer before the skeleton is complete.<BR>However, I have also started to add content and am asking the administrators to please add some classes to (one of) the wiki stylesheets for use in the documentation. So far I have used:<br />
*"keyword" for styling keywords<br />
*"syntax" for styling syntax items<br />
*"location" for styling paths.<br />
Please feel free to create whatever classes you want according to your standards, I will use them as you specify. The above are just preliminary examples and can easily be changed. Also please set the properties as you see fit. I used properties that mimic the original documentation except in color, so as to differentiate between wiki links and documentation items. Again, these are just examples and can easily be changed.<BR><BR>Once you have created the classes, please document them in the [[Help:Editing_Guidelines|Editing Guidelines]] so that people adding documentation will know how to format the content.<BR><BR>Note that I am rewording the content such that it falls under the license of this wiki but retains the original meaning.<BR>[[User:Eddie|Eddie]] 19:07, 6 January 2008 (UTC)</div>Eddiehttps://wiki.povray.org/content?title=Talk:Main_Page&diff=397Talk:Main Page2008-01-04T14:57:39Z<p>Eddie: /* Will there be pages that contain pov-objects or macros? */</p>
<hr />
<div>Please add suggestions that don't fit anywhere else here.<br />
<br />
== Centralized log-in ==<br />
<br />
Personally I don't think it is a big deal. Most browsers remember your passwords if cookies aren't used to remember log-ins. I vote that resources be used in other needed areas than in a centralized login. [[User:Eddie|Eddie]] 16:15, 10 November 2007 (UTC)<br />
<br />
== Other Pages sidebar / links ==<br />
<br />
The Other Pages sidebar seems like it should have a link to the main POV-ray website, or if not there, there should be a link part of the template somewhere that is always available regardless of where you are in the wiki.<br />
<br />
--[[User:Reactor|Reactor]] 11:44, 28 December 2007 (UTC)<br />
:I agree, the "Other Pages" section should have a link to the official POV-Ray Web site. The "Content" section needs a link to [[Documentation:Contents|Documentation]]. [[User:Eddie|Eddie]] 01:13, 30 December 2007 (UTC)<br />
<br />
== File uploads / supported file types ==<br />
<br />
I had no trouble uploading some images, but when I tried to upload a scene file as .pov, I got the error message:<br />
"The file is corrupt or has an incorrect extension. Please check the file and upload again."<br />
<br />
I tried uploading it as a .txt and giving it a .pov destination filename, but no luck. Is there an issue with uploading source at this time?<br />
--[[User:Reactor|Reactor]] 02:04, 31 December 2007 (UTC)<br />
<br />
:By default, a mediawiki will only allow the uploading of image and video files. The administrators will need to configure the wiki to allow the uploading of other file types. [[User:Eddie|Eddie]] 14:54, 4 January 2008 (UTC)<br />
<br />
== Will there be pages that contain pov-objects or macros? ==<br />
<br />
Hi!<br />
Will this wiki hold pages that contain the pov for objects or macros?<br />
For example I tried to create a page Chair_(Model). (Didn't work, btw.)<br />
<br />
Or will that be strictly in the section lib.povray.org?<br />
<br />
I hope this wiki will become as nice just like povray.org in general is. <br />
(And not like so many other wikis develop into. =)<br />
Greetings --[[User:D. Hansen|D. Hansen]] 09:36, 4 January 2008 (UTC)<br />
<br />
:A wiki is a communal effort. This wiki will only ever be as good as the POV-Ray community makes it.<BR>Personally I don't see the need for a page about each object in the library, but you're welcome to create them if you wish. (Avoid special characters and punctuation, for the most part, in page titles.)<BR>I think well documented macros will be very much welcomed in this wiki. I say go for it! :) [[User:Eddie|Eddie]] 14:57, 4 January 2008 (UTC)</div>Eddiehttps://wiki.povray.org/content?title=Talk:Main_Page&diff=396Talk:Main Page2008-01-04T14:54:02Z<p>Eddie: /* File uploads / supported file types */</p>
<hr />
<div>Please add suggestions that don't fit anywhere else here.<br />
<br />
== Centralized log-in ==<br />
<br />
Personally I don't think it is a big deal. Most browsers remember your passwords if cookies aren't used to remember log-ins. I vote that resources be used in other needed areas than in a centralized login. [[User:Eddie|Eddie]] 16:15, 10 November 2007 (UTC)<br />
<br />
== Other Pages sidebar / links ==<br />
<br />
The Other Pages sidebar seems like it should have a link to the main POV-ray website, or if not there, there should be a link part of the template somewhere that is always available regardless of where you are in the wiki.<br />
<br />
--[[User:Reactor|Reactor]] 11:44, 28 December 2007 (UTC)<br />
:I agree, the "Other Pages" section should have a link to the official POV-Ray Web site. The "Content" section needs a link to [[Documentation:Contents|Documentation]]. [[User:Eddie|Eddie]] 01:13, 30 December 2007 (UTC)<br />
<br />
== File uploads / supported file types ==<br />
<br />
I had no trouble uploading some images, but when I tried to upload a scene file as .pov, I got the error message:<br />
"The file is corrupt or has an incorrect extension. Please check the file and upload again."<br />
<br />
I tried uploading it as a .txt and giving it a .pov destination filename, but no luck. Is there an issue with uploading source at this time?<br />
--[[User:Reactor|Reactor]] 02:04, 31 December 2007 (UTC)<br />
<br />
:By default, a mediawiki will only allow the uploading of image and video files. The administrators will need to configure the wiki to allow the uploading of other file types. [[User:Eddie|Eddie]] 14:54, 4 January 2008 (UTC)<br />
<br />
== Will there be pages that contain pov-objects or macros? ==<br />
<br />
Hi!<br />
Will this wiki hold pages that contain the pov for objects or macros?<br />
For example I tried to create a page Chair_(Model). (Didn't work, btw.)<br />
<br />
Or will that be strictly in the section lib.povray.org?<br />
<br />
I hope this wiki will become as nice just like povray.org in general is. <br />
(And not like so many other wikis develop into. =)<br />
Greetings --[[User:D. Hansen|D. Hansen]] 09:36, 4 January 2008 (UTC)</div>Eddiehttps://wiki.povray.org/content?title=Documentation:Contents&diff=346Documentation:Contents2007-12-30T19:37:21Z<p>Eddie: Added categories.</p>
<hr />
<div>The following is a list of the currently-available documentation articles. If you add a new article, please list it here.<br />
<br />
Please also read our '''[[Help:Editing_Guidelines|Editing Guidelines]]''' prior to creating any articles.<br />
<br />
==Completed Articles==<br />
<br />
''(None so far)''<br />
<br />
==Work-in-Progress Articles==<br />
<br />
*[[Documentation:Contents/Introduction to POV-Ray|Introduction to POV-Ray]]<br />
*[[Documentation:Contents/POV-Ray Reference|POV-Ray Reference]]<br />
*[[Documentation:Contents/POV-Ray for Windows|POV-Ray for Windows]]<br />
*[[Documentation:Contents/POV-Ray for Mac OS|POV-Ray for Mac OS]]<br />
*[[Documentation:Contents/POV-Ray for Unix|POV-Ray for Unix]]<br />
<br />
[[Category:Top level]]<br />
[[Category:Documentation]]</div>Eddiehttps://wiki.povray.org/content?title=Talk:Main_Page&diff=329Talk:Main Page2007-12-30T01:13:14Z<p>Eddie: /* Other Pages sidebar / links */ Added comment.</p>
<hr />
<div>Please add suggestions that don't fit anywhere else here.<br />
<br />
== Centralized log-in ==<br />
<br />
Personally I don't think it is a big deal. Most browsers remember your passwords if cookies aren't used to remember log-ins. I vote that resources be used in other needed areas than in a centralized login. [[User:Eddie|Eddie]] 16:15, 10 November 2007 (UTC)<br />
<br />
== Other Pages sidebar / links ==<br />
<br />
The Other Pages sidebar seems like it should have a link to the main POV-ray website, or if not there, there should be a link part of the template somewhere that is always available regardless of where you are in the wiki.<br />
<br />
--[[User:Reactor|Reactor]] 11:44, 28 December 2007 (UTC)<br />
:I agree, the "Other Pages" section should have a link to the official POV-Ray Web site. The "Content" section needs a link to [[Documentation:Contents|Documentation]]. [[User:Eddie|Eddie]] 01:13, 30 December 2007 (UTC)</div>Eddiehttps://wiki.povray.org/content?title=Documentation:Contents&diff=322Documentation:Contents2007-12-30T00:44:04Z<p>Eddie: /* Work-in-Progress Articles */ Starting the documentation skeleton.</p>
<hr />
<div>The following is a list of the currently-available documentation articles. If you add a new article, please list it here.<br />
<br />
Please also read our '''[[Help:Editing_Guidelines|Editing Guidelines]]''' prior to creating any articles.<br />
<br />
==Completed Articles==<br />
<br />
''(None so far)''<br />
<br />
==Work-in-Progress Articles==<br />
<br />
*[[Documentation:Contents/Introduction to POV-Ray|Introduction to POV-Ray]]<br />
*[[Documentation:Contents/POV-Ray Reference|POV-Ray Reference]]<br />
*[[Documentation:Contents/POV-Ray for Windows|POV-Ray for Windows]]<br />
*[[Documentation:Contents/POV-Ray for Mac OS|POV-Ray for Mac OS]]<br />
*[[Documentation:Contents/POV-Ray for Unix|POV-Ray for Unix]]</div>Eddiehttps://wiki.povray.org/content?title=HowTo_Talk:Contents&diff=321HowTo Talk:Contents2007-12-29T00:34:44Z<p>Eddie: /* The Line Between Knowledgebase and Tutorial */</p>
<hr />
<div>Please hold discussions regarding content of the [[HowTo:Contents]] page here.<br />
<br />
When starting a new topic, use the '+' button (on the right of the edit button) rather than edit. '+' starts a new section.<br />
<br />
Also, please sign your contributions. This can be done by adding <nowiki>~~~~</nowiki> (four tildes) at the bottom of your comment.<br />
<br />
[[User:Chrisc|chrisc]] 14:48, 10 November 2007 (UTC)<br />
<br />
:Also, when replying to a comment, add a colon at the beginning of your text. That will indent it, making a threaded conversation like on newsgroups. [[User:Nicolas|Nicolas]] 17:50, 10 November 2007 (UTC)<br />
<br />
::Indeed, and adding multiple colons will form an indented hierarchy. ;) [[User:Eddie|Eddie]] 21:40, 10 November 2007 (UTC)<br />
<br />
====Manually maintained lists====<br />
Personally I think it is a better idea to use Wiki categories than have a page that requires a manually maintained list of other pages. I will try to get some examples in place to show what I mean. I just need to make some time... :)<br />
<br />
[[User:Eddie|Eddie]] 15:55, 10 November 2007 (UTC)<br />
<br />
:Actually, the [[:Category:Help|Help]] category is a good example of what I mentioned above. All pages added to a category automatically appear on the category page which alleviates the need to have a page where you manually maintain a list of other pages. Do the admins agree with this policy?<br />
<br />
:[[User:Eddie|Eddie]] 17:25, 11 November 2007 (UTC)<br />
<br />
::I don't have a problem with it as such, though a contents page would always be around I think (it for example allows us to highlight particular articles, or to otherwise serve as a 'front end' to the namespace).<br />
<br />
::[[User:Chrisc|chrisc]] 17:42, 11 November 2007 (UTC)<br />
<br />
====Basic article suggestions====<br />
* A [[style guide|writing style guide]] for the Wiki. This external example [http://www.riscos.info/index.php/How_to_edit#Brief_Style_Guide Wiki style guide] covers many of the areas we might care about, but there will certainly be some extra PoV-specific ones as well. I think this one may be well worth adding as a high priority, because it will help establish a high level of quality right from the start.<br />
* How to cite &ndash; &quot;''When citing the PoV-Wiki, please include the date and time of the revision to which you refer. This information remains static even when the page is updated, which means others can find the information you were referring to even if it is later edited or vandalised. To provide a link to a specific historical version of a page &hellip;''&quot;<br />
* 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.<br />
* 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.)<br />
::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.<br />
::[[User:Wound|Wound]] 19:28, 21 November 2007 (UTC)<br />
::::I agree, and thought about that when looking at the [[HowTo:Plan_your_scenes]] page. I think it should be a related but separate section from the suggestion above about testing layouts and the like, since that is more of a tip or trick for organizing the scene itself, and not the SDL source. --[[User:Reactor|Reactor]] 13:18, 28 December 2007 (UTC)<br />
* 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?<br />
::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)<br />
* 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;<br />
::That is a way of organizing them I hadn't considered. I had just thought of some categories things could fall under, and added a few links that way. I like the idea of a sections for artistic howtos, or maybe increasing scene realism howtos. --[[User:Reactor|Reactor]] 13:18, 28 December 2007 (UTC)<br />
* ''Program'' coding style guide - that is, how PoVRay itself is coded. Compiling tips. ? Not so sure about these ones. Probably less vital.<br />
[[User:Simon Smith|Simon Smith]] 21:08, 17 November 2007 (UTC) (updated, errata idea added)<br />
<br />
: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)<br />
<br />
* 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)<br />
*: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)<br />
<br />
== The Line Between Knowledgebase and Tutorial ==<br />
<br />
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?<br />
--[[User:Reactor|Reactor]] 13:43, 28 December 2007 (UTC)<br />
<br />
: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)</div>Eddiehttps://wiki.povray.org/content?title=User_talk:Coolhand2&diff=272User talk:Coolhand22007-12-13T01:19:29Z<p>Eddie: Welcome.</p>
<hr />
<div>===Welcome===<br />
Welcome to the POV-Ray Wiki and thanks a ton for all your contributions so far. One small piece of advice, however, and that is "pace yourself". I work on two other Wiki projects and it is easy to burn yourself out by trying to do too much in as short a time as possible. I usually limit myself to about fifteen minutes a session and usually one session a day. That way it doesn't feel like working on the Wiki is a chore. Thanks again. [[User:Eddie|Eddie]] 01:19, 13 December 2007 (UTC)</div>Eddiehttps://wiki.povray.org/content?title=User_talk:Snaily&diff=227User talk:Snaily2007-12-08T16:05:04Z<p>Eddie: Welcome.</p>
<hr />
<div>===Welcome===<br />
Welcome to the POV-Ray Wiki and thanks for your great contribution on animation. :) [[User:Eddie|Eddie]] 16:05, 8 December 2007 (UTC)</div>Eddiehttps://wiki.povray.org/content?title=HowTo_Talk:Contents&diff=204HowTo Talk:Contents2007-11-17T21:21:23Z<p>Eddie: /* Basic article suggestions */ Added comment.</p>
<hr />
<div>Please hold discussions regarding content of the [[HowTo:Contents]] page here.<br />
<br />
When starting a new topic, use the '+' button (on the right of the edit button) rather than edit. '+' starts a new section.<br />
<br />
Also, please sign your contributions. This can be done by adding <nowiki>~~~~</nowiki> (four tildes) at the bottom of your comment.<br />
<br />
[[User:Chrisc|chrisc]] 14:48, 10 November 2007 (UTC)<br />
<br />
:Also, when replying to a comment, add a colon at the beginning of your text. That will indent it, making a threaded conversation like on newsgroups. [[User:Nicolas|Nicolas]] 17:50, 10 November 2007 (UTC)<br />
<br />
::Indeed, and adding multiple colons will form an indented hierarchy. ;) [[User:Eddie|Eddie]] 21:40, 10 November 2007 (UTC)<br />
<br />
====Manually maintained lists====<br />
Personally I think it is a better idea to use Wiki categories than have a page that requires a manually maintained list of other pages. I will try to get some examples in place to show what I mean. I just need to make some time... :)<br />
<br />
[[User:Eddie|Eddie]] 15:55, 10 November 2007 (UTC)<br />
<br />
:Actually, the [[:Category:Help|Help]] category is a good example of what I mentioned above. All pages added to a category automatically appear on the category page which alleviates the need to have a page where you manually maintain a list of other pages. Do the admins agree with this policy?<br />
<br />
:[[User:Eddie|Eddie]] 17:25, 11 November 2007 (UTC)<br />
<br />
::I don't have a problem with it as such, though a contents page would always be around I think (it for example allows us to highlight particular articles, or to otherwise serve as a 'front end' to the namespace).<br />
<br />
::[[User:Chrisc|chrisc]] 17:42, 11 November 2007 (UTC)<br />
<br />
====Basic article suggestions====<br />
* A [[style guide|writing style guide]] for the Wiki. This external example [http://www.riscos.info/index.php/How_to_edit#Brief_Style_Guide Wiki style guide] covers many of the areas we might care about, but there will certainly be some extra PoV-specific ones as well. I think this one may be well worth adding as a high priority, because it will help establish a high level of quality right from the start.<br />
* How to cite &ndash; &quot;''When citing the PoV-Wiki, please include the date and time of the revision to which you refer. This information remains static even when the page is updated, which means others can find the information you were referring to even if it is later edited or vandalised. To provide a link to a specific historical version of a page &hellip;''&quot;<br />
* 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.<br />
* 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.)<br />
* 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?<br />
::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)<br />
* 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;<br />
* ''Program'' coding style guide - that is, how PoVRay itself is coded. Compiling tips. ? Not so sure about these ones. Probably less vital.<br />
[[User:Simon Smith|Simon Smith]] 21:08, 17 November 2007 (UTC) (updated, errata idea added)<br />
<br />
: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)</div>Eddiehttps://wiki.povray.org/content?title=Template_talk:Stub&diff=191Template talk:Stub2007-11-11T17:29:27Z<p>Eddie: Added to the template documentation.</p>
<hr />
<div>===Reason for this template===<br />
This template performs two functions:<br />
*It places a consistent message on "stub" pages/articles.<br />
*It automatically places the page/article in the [[:Category:Stubs|Stubs]] category so that all stubs can be easily located by people who want to expand them.<br />
<br />
===Using this template===<br />
To use this template in an article, simply put the text <nowiki>{{Stub}}</nowiki> at the top of the article.</div>Eddiehttps://wiki.povray.org/content?title=HowTo_Talk:Contents&diff=190HowTo Talk:Contents2007-11-11T17:25:29Z<p>Eddie: Added comment and some formatting.</p>
<hr />
<div>Please hold discussions regarding content of the [[HowTo:Contents]] page here.<br />
<br />
When starting a new topic, use the '+' button (on the right of the edit button) rather than edit. '+' starts a new section.<br />
<br />
Also, please sign your contributions. This can be done by adding <nowiki>~~~~</nowiki> (four tildes) at the bottom of your comment.<br />
<br />
[[User:Chrisc|chrisc]] 14:48, 10 November 2007 (UTC)<br />
<br />
:Also, when replying to a comment, add a colon at the beginning of your text. That will indent it, making a threaded conversation like on newsgroups. [[User:Nicolas|Nicolas]] 17:50, 10 November 2007 (UTC)<br />
<br />
::Indeed, and adding multiple colons will form an indented hierarchy. ;) [[User:Eddie|Eddie]] 21:40, 10 November 2007 (UTC)<br />
<br />
====Manually maintained lists====<br />
Personally I think it is a better idea to use Wiki categories than have a page that requires a manually maintained list of other pages. I will try to get some examples in place to show what I mean. I just need to make some time... :) [[User:Eddie|Eddie]] 15:55, 10 November 2007 (UTC)<br />
<br />
:Actually, the [[:Category:Help|Help]] category is a good example of what I mentioned above. All pages added to a category automatically appear on the category page which alleviates the need to have a page where you manually maintain a list of other pages. Do the admins agree with this policy? [[User:Eddie|Eddie]] 17:25, 11 November 2007 (UTC)<br />
<br />
====Basic article suggestions====<br />
* A [[style guide|writing style guide]] for the Wiki. This external example [http://www.riscos.info/index.php/How_to_edit#Brief_Style_Guide Wiki style guide] covers many of the areas we might care about, but there will certainly be some extra PoV-specific ones as well. I think this one may be well worth adding as a high priority, because it will help establish a high level of quality right from the start.<br />
* How to cite &ndash; &quot;''When citing the PoV-Wiki, please include the date and time of the revision to which you refer. This information remains static even when the page is updated, which means others can find the information you were referring to even if it is later edited or vandalised. To provide a link to a specific historical version of a page &hellip;''&quot;<br />
* 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.<br />
* 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.)<br />
* 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;<br />
* ''Program'' coding style guide - that is, how PoVRay itself is coded. Compiling tips. ? Not so sure about these ones. Probably less vital.<br />
[[User:Simon Smith|Simon Smith]] 22:59, 10 November 2007 (UTC)<br />
: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)</div>Eddiehttps://wiki.povray.org/content?title=Template_talk:Stub&diff=189Template talk:Stub2007-11-11T16:48:41Z<p>Eddie: Documented template.</p>
<hr />
<div>===Reason for this template===<br />
This template performs two functions:<br />
*It places a consistent message on "stub" pages/articles.<br />
*It automatically places the page/article in the [[:Category:Stubs|Stubs]] category so that all stubs can be easily located by people who want to expand them.</div>Eddiehttps://wiki.povray.org/content?title=Knowledgebase:Windows_Vista&diff=188Knowledgebase:Windows Vista2007-11-11T16:44:50Z<p>Eddie: Added "Stub" template.</p>
<hr />
<div>{{Stub}}<br />
<br />
This page summarizes some of the known issues in using POV-Ray with Windows Vista&reg;.<br />
<br />
[[Category:{{NAMESPACE}}|Vista]]</div>Eddiehttps://wiki.povray.org/content?title=Category:Stubs&diff=187Category:Stubs2007-11-11T16:42:17Z<p>Eddie: Added description.</p>
<hr />
<div>Articles in this category are placeholders or very brief articles that need more content. Please help enhance the POV-Wiki by adding quality content.</div>Eddiehttps://wiki.povray.org/content?title=Template:Stub&diff=186Template:Stub2007-11-11T16:40:43Z<p>Eddie: Added global template.</p>
<hr />
<div><div align="center"><div align="left" style="width:50%; padding: .5em 0; padding-left: 1em; background-color:#E2EDFE; border:2px dotted #282FDD;">[[Image:Stub.gif|left]]<i>This article is a <b>stub</b>.<BR>Please help enhance the POV-Wiki by expanding it.</i></div></div><br />
[[Category:Stubs]]</div>Eddiehttps://wiki.povray.org/content?title=File:Stub.gif&diff=185File:Stub.gif2007-11-11T16:39:04Z<p>Eddie: </p>
<hr />
<div></div>Eddiehttps://wiki.povray.org/content?title=Category:KB&diff=184Category:KB2007-11-11T16:29:58Z<p>Eddie: Added redirect.</p>
<hr />
<div>#REDIRECT [[:Category:Knowledgebase]]</div>Eddiehttps://wiki.povray.org/content?title=HowTo_Talk:Contents&diff=161HowTo Talk:Contents2007-11-10T21:40:27Z<p>Eddie: Added comment.</p>
<hr />
<div>Please hold discussions regarding content of the [[HowTo:Contents]] page here.<br />
<br />
When starting a new topic, use the '+' button (on the right of the edit button) rather than edit. '+' starts a new section.<br />
<br />
Also, please sign your contributions. This can be done by adding <nowiki>~~~~</nowiki> (four tildes) at the bottom of your comment.<br />
<br />
[[User:Chrisc|chrisc]] 14:48, 10 November 2007 (UTC)<br />
<br />
:Personally I think it is a better idea to use Wiki categories than have a page that requires a manually maintained list of other pages. I will try to get some examples in place to show what I mean. I just need to make some time... :) [[User:Eddie|Eddie]] 15:55, 10 November 2007 (UTC)<br />
<br />
:Also, when replying to a comment, add a colon at the beginning of your text. That will indent it, making a threaded conversation like on newsgroups. [[User:Nicolas|Nicolas]] 17:50, 10 November 2007 (UTC)<br />
<br />
::Indeed, and adding multiple colons will form an indented hierarchy. ;) [[User:Eddie|Eddie]] 21:40, 10 November 2007 (UTC)</div>Eddiehttps://wiki.povray.org/content?title=Talk:Main_Page&diff=157Talk:Main Page2007-11-10T16:15:51Z<p>Eddie: New section: Centralized log-in</p>
<hr />
<div>Please add suggestions that don't fit anywhere else here.<br />
<br />
== Centralized log-in ==<br />
<br />
Personally I don't think it is a big deal. Most browsers remember your passwords if cookies aren't used to remember log-ins. I vote that resources be used in other needed areas than in a centralized login. [[User:Eddie|Eddie]] 16:15, 10 November 2007 (UTC)</div>Eddiehttps://wiki.povray.org/content?title=User:Eddie&diff=156User:Eddie2007-11-10T15:56:12Z<p>Eddie: Stub. :)</p>
<hr />
<div>POV-Ray enthusiast.</div>Eddiehttps://wiki.povray.org/content?title=HowTo_Talk:Contents&diff=155HowTo Talk:Contents2007-11-10T15:55:46Z<p>Eddie: Added comment.</p>
<hr />
<div>Please hold discussions regarding content of the [[HowTo:Contents]] page here.<br />
<br />
When starting a new topic, use the '+' button (on the right of the edit button) rather than edit. '+' starts a new section.<br />
<br />
Also, please sign your contributions. This can be done by adding <nowiki>~~~~</nowiki> (four tildes) at the bottom of your comment.<br />
<br />
[[User:Chrisc|chrisc]] 14:48, 10 November 2007 (UTC)<br />
<br />
:Personally I think it is a better idea to use Wiki categories than have a page that requires a manually maintained list of other pages. I will try to get some examples in place to show what I mean. I just need to make some time... :) [[User:Eddie|Eddie]] 15:55, 10 November 2007 (UTC)</div>Eddie