|
From: Simon de B. <si...@z2...> - 2003-03-20 10:05:56
|
> > Isn't that what a (ffmpeg) stream in/out objects should take care of? Or will > > connector be able to 'recognize' some standard streams. > > you might have noticed that i'm trying to avoid creating the objects > manually. when user says i want a videoplayer he gets the complete patch > consisting of several "little" objects - media in/out, timer + > scheduler. it doesn't mean, as anne was afraid, that we (artm and simon) > will have to invent the most generic and siutable for anybody compound > objects - anybody will be able to do that, anybody who feels he has > enough expertise and courage :) yes, that's clear. > > but compound objects (or components, or maybe we'll call them servlets? > because they run on server. then their GUIs will be applets) aren't the > only way to hide details. the "intelligent pipeline construction" is > another. this technique can take care of inserting ffmpeg-out / > ffmpeg-in objects on both ends of distributed connector if the types of > the properties being connected are supported (or suggest) using > ffmpeg-stuff. So you get intelligent/flexible compound objects (servlets) that are able to change in/out types according to connection. That's i think a powerfull approach for hiding details.. -- Simon de Bakker \/01|)7 workgroup: http://www.void7.org personal homepage: http://www.josos.org |