I'm frequently in a similar position.  Often my scenes develope as I work on
them and they rarely end up like what I first envisioned.  This means when I
go back to change something in the code it is often much different than the
neat, "orderly" script that I first intended to create.  I know there is no
excuse for messy coding but when I get seriously get the creative juices
flowing neatness somehow falls to the back burner ;)

I too, would find something along those lines useful.  Something similar to
an html "beautify" utility, that might do the above forementioned
("condense" rotations and translates, etc.) as well as make comment
seperators and such uniform, etc.


"Defective" <def### [at] homecom> wrote in message
news:elf41tkr79q176h6et1t7uro4hhn6a71na@4ax.com...
> On 14 Nov 2000 07:44:26 -0500, Geoff Wedig
> <wed### [at] darwinepbicwruedu> wrote:
>
> >
> >Well, since POV does this internally, turning all of that stuff into a
> >single transform, it would only make a difference in the parsing, and
> >parsing is fast enough that I don't think it's high on anyone's
priorities
> >(this coming from someone who does images with 2+ hour parses)
> >
>
> Actually...
>
> I'm thinking along the lines of generating something I can read
> myself.  my machines all parse faster than I do.  An example of the
> problem would be my current project...I'm rendering all the parts I've
> built for my truck.  The parts that mount to the box have all been
> generated through much fiddling.  Now when I look at the code, I spend
> a lot of time wading through the various rotations, translations and
> additions and subtractions that have been used to place the bits and
> pieces where I want them.  I've been cleaning up the individual
> objects and it's taking me hours on some parts.  This should be
> something that can be automated.
>
> Defective O-O
>
>

Post a reply to this message