 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> If you're talking about the list of scenes, that's just the miracle of
> Unix command-line tools (on a Windows machine no less) to get a raw
> list, and a text editor with good find/replace to bring it into the
> GitHub Markdown format.
And lots and lots of practice and experience.
> The real work only starts from there: What do we even _do_ with this list?
Oh how right you are.
> Me, personally, I would LOVE to see consistent formatting throughout all
> the sample scenes. Preferably MY own favorite style of course. (The
> style used in the "Insert Menu" sample snippets, for instance, is an
> abomination. No offense, Friedrich.)
Yes, I've been through those - but on the flip-side, he got them done enough to
work reliably and ship out over all these years. Maybe there is some unix
scripting that could address that aspect to some degree...?
> One thing really worth investigating though is whether there are any
> lowercase variable names in those scenes - because those are very
> strongly non-recommended. William Pokorny might be able to help with
> that: If I understand correctly he has a version of the parser that
> warns on lowercase variables.
Very good point.
> Also, while it might be argued to keep the file formatting intact to
> reflect the wide variety in that respect, I'd really love to see at
> least the file headers standardized. Again, my personal opinion.
Following up on the above idea, maybe there's a tag in the comments that could
be used to help introduce some automation to the process? So, just as an
off-the-top-of-the-head example, html has <header> <\header> and a script could
just replace everything in between.
> > Many files say something to the effect of
> > "Persistence Of Vision raytracer version 3.5 sample file."
> >
> > but then there is #version 3.7;
> >
> > update to make consistent?
>
> Another point worth discussing: Should it be the version in which the
> sample file was first introduced, the one in which it was last updated,
> the one that it now requires as minimum, or the one it will ship with
> (i.e. v3.8)?
Depending on the scene, put a file history?
/*
v 3.5
updated 1/2/03 by Joe Schmo for v 3.6
update 04/19/2018 by John Q. Public for v 3.7
min version required for proper usage: v 3.7
This file provided as part of the v 3.8 distribution package
*/
> > scenes/objects/ttf1.pov is ... heinous?
> > I'm guessing part of this project is to make them ... better?
>
> I would think so.
See attached.
> Oh, by the way: That particular scene should be called out for showing
> an outdated version number in the output image.
Yes,. It uses:
concat("Version:", str(version, 0, 1))
which is the version set in the scene, not a saved variable of the running
version.
Maybe it should display both?
> Team up and discuss. This is (or should be) as much your software
> package as it is mine.
Right-o.
Post a reply to this message
Attachments:
Download 'ttf1.png' (615 KB)
Preview of image 'ttf1.png'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ah crap.
I forgot to mention the warnings:
File 'ttf1.pov' line 26: Possible Parse Error: Text may not be displayed as
expected. Please refer to the user manual regarding changes in POV-Ray v3.8 and
later.
File 'ttf1.pov' line 39: Possible Parse Error: Text may not be displayed as
expected. Please refer to the user manual regarding changes in POV-Ray v3.8 and
later.
I don't see in the User Manual (wiki) where this is addressed.
https://wiki.povray.org/content/Reference:Text
What should I do to get rid of these?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2021-06-17 6:41 AM (-4), Bald Eagle wrote:
>
> File 'ttf1.pov' line 26: Possible Parse Error: Text may not be displayed as
> expected. Please refer to the user manual regarding changes in POV-Ray v3.8 and
> later.
> File 'ttf1.pov' line 39: Possible Parse Error: Text may not be displayed as
> expected. Please refer to the user manual regarding changes in POV-Ray v3.8 and
> later.
These warnings do not appear with my rolled back version
(3.8.0-alpha.9945627).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 17.06.2021 um 12:41 schrieb Bald Eagle:
> File 'ttf1.pov' line 26: Possible Parse Error: Text may not be displayed as
> expected. Please refer to the user manual regarding changes in POV-Ray v3.8 and
> later.
> File 'ttf1.pov' line 39: Possible Parse Error: Text may not be displayed as
> expected. Please refer to the user manual regarding changes in POV-Ray v3.8 and
> later.
>
>
> I don't see in the User Manual (wiki) where this is addressed.
> https://wiki.povray.org/content/Reference:Text
>
> What should I do to get rid of these?
Those warnings are... um... special. They should be going away as soon
as we have the first v3.8.0-beta.
(Technical background: Those warnings are related to my work to clean up
character encoding stuff in the parser and beyond. It has been decided
to back out those changes in order to not break backward compatibility,
while also not spending ages to try to somehow mimick the old behavior
in legacy scenes.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> Those warnings are... um... special. They should be going away as soon
> as we have the first v3.8.0-beta.
Very good.
I suspected, based on past mention by Dick Balaska, but didn't want to make any
unfounded assumptions.
So I will ignore THAT warning.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
clipka <ano### [at] anonymousorg> wrote:
> ...
> That leaves us with <500 files making up genuine scenes, organized into
> 312 distinct scenes (judging by the number of preview images).
> ...
> 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.
had a look at this and went through the check list for the
'scenes/language/arrays/array?.pov' files. pass. have not dared (nor wanted)
to click on anything on yr page.
two observations: there ought to be some SDL coding style guidelines (because
'array?.pov' could do with re-formatting, imo), and the comments, while good,
ought to be vetted by a native speaker (eg 'array2.pov'. I'd write "... and
initialized with one digit floats. This digits are displayed..." as "... and
initialised with single digit floats. These digits...")
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2021-06-16 9:44 PM (-4), Bald Eagle wrote:
>
> scenes/objects/ttf1.pov is ... heinous?
scenes/objects/ttf1.pov also is licensed under Creative Commons
Attribution, but does not name anyone to which to attribute. How many
other files are like this?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2021-06-17 3:16 AM (-4), clipka wrote:
>
> The font that really got under my skin was cyrvetic.ttf. But if we stick
> to ASCII, the fonts are useful. Though arguably not the prettiest.
Cyrvetic is what I normally use if I don't need anything more than
ASCII. Admittedly, as a native anglophone, I'm privileged in this respect.
One thing rarely mentioned about Crystal is that it is monospace--which
makes it useful for rendering source code and ledger tables, not typical
ray tracing subjects.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"jr" <cre### [at] gmailcom> wrote:
> clipka <ano### [at] anonymousorg> wrote:
> > ...
> > 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.
>
> had a look at this and went through the check list for the
> 'scenes/language/arrays/array?.pov' files. pass. have not dared (nor wanted)
> to click on anything on yr page.
>
> two observations: there ought to be some SDL coding style guidelines (because
> 'array?.pov' could do with re-formatting, imo), and the comments, while good,
> ought to be vetted by a native speaker (eg 'array2.pov'. I'd write "... and
> initialized with one digit floats. This digits are displayed..." as "... and
> initialised with single digit floats. These digits...")
I modified the 'array?.pov' files, correcting typos and reformatting the code
with more (and consistent) whitespace. attached as zip :-), in case you find
use for them.
regards, jr.
Post a reply to this message
Attachments:
Download 'clipka_arraypov.zip' (4 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Op 17/06/2021 om 20:05 schreef jr:
> two observations: there ought to be some SDL coding style guidelines (because
> 'array?.pov' could do with re-formatting, imo), and the comments, while good,
> ought to be vetted by a native speaker
>
I am very much in favour of this indeed! Especially the second.
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
