 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> 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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"jr" <cre### [at] gmailcom> wrote:
> ...
> I modified the 'array?.pov' files, ...
did same for 'scenes/language/fileio/fileio.pov' (attached). would have
"failed" as it had version 3.6 directive. the comments, again, still ought to
be proofread by a native speaker.
re previews directory - does not completely mirror the /scenes/ layout, eg
'previews/language' has no 'arrays' and 'fileio' sub-directories.
regards, jr.
Post a reply to this message
Attachments:
Download 'fileio.pov.txt' (2 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 6/16/2021 9:44 PM, Bald Eagle wrote:
> Are there any guidelines that we're following with regard to file formatting?
> Indentation - tabs, spaces, doesn't matter...
Maybe someone has written a pretty-printer for a language sufficiently
similar to POV-Ray SDL to be useful.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Horvath <mik### [at] gmailcom> wrote:
> On 6/16/2021 9:44 PM, Bald Eagle wrote:
> > Are there any guidelines that we're following with regard to file formatting?
> > Indentation - tabs, spaces, doesn't matter...
>
> Maybe someone has written a pretty-printer for a language sufficiently
> similar to POV-Ray SDL to be useful.
>
>
> Mike
Could the closest be SmallTalk,
http://mvolkmann.github.io/programming/Smalltalk.html
Falling back on something like Lua with more alterations?
https://github.com/jagt/pprint.lua
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"jr" <cre### [at] gmailcom> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > ...
> > I modified the 'array?.pov' files, ...
and did same for 'scenes/language/macros' (attached). also "pass" by the "Scene
Files Review" criteria. however, using alpha.9945627, the rendered images are
not _exactly_ the same, eg 'macro1' preview has a small gap between rightmost
object and right edge, but not when rendered.
regards, jr.
Post a reply to this message
Attachments:
Download 'clipka_macros.zip' (7 KB)
|
|
| |
| |
|
|
|
|
| |
