Am 16.06.2021 um 22:17 schrieb Bald Eagle:
> clipka <ano### [at] anonymousorg> wrote:
> 
>> What I'd really like to see is some esteemed members of the community
>> sticking their heads together, looking through the sample scenes, and
>> then deciding, on a case-by-case basis, how to proceed with the scene.
> 
> Certainly could do that, although AFAICR, there were a LOT of scenes in the
> distribution...  IIRC, it's something like > 2600 files.

2579 in v3.7.

But of those,

- 312 are in the `previews` subdirectory, containing nothing but 
pre-rendered images of scenes, and

- 1778 are in the `templates` subdirectory, containing short scene 
snippets, and typically coming in pairs of one text file and one 
rendered image. Plus a few HTML files. So that's a guesstimated ~850 
code snippets.

That leaves us with <500 files making up genuine scenes, organized into 
312 distinct scenes (judging by the number of preview images).


Of course those ~850 code snippets also might warrant getting a review, 
possibly even more so than the sample scenes.


> I'm not sure what the best way to attack this is, but if I were gonna play
> Project Manager, I'd suggest that an outline was made by outputting a directory
> tree, and then people with the artistic and technical eyes for detail could do a
> quick sifting through the rendered scenes to tag the most egregious examples, or
> using knowledge of the code features to pick out the ones that would need
> editing due to deprecated keywords/syntax/code structure or other such things
> that don't necessarily show themselves in the renders.

I've thrown together something using GitHub Wiki on our repo; please 
have a look at https://github.com/POV-Ray/povray/wiki/Scene-Files-Review 
to see whether that might be a useful tool to manage this task, and how 
you think it could be improved.

Post a reply to this message