From owner-freebsd-multimedia Fri May 26 0: 6:51 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from kiew.egd.igd.fhg.de (kiew.egd.igd.fhg.de [192.102.170.32]) by hub.freebsd.org (Postfix) with ESMTP id C5DDE37B856 for ; Fri, 26 May 2000 00:06:44 -0700 (PDT) (envelope-from runge@rostock.zgdv.de) Received: from rostock.zgdv.de (penguin.egd.igd.fhg.de [192.102.170.145]) by kiew.egd.igd.fhg.de (Netscape Messaging Server 3.6) with ESMTP id AAA3236 for ; Fri, 26 May 2000 09:06:37 +0200 Message-ID: <392E231D.BA8C1519@rostock.zgdv.de> Date: Fri, 26 May 2000 09:09:17 +0200 From: Thomas Runge X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en, de MIME-Version: 1.0 Cc: multimedia@FreeBSD.ORG Subject: Re: TV Users - Let me bounce this off you References: <20000525210340.A44725@nc.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Randall Hopper wrote: > > Been thinking about a way to make writing TV apps easier (not just > easy; trivial!). An API that would allow folks to literally write their > own in Python or Tcl TV app with 5-10 lines of code. Well, making complicated things esier is almost always a good idea :-) But it's necessary to specify a good API, which lets you make simple things easy, but doesn't stop you making more complicated tasks. I didn't have a look into the Video4Linux API, but wouldn't it be a good idea to support that? And how about supporting multiple output sources? -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message