Re: [Pyobjc-dev] QuickTimeViewer demo using PyObjC!
Brought to you by:
ronaldoussoren
From: Jack J. <Jac...@or...> - 2003-01-07 22:33:35
|
On dinsdag, jan 7, 2003, at 11:34 Europe/Amsterdam, Dinu Gherman wrote: > Ok, instead of fiddling further with services I wrote a simple demo > that fetches and displays QuickTime movies from the web, with some > predefined URLs pointing to pixar.com > Now if I only could get access to the real QuickTime movie content > using PyObjC...! We have all the tools in Python to do this, we only need to glue them together! NSMovie has a QTMovie method which returns the quicktime movie object. If we have a way to pass this to Carbon.Qt.Movie() we would be all set. And note that the same goes for lots of other objects for other frameworks that Cocoa can wrap. This is an area in which Python can really outshine Java, because we not only have the Cocoa interface but also the Carbon and other toolboxes. My preferred way to glue this together would be to add a method pyObjC_NSMovieAsMovie to PyObjC, which would return the void* as a Carbon.Qt.Movie object (and also the reverse: initWithMovie: should accept a Carbon. Qt.Movie object too. Note that this will not tie PyObjC to the Carbon.Qt module directly: the MovieObj_New() and MovieObj_Convert() routines (which convert C pointers from/to Python objects) are in the Python core, and when first invoked they will attempt to load the required module. After that the calls are fairly cheap: one extra subroutine call. Or we could say that NSMovie and initWithMovie: are pretty useless as they are anyway, and just let those always use Carbon.Qt.Movie objects. -- - Jack Jansen <Jac...@or...> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman - |