OK. After some delays, please find the latest beta of the granite macro.

You will find that a number of fundamental changes have been made: 
changes to array names and internal parameter names; corrections of 
remaining errors; aligning the granite textures to real world 
dimensions; changing some arrays to mixed arrays. I probably forgot a 
few but they may not influence your understanding/use.

Of course, the two developed granite data include files to date (pending 
future ones) have also been corrected.

A first draft of the documentation is included here in pdf-format. It 
concerns principally the macro structure itself which is rather complex 
I confess. The documentation will be expanded later on. I want to ask 
you to critically review the structure and text of the docs on 
comprehension and language. Native speakers, sharpen you pens! I 
consider this to be a very essential exercise, so please do not spare me 
nor my text. In a final stage I may also provide a html version.

Some examples are posted in p.b.i.

-- 
Thomas

Post a reply to this message

Attachments:
Download 'granite_21_beta_1.6.mcr.txt' (21 KB) Download 'granite_21 - documentation.pdf' (259 KB) Download 'dakotaredgranite.inc.txt' (4 KB) Download 'saintandregreengranite.inc.txt' (4 KB)

Thomas de Groot <tho### [at] degrootorg> wrote:
> I want to ask
> you to critically review the structure and text of the docs on
> comprehension and language. Native speakers, sharpen you pens! I
> consider this to be a very essential exercise, so please do not spare me
> nor my text.

Here ya go:

Post a reply to this message

Attachments:
Download 'betadocumentationcritique - bw.pdf' (331 KB)

Op 22/06/2021 om 21:18 schreef Bald Eagle:
> Thomas de Groot <tho### [at] degrootorg> wrote:
>> I want to ask
>> you to critically review the structure and text of the docs on
>> comprehension and language. Native speakers, sharpen you pens! I
>> consider this to be a very essential exercise, so please do not spare me
>> nor my text.
> 
> Here ya go:
> 

Perfect Bill and thanks! That is what I mean. :-)

-- 
Thomas

Post a reply to this message

Op 22-6-2021 om 21:18 schreef Bald Eagle:
> Here ya go:
> 

I started transposing your corrections to the docs. They make all the 
difference indeed. Writing correct English is a real challenge; 
notwithstanding the opinion of some. ;-)

I was aware of the lack of some definitions and better explanations but 
got lazy of course; I knew it would be thrown back at me later. ;-) 
Additional work to do here.

A couple of answers to your comments I can already make here:

"Now, you have
scale M_scale
rotate M_rotat
translate M_trans
Are these really necessary in the macro? "

They are not really essential for the macro indeed and could be left 
outside. However, I decided to keep them /inside/ the macro for a 
psychological reason: this way, the user will remain more aware of the 
changes he /forces/ on the granite.

"I think that an annotated diagram of the final texture should accompany 
this document, and perhaps
some specialized renders of the array results – showing how the texture 
elements correspond to the
array entries, especially the mask. "

Yes, I was thinking on the same lines here.

"Line 26: Why not just expand “Typ” to “Type”? "

Yes, of course.

"Line 391 – spelling “aligne” → align "

<grin> nice typo. Shows my French background trying to struggle to the 
surface when I am not looking. :-)

-- 
Thomas

Post a reply to this message

Bill, that little scene file you wrote (color_map gradient scene) is 
going to be very useful! I post here an improved version together with 
an image output. I think that, changed into a macro, it could be very 
helpful for writing new granite maps.

-- 
Thomas

Post a reply to this message

Attachments:
Download 'be_colormapgradient.png' (29 KB) Download 'utf-8' (4 KB)

Preview of image 'be_colormapgradient.png'

This should do the trick.

-- 
Thomas

Post a reply to this message

Attachments:
Download 'utf-8' (3 KB)