-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi Richard,

Richard Spindler schreef:
> 2008/2/2, Stefan de Konink <[EMAIL PROTECTED]>:
>> Then you misunderstand me. There are widget toolkits for OpenGL, we can
>> have a look what Blender uses. If we make a new interface based on an
>> OpenGL frontend this can have serious advantages!
> 
> So where exactly is the advantage in creating a new interface, when we
> can use code that has already been written?
> 
> btw. I am talking about the Widgets.
> 
> For Preview and Real-Time compositing, I am all for using OpenGL. But
> this is only necessery for the part of the UI, where the Video Preview
> is. Buttons are mostly 2D, you know? You don't need a 3D OpenGL Window
> for them. :-P

If we are moving canvases around (timeline) it doesn't really matter if
we use Cairo, obscure super fast QT Vector implementation or just native
OpenGL. It has to be written, and I don't think making a button widget
in any drawing implementation takes huge amount of developer effort.


>>> BTW. You can make a fullscreen OpenGL app in Qt and GTK+.
>> My god, I hope you never have done this yourself. Why have a widget
>> toolkit take care of something that can be done without this toolkit,
>> resulting in a smaller application, less dependancies etc?
> 
> What can be done without the toolkit? Sure I can write my own code to
> draw Buttons and process mouse events and stuff, but why, this code
> has already been written, and is well tested. Developer Time is much
> more expensive than CPU time.

I'm sorry developer time is more expensive? Where do you come from? We
are not starting a NewCinelerra company and probably want to have the
best (not the optimal) solution for the system. There are huge amounts
of code written in OpenGL also widgetsets but please don't forget:

There is no widgetset going to improve an video editore where people
prefer to work on with a *keyboard* or a dedicated Shuttle and not a
mouse clicking on buttons! My perception is not to redo Kino, but more
try to conquer the Avid/Combustion user.


http://mac.softpedia.com/progScreenshots/Avid-Xpress-DV-Screenshot-14207.html

Seriously how much *buttons* do you see?


http://www.desktopimages.com/images/Press/VFX-Set-Ext-Combustion-S.jpg

Probably more buttons there...


If in your perception we are making an 'office like' application that
edits video, I might be wrong. But we probably can stick with what
already exists. I am hoping we will design a GUI that is thought
'out-of-the-box'. As a toolkit and not some application, something you
will focus on 100% when you use it.


Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHpQQ2YH1+F2Rqwn0RCt4wAJ9fByh3uHNWQvP7wbZcpEEbairFJACeIz7N
BUDbB42wElF1EEGHyeuv8W8=
=FSDt
-----END PGP SIGNATURE-----

_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra

Reply via email to