home *** CD-ROM | disk | FTP | other *** search
- (This isn't in any sort of priority ordering. It's just here. --
- denotes things that haven't been started, // things that are half done.)
-
-
- -- Make source-code less of an ugly mess. Not all that stuff belongs in
- main() that finds itself there anyhow. (Sorry, this only happens when
- someone else does it, or I get really bored.)
-
- -- Add internal representation of vectors:
- <vector> to < <real> <real> <real> > [...]
-
- -- Make aat read rayscene .arr-style files.
-
- // Write a decent description of the input-file structure than is in the
- readme file.
-
- There's now something better than there was before. But it could
- be better. I prefer to add a new gimmick than explain the ones I
- already have.
-
- // Add a way to relate two or three variables (IE based on one, constrain
- other so that the two are a point on some circle)
-
- Partially answered need -- With the SIN-type motion, you are able to
- do this. It's still annoying to do, though. (Nearly as annoying as
- using sin.exe that rayshade provides.) Ideally, I would have something
- like:
-
- CONSTRAIN <variable1> TO <variable2> BY CIRCLE <double1> <double2>
- <double3> [ FRAMES <integer> ]
-
- (where the three doubles would be center X, Y and radius so that:
- (variable1-double1)**2+(variable2-double2)**2==(double3)**2)
-
- However, I'm not sure how I'd prefer this to work, exactly.
-
-