Re: octave gset, graw

[Bill Denney]

On Fri, 24 Feb 2006, Daniel J Sebald wrote:

> Bill Denney wrote:
>
> > I agree with this.  That is why I am trying to make sure that the 
> > interface for the users and the backend developers is defined.  If I 
> > can make a set of handles and then use it to make a plot on the screen, 
> > then export it to an SVG, then make an animation out of it, ... then 
> > I'm going to enjoy plotting significantly more (which is currently what 
> > I think is the biggest weakness in Octave).
>
> __graw__('set term gif animate\n');
> __graw__('set output '''myfile.gif'''\n');
> for i_image = 1:50
>  x = <process some data>;
>  plot(x);
> end
> __graw__('set output\n');
>
> I realize it would be nice to have something more like
>
> for i_image = 1:50
>  x = <process some data>;
>  plot(x);
>  print -dgifa 'myfile.gif'
> end
>
> but it takes some non-trivial coding to enable this.

I'm hoping to help do the non-trivial coding that will allow:

movie_handle = movie('file.mpg'); # or .avi or whatever
for i_frame = 1:50
  x = <some data>;
  plot_handle = plot(x);
  movie_handle = addframe(movie_handle, plot_handle);
endfor

My guess is that the movie_handle will have properties like:

frames (handles to figure, axis, or image objects that show the image)
resolution (height and width in pixels)
filetype ('mpg', 'avi', etc-- whatever we can handle)
some more that I can't think of at the moment.

Bill

--
"Patriotism is supporting your country all the time and the government
when it deserves it."
  -- Mark Twain