Those who travel very slowly may yet make far greater progress, provided they keep always to the straight road, than those who, while they run, forsake it. Rene Descartes, Discourse on the Method
Lo so che parlo perche' parlo ma che non persuadero' nessuno; e questa e' disonesta' - ma la rettorica mi costringe a forza a far cio' - o in altre parole "e' pur necessario che se uno ha addentato una perfida sorba la risputi". C. Michelstaedter, La Persuasione e la Rettorica
SOCRATES: Eh! What can be feared when one is doing one’s duty? I know the rage of my enemies. I know all their slanders; but when one only tries to do good to men and when one does not offend heaven, one can fear nothing, neither during life, nor after death. Voltaire, Socrates, ACT II
Render Flam3 Padding XForms is a unique feature that I introduced in the script version 1.3.7 (04 November 2008). It was mainly coded to adjust some quirks related to the Morph animation type so the user can have a better control of the whole morphing process but it can also affect Edge and Sheep ones.
Why I’m talking about it?
I’ve had no feedback about it (I’m not blaming anyone) but the script has some potential that lays underneath the surface and the current preliminary documentation doesn’t help at all (I’ll work on it as soon as possible too).
So I was just guessing: “Had someone tried it at all?”. Who knows…
Four simple video examples can maybe show how Padding XForms changes the animation motion.
I’m glad to find that WordPress had won the Overall Best Open Source CMS Award (found it in my Dashboard today) and it was also named first runner-up in the Best Open Source PHP CMS Category.
WP is a very powerful and flexible platform and it really deserves both Awards for sure!
I was very excited last week to learn that WordPress has been awarded the Overall Best Open Source CMS Award in the 2009 Open Source CMS Awards. This is a landmark for us, as it is the first time we’ve won this award, and it marks a shift in the public perception of WordPress, from blog software to full-featured CMS. No small contest, the Open Source CMS Awards received over 12,000 nominations and more than 23,000 votes across five categories.
… … …
In addition to winning in the Overall Best Open Source CMS category, WordPress was named first runner-up in the Best Open Source PHP CMS category.
The last WordPress versions has introduced the automatic insertion of Generator meta tag in the HTML HEAD.
So what is the problem?
The Generator meta tag reports both the platform name and the software version; an example is “WordPress 2.8.5“. I don’t know why they decided to expose the version number, a so deprecated and potentially harmful information, directly to everybody “eyes” cos this precious information could facilitate a potential hacking tactic based on specific revision problems.
I just don’t believe how much fast the time flows; the last release is approaching to a month ago. I’ve got so few spare time to work on the script: the new code was added during the weeks but I was out of testing possibilities due to some main-job urgencies.
Well, there’s not much hurry: no users response at all! … I’m not complaining, it’s the world we live in …
Beta3 is a quite good step forward to me. I’m quite near to the end of the 1.3.x planned-features-table so maybe I’d be better stay silent and go on with the coding. Who knows! :O
The new 1.4.x will have plenty of new small commodities and it’ll be mainly focused on usability. You know I’m still on the case.
Flam3 installation is now checked using Apophysis “Export renderer” path: we’ll no see the annoying request anymore, plus it can be easily changed just in case you need to use some different Flam3 versions.
Flam3 2.8 Bet4 stagger env var is now fully supported, plus I added the ‘oscope’ to ‘oscilloscope’ conversion and dropped redundant and useless (to Flam3) Flame.Angle tag.
The other small adds can be found in the Changelog.
I’m back to this script again after more than one year.
Why? Well, some update needs surfaced out of genetic-design mailing list during the last days.
First of all I’ve had the confirmation that the ‘twintrian’ Variation is currently banned; when a Flame containing this Variation is uploaded then the designer will have a surprise: the result it’ll be different cos the server silently erase it.
I’ve secondly discovered that ES (ElectricSheep) server limits to 5 the number of Variations per Transforms (XForm); I was completely unaware of it or I forgot the limitation when I firstly coded the script (I really don’t remember).
Stagger env var is another Flam3 2.8 new feature.
It permits to control how the Transforms are interpolated during the animation; every designer can use this feature to customize the animation motions.
It applies to all animation modes created by Flam3: Sheep (Loop), Edge and Morph ones.
Erik Reckase explains it this way: “Setting stagger to 0 means the same as current behaviour. stagger=1 means that each xform will interpolate one at a time instead of simultaneously. stagger=0.5 means that the second xform will start halfway through the interpolation of the first xform, and so on.” and also “Affects simultaneity of xform interpolation during genome interpolation. Represents how ‘separate’ the xforms are interpolated. Set to 1 for each xform to be interpolated individually, fractions control interpolation overlap.”
Setting stagger to 0 is like not having it at all. The Transforms are in both cases interpolated in the old Flam3 2.7.xx way.
I’ve prepared 4 small clips that visually explain the ‘stagger’ env var usage.
The first two clips represent what previously said about stagger=0 and no stagger usage: the result is the same!
![RW (Recursive-Whirls) [Reprised]](http://exper.3drecursions.com/apo/rw_recursive-whirls_reprised_tmb.jpg)
