Ron Parker wrote:

> I just started playing with pov-mode myself, and the first thing I
> found is that rendering the scene is a lot more work than it should
> be.  Is there some variable somewhere I can set with the default
> render command so I don't have to retype it every time I run emacs?

Just make a make file. Then you can just do the emacs compile command to
make it work. Plus, you can setup all the dependencies of .inc files and map
files, etc.


--
"My new computer's got the clocks, it rocks
But it was obsolete before I opened the box" - W.A.Y.

Post a reply to this message

On Tue, 02 Nov 1999 07:41:26 -0800, Jon A. Cruz wrote:
>Ron Parker wrote:
>
>> I just started playing with pov-mode myself, and the first thing I
>> found is that rendering the scene is a lot more work than it should
>> be.  Is there some variable somewhere I can set with the default
>> render command so I don't have to retype it every time I run emacs?
>
>Just make a make file. Then you can just do the emacs compile command to
>make it work. Plus, you can setup all the dependencies of .inc files and map
>files, etc.

I don't tend to do big complicated scenes, and I certainly don't put them
in separate directories.  I just want a simple command I can execute to 
render the current buffer using some default ini file.  It's the "render 
the current buffer" part it doesn't seem to handle - I have to actually 
type the name of the current file into the minibuffer whenever I switch 
to another project.  I also have to manually type in 
"~/sp31g/source/unix/x-povray dw320.ini" each time I restart emacs.  
That seems like too much work.  Of course I could add a symlink or shell
script to make it a little shorter, but ideally it would remember it from 
session to session.

But, inspired by what you suggested, wouldn't it be cool if POV had an 
option like GCC's -E -MMD to automatically generate dependency information?

-- 
These are my opinions.  I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message

Ron Parker <ron### [at] povrayorg> wrote:
: But, inspired by what you suggested, wouldn't it be cool if POV had an 
: option like GCC's -E -MMD to automatically generate dependency information?

  What would you use that information for?
  AFAIK you can't compile pov files to object files which you then link
together to a binary file, but everything is parsed again every time you
render a scene.

  Or is this some superpatch feature?-)

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

On 2 Nov 1999 11:48:02 -0500, Nieminen Juha wrote:
>Ron Parker <ron### [at] povrayorg> wrote:
>: But, inspired by what you suggested, wouldn't it be cool if POV had an 
>: option like GCC's -E -MMD to automatically generate dependency information?
>
>  What would you use that information for?
>  AFAIK you can't compile pov files to object files which you then link
>together to a binary file, but everything is parsed again every time you
>render a scene.

For building a makefile as Jon suggested - one that only rerenders a given
scene if something about it has changed.  Not that such a feature is 
particularly useful, I guess, but it'd still be nice to be able to get a
list of the dependencies of a scene file if you plan to pack it up and
send it off to irtc or news.povray.org or wherever.

-- 
These are my opinions.  I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message

Ron Parker wrote:

> On Tue, 02 Nov 1999 07:41:26 -0800, Jon A. Cruz wrote:
> >Ron Parker wrote:
> >
> >> I just started playing with pov-mode myself, and the first thing I
> >> found is that rendering the scene is a lot more work than it should
> >> be.  Is there some variable somewhere I can set with the default
> >> render command so I don't have to retype it every time I run emacs?
> >
> >Just make a make file. Then you can just do the emacs compile command to
> >make it work. Plus, you can setup all the dependencies of .inc files and map
> >files, etc.
>
> I don't tend to do big complicated scenes, and I certainly don't put them
> in separate directories.  I just want a simple command I can execute to
> render the current buffer using some default ini file.  It's the "render
> the current buffer" part it doesn't seem to handle - I have to actually
> type the name of the current file into the minibuffer whenever I switch
> to another project.  I also have to manually type in
> "~/sp31g/source/unix/x-povray dw320.ini" each time I restart emacs.
> That seems like too much work.  Of course I could add a symlink or shell
> script to make it a little shorter, but ideally it would remember it from
> session to session.
>
> But, inspired by what you suggested, wouldn't it be cool if POV had an
> option like GCC's -E -MMD to automatically generate dependency information?
>
>

I use a make file even if I only have one file. Its easy to make different
settings. I never use inc files as I have yet to see a need for them. Then i
have bind the compile command to f12 in emacs.


Note that this will always execute even if the source has not changed.
-----------

SRC=<change_to_your_file>.pov

CC=/usr/src/pov/povray31/source/unix/x-povray
INC=/usr/src/pov/bin/povray31/include

WIDTH=640
HEIGHT=480

QWIDTH=320
QHEIGHT=240


normal:
        $(CC) -L$(INC) -i $(SRC) +w$(WIDTH) +h$(HEIGHT) +d +v

quick:
        $(CC) -L$(INC) -i $(SRC) +w$(QWIDTH) +h$(QHEIGHT) +d +v

Post a reply to this message

Ron Parker <ron### [at] povrayorg> wrote:
: it'd still be nice to be able to get a
: list of the dependencies of a scene file if you plan to pack it up and
: send it off to irtc or news.povray.org or wherever.

  Yes, that would be useful sometimes.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Btw, another useful feature would be a switch that makes povray just
parse the scene but not render it. This would be a fast way of checking the
syntax correctness of a file.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Nieminen Juha wrote:
> 
>   Btw, another useful feature would be a switch that makes povray just
> parse the scene but not render it. This would be a fast way of checking the
> syntax correctness of a file.

... or start povray with "+w1 +h1".

Post a reply to this message

Jakob Flierl <joo### [at] gmxde> wrote:
: ... or start povray with "+w1 +h1".

  That's not the same since it will not only parse the scene but actually
make instances of all the objects, calculate all the #while-loops, #macros,
etc, and so on.
  For example the conversion of bicubic patches to triangles is done
after parsing the patches and can take very long.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

On 3 Nov 1999 12:05:49 -0500, Nieminen Juha wrote:
>  That's not the same since it will not only parse the scene but actually
>make instances of all the objects, calculate all the #while-loops, #macros,
>etc, and so on.

Some of that would probably have to stay.  Consider these two problems, which
wouldn't be caught on such a prepass but probably should be:

Problem 1:
----------
#macro MyMacro( foo, bar ) 
  object {foo texture {bar}}
#end

MyMacro(1,2)

Problem 2:
----------
#declare a=0;
#while (a<1 ) 
  #if (a<.5)
    sphere {10*a*x,1 pigment {color rgb 1-a}}
  #else
    sphere {10*a*x,1 pigment {color rgb a}
  #end
  #declare a=a+.1;
#end

-- 
These are my opinions.  I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message