On Thu, Mar 21, 2002 at 12:43:00PM +0100, Ronald Bultje wrote: > > So, let's see... Scaling. How are you gonna scale? There's various ways > to do this, either of which has advantages over some of the others. So put them all in the lib and let the user or developer choose which method to use based on the app/usage. But for heaven's sake, don't have *every* developer writing and rewriting scaling functions. > So, > which are we gonna use? The one that best suits the user or app. > And how are we going to program it? If I have a > better but uglier way, which won't be put in libv4l, then what? If it is better than the existing methods in some way, then it can be _added_ to the lib. It doesn't have to replace an existing method. > Application developers are supposed to be smart people who know what > they're doing and can write smart apps. But they shouldn't be _re-writing_ low level functions. > Sure, they can use each others > code and make a generic library for some functions, but these functions > should in no way be forced upon the developer. Of course not. > If someone has better > code, let him use that. Sure. Hopefully if it is better, the developer will contribute it to the v4l lib. > Everyone's demands are different. Too different to make one generic > library and force everyone to use it. One generic library does not mean only one way to do things. b. -- Brian J. Murrell
Attachment:
pgpYD30xYValf.pgp
Description: PGP signature
