Embedding a random value (multiple?) into the CFDG file

[Ebola_One]

This would mainly be to display the CFDG file as the author intended, but is an optional addition to the file.

Something like:

Code: Select all

randomvalues RYV, RKV, RMK

startshape GO

rule GO {
.
.
}

And if the "randomvalues" doesn't exisit at the beginning of the file, simply use a random value made on the spot (the one displayed in the main editor window)

I can also see something like this being useful for a screen saver application - if you list several random values within a single CFDG file, it broadens the available examples of that file.

Think of it a kind of "quality control" that's pre-set by the author, and a way of saving favorite renders.

[PatternGuru]

Very good idea indeed. Especially in things like the possible future screen saver option and of course for a "self rendering" variation of the online galary maybe? Then the auto-submit option could simply put the current variation code into the file at submission time if there isn't one in the file already so the exact image you just rendered (and is still on screen) would be the example images shown on the galery if you don't override that in the file itself. Cool. Hope to see it happen.

[PatternGuru]

Not too sure about your suggestion for a name though. Since that's the name mentioned in the FAQ forum, I'd go with something like variation, variations, variant or variants instead of randomvalues.

[Ebola_One]

Not too sure about your suggestion for a name though. Since that's the name mentioned in the FAQ forum, I'd go with something like variation, variations, variant or variants instead of randomvalues.

Yeah, for sure, it was just an example

[robo git]

John/Mark/Chris: Any thoughts? This would probably be relatively simple to implement in the IDE.

[MtnViewJohn]

Yeah, that should be pretty easy. Probably we would have a button labeled 'Next', to the right of the variant control that cycles to the next embedded variant and renders. Seems like a good idea.

Now that there is a border width attribute it might be nice to set that in the cfdg file too. Animation attributes too. Rather than cluttering the top-level namespace (such as there is a namespace) with new tokens I would define a property container syntax with key/value pairs:

Code: Select all

properties {
    variants { uux aef ttd }
    border { 1.0 }  // variable borders too big
    animation-codec { H.264 }
    crop { true }
} 

Unrecognixed keys would be ignored.