Frame System

[Miguel Angel Gómez Márquez]

---
No, that is far to inflexible
---
Why? i'd ask in this case an example as an answer.


----
1) There may not allways be a simple function or interpolation. Imagine a
box that follows a sinus wave or an animation that is calculated in discrete
steps (explosions, flow simulation etc.)
----
And if there are not simple or easy what happens?
I didn't understand that comment, i don't have problems with math nor
numerical methods.
and if we use "external" functions this will let to implement several
functions and keep adding more functions without modifying the program code.

---
2) You modified my example scene to make it easier for you ;-)
----
Hmmm i didn't, thats how it would work, and it was going to be
easier to understand, i am not the kind of people who hiddes the
already found mistakes, if i were like that i would be only wasting
my time and speaking non sense.

I modify the example (and very little btw) because, i got to be a little bit
stubborn with this
special point.

The clock (for the frame system) should not be used inside the code.
The clock should only be used as frame indicator.



---
I deliberately inserted the animated inverse flag and choose a scene where
an object (the csg) and a child object are both animated. Following your
example, the whole csg has to be exported twice with all child objects.
----
I didn't understood your inverse flag setting.
and please don't use clock parameters, clock
should only be used as global.

You don't need to declare each parameter, only
the "first child" or the child of your convenience.
example for this case:
With those comments you are impliying that those elements are to be
animated.
You don't need to declare inner levels.
//start csg
csg {
  box {}
  box {}
}
// end csg
csg {
 box {}
 box {}
}

---
My present approach to export non-povray properties is to serialize these
attributes with special comments.  After all discussion I tend to do that
with all animation objects and scripts. Example of an animated scene with a
script where the rotation is calculated in discrete steps (the script will
be called once for each frame), and where corner 1 of the cube follows a
spline.
---
I thought i explained this earlier, or arent //PMBox1Begin special comments?

---
You still have all information for the animation for later use.
---
:S
In my approach you can have the numbers before the render if you like
remmember the animation parser before sending it to the serializer, (so you
can preview them in opengl, before rendering if you like to implement it)
And your approach is wrong  because:
Say you stored all the animation in memory (instead of calculating for the
frame you are working on) if you increase from 10 frames to 20 (to smooth
the animation)
Your data in memory is totally useless
Suppose you want to start asynchronaly an object, that start in frame 3
instead of 0.
You will have to recalculate them all.

----
When the result satisfies you, you can render the scene without to
recalculate the animation.
----
So, in my explanation.
I feel like i am not making myself clear.
I already give an example about how to do that, without modifying the code.
// end csg
csg {
 box {}
 box {}
}

---
My present approach to export non-povray properties is to serialize these
attributes with special comments.  After all discussion I tend to do that
with all animation objects and scripts. Example of an animated scene with a
script where the rotation is calculated in discrete steps (the script will
be called once for each frame), and where corner 1 of the cube follows a
spline.
---
I thought i explained this earlier, or arent //PMBox1Begin special comments?

---
You still have all information for the animation for later use.
---
:S
In my approach you can have the numbers before the render if you like
remmember the animation parser before sending it to the serializer, (so you
can preview them in opengl, before rendering if you like to implement it)
And your approach is wrong  because:
Say you stored all the animation in memory (instead of calculating for the
frame you are working on) if you increase from 10 frames to 20 (to smooth
the animation)
Your data in memory is totally useless
Suppose you want to start asynchronaly an object, that start in frame 3
instead of 0.
You will have to recalculate them all.

----
When the result satisfies you, you can render the scene without to
recalculate the animation.
----
So, in my explanation. (if you like, its just matter of saving the
calculated tweend objects)
but you'd fall in the problems i posted before.

I feel like i am not explaining myself.


Buen día
Att. Miguel A. Gómez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kpovmodeler-devel/attachments/20061005/2e1d980c/attachment.html