What's the plan?|
as of April, 2005:
Create the gestural files. I already have a huge backlog of old Vapor paint control files. I'm also making up new ones
or revising the old ones nearly every day, as seen in The Daily Vapor.
Eventually, I'll have longer, more detailed animations to work with, but I need to get up to speed! These could be
based on the subjects mentioned in the "art" page, or other animations that have been brewing
I've started printing out proofs and test prints. Soon, a good quality printer will be here, and I intend to
print the smaller images myself, and farm out the big ones. The small images might be able to go up to a
bleeding 13x44 inches, but I'm not sure.
A secondary line of assets is to be made from these control files: postcards, panoramas, posters, flip books,
computer background screens, DVD greeting cards, and computer-only things like Quicktime VR, VRML worlds,
Flash animations, etc.
Since any image could be created in a big variety of aspects, sizes, or "temporal content", there needs to be
a mix of both preprinted work and customized prints.
Some editions should be earmarked to be 1 of 1 and "retired" for the particular format produced. Other editions
may be produced for the purpose of being manipulated further with conventional art materials into
polyhedra, pop-ups, topological or temporal maps, or other more sculptural forms.
R & D will continue:
- the Amiga based modeler will get occasional but rare enhancements, and new AREXX macros will continue
to be developed. This has already resulted in some interesting new capabilities.
- the "C" renderer will continue to expand its capabilities. There are some old ideas being tested and
written in right now, such as all-vector rendering (direct to Postscript, SVG, Flash, and other vector-based
standards) and native audio rendering.
- the new Modeler will continue to be developed, taking advantages in the 15+ years having elapsed since
the original modeler was conceived. Many of the very useful ideas will be continued, with a few others
added that are impractical to put into the old modeler at this point. The new modeler should be less cumbersome
with dealing with images, render while drawing, and know about drawing tablet parameters. The current version
is being coded in Objective C - I'd use Java if there were a nice way to get the tablet data on a Mac from Java
(Windows folks can use Wintab.dll).
- I'm working on a new image format, which is really like a 3D shader language for 2D, so I can create
images algorithmically at arbitrary resolution. I'm hoping to make it a library so I can plug it into