GNOME Bugzilla – Bug 651536
baseclass for scopes (visualizers)
Last modified: 2011-06-06 12:23:49 UTC
I have started a baseclass for visualizers and wrote a couple of them. I'll post this here for some early comments as I will be away for a few days. Next things I will do is: * unit tests * element-maker template * improve synaescope (it is already quite similar) * more shading functions
Created attachment 188917 [details] [review] scopes: first version of a scopes plugin using a new baseclass Add a new baseclass for writing visualisation plugins. Provide a simple wave oscilloscope as a first subclass.
Created attachment 188918 [details] [review] scopes: add a simple fft based scope Add a 2nd demo scope that uses a fft.
Created attachment 188919 [details] [review] basescope: remove some comments Those comments where pointing to example calls that we do in the subclass.
Created attachment 188920 [details] [review] basescope: allow subclasses telling how many sample they need per frame This allows e.g. FFT based elements to require enough data. If they need more data than what we get, we flush less from the adapter.
Created attachment 188921 [details] [review] basescope: add a backbuffer and apply shading effects Keep the last frame and apply shade and geometry effects. Expose the shading effects as a controllable gobject property on the baseclass.
Created attachment 188922 [details] [review] basescope: add a property to modify the ammount of shading Add another property to specify the shading per color channel. Fix endianess issues in the shading code.
Created attachment 188923 [details] [review] basescope: add more shading effects
Created attachment 188924 [details] [review] scopes: draw pixels with signle 32bit writes
Created attachment 188925 [details] [review] scopes: add a new element similar to synaesthesia
Created attachment 188926 [details] [review] spectrascope: use add_pixel for non-white pixels
Created attachment 188927 [details] readme with testing info and stuff
"Scope"? How about "Visualizer" or something.
I found Visualizer to long and I am always unsure wheter it is Visuali{z,s}er :). But if that is all that people are worried about I can change it for sure.
Seems that we're using the American spelling everywhere (e.g. serialize)... so use the z :)
I have been making the changes (renaming), integrated with docs, tests and other stuff. Just pushed the patches. Change request per IRC/email :)