| |
It appears from this discussion that methods already exist, its just
that they are not particularly easy to use or accessible.
Whatever solution we choose, we need to think about usability. I am a
developer, and even I dont like having pull things through 5 or 6
different command line programs just to get something done.
So whatever method, additional files formats, using POV or whatever, a
single API library could be built, and then incorporated into existing
UI's so non-developers can use it. If you still want a command line
app, then that could also be built around the same API (there might be
some developer types who want to use makefiles to build animations).
I would like to reach the stage where we can use something like MLCad
to build my design (and group it as MPD's - that is a good technique),
then use *the same tool* to build keyframes, and preview the animation
with OpenGL or DirectX based rendering. I can then hit an export
animation button, which will ask me (much like MAX) what resolution I
want, animation format, colour depth etc, and hit go - and it will
generate what it needs, render the file(might be time to go to work or
bed for a few hours), and when finished, offer me an option to play it
back now, or go back to the editor.
I might be asking too much - and it is early days yet, but by starting
with a wrapper API around the existing tools, and being aware of what
external tools and dependancies there are, it is an acheivable goal.
POV has libraries that can be built against instead of calling its
executable, but I am not so familiar with the other items in the tool
chain.
Cheers,
OrionRobots (I am going to use this for now on to avoid confusion with
the other Orion)
--
http://orionrobots.co.uk
|
|
Message has 1 Reply:
Message is in Reply To:
61 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
