Re: [Openpvr-devel] Project update listing?

[Brian J. M. <5e4...@in...>]

On Sun, Mar 31, 2002 at 12:02:53PM -0500, Gregory Gee wrote:
>=20
>   I can't seem to get to the openpvr project page.

I can get there.

> Is it down?

Doesn't seem to be.  http://openpvr.sf.net/

> I want to
> know what state it is in.

Well, it's still being developed.  I am fairly happy with what I have
going right now, but it's hardly complete.  I have been giving the
"seen" database some thought.  Right now it's updated manually and
it's an XML file.

I don't think an XML file is the right solution however.  A database
(berkely db perhaps, I dunno yet, opinions welcome) I think is the
better vehicle.  An XML file would have to be completely read and
rewritten for every update of the database.

> I see code in CVS but no information on state.

That's because state-wise it's still quite developmental.

> Has someone made up a schedule of what components will be done first.

Not really.  This is a "scratch what itches" type of project, being
done on free and available time.  My first itch was a scheduler which
led to a need to record and playback.

My current itch is a user interface.  I have written (but not yet
committed) a very basic interface using GTK+ for Linux framebuffer.
It simply lists the files in my movie directory and when one is
selected, it plays it with MPlayer.

Before I can make any more progress with the UI I need to get an IR
receiving going so that I can interact with the UI.  I went out
yesterday to buy some IR (lirc) parts but was not successful.  I will
be back out tomorrow for them.  I expect to have a remote in the next
couple of days so I can further the selction and playback UI.

> It
> would be useful if a release was made available with the scheduler and
> recording.

Nothing is really release-state ready yet.  What you can get out of
CVS is useful and works (I use it everyday to schedule my recordings)
but basic, but "experimentally-unneeded" things like file locations,
and command line args parsing and the like are not there.  Also I want
to have the seen database fully functional before making a release.

> Playback is an optional builtin component right now for me.  I'd
> really like to at least start recording.

Well checkout CVS and play with the scheduler and "record".  What
record/encoder are you planning on using?  record supports a handful.

>   When the project page returns could someone list the order of the compo=
nents
> that will be completed and there current state.  Also some installation n=
otes
> would be handy.

They would be.  I will see if I can get some basic notes going.

> - scheduler
> - recorder
> - playback
> - web frontend to scheduler

I will likely not be doing a web interface myself, unless I get an
itch.  I am not a fan of web interfaces, but if somebody wants to
write one, I will certainly include it if it's useful enough.

b.

--=20
Brian J. Murrell