Mailing List Archive

libmyth
Started working on this -- I think I'm fairly done breaking CVS now =) If
anyone's following CVS, I'd recommend doing a new checkout, as I've moved
directories and files around quite a bit, and CVS isn't all that great at
updating things like that. Please let me know if things don't build
properly, but it does all compile on my box, as of now.

Anyway, 'libmyth' isn't too library-ish yet, but I've got all the mythtv apps
and mythmusic using it now.

On Friday 20 September 2002 05:29 pm, Thor Sigvaldason wrote:
> Absolutely. In fact, it would be nice to have a fairly large shared lib
> that can do the lcd stuff, handle menus, and even act as a "Myth Server".
> If it can access the database and knows about where content is on the
> filesystem, then it could be the "thing" that could serve content to any
> requesting client whether local or across a network (to solve all of those
> "I want the server in my basement and a diskless box in my living room"
> requests).

Hmm. I'd think the best way to do this is using nfs mounts, really.. Just
have to tell it to use the basement server for the mysql queries, and search
all specified locations for files to play, and you've got a remote box.

I haven't decided how heavy the lib's going to be, yet.

> Whenever you start building a lib, all the algorithms and logic go in
> there, and the GUI's become lighter (more and more like thin clients).
>
> The alternative, of course, is a lighter library and a separate mythServer
> process. Either way, I'd really like to get to a point where you can
> configure mythboxes as peers on a network. It just opens up so much
> potential (mythFarms in your basement that record oodles of programs [e.g.
> handoff of conflicts], p2p file sharing, to end-user streaming, dedicated
> re-encoding boxes for DVD/VCD burning, etc., etc.).
>
> On a related note, are you planning to move MythMusic into the main MC
> executable, or is the plan for it to stay separate (?). Just wondering
> about how to best start sticking mythLCD into other things.

I think I'm going to keep it separate for now. Hm. How well does lcdproc
deal with having multiple programs try and talk to it?

Isaac
Re: libmyth [ In reply to ]
On Saturday 21 September 2002 05:17 pm, you wrote:

>
> Anyway, 'libmyth' isn't too library-ish yet, but I've got all the mythtv
> apps and mythmusic using it now.
>

Lots of files flying around .... :-)
>
> Hmm. I'd think the best way to do this is using nfs mounts, really.. Just
> have to tell it to use the basement server for the mysql queries, and
> search all specified locations for files to play, and you've got a remote
> box.
>

Well .... yes, but then you need NFS. I'm thinking about 3 (6?, 12?) months
from now when I should be able to P2P files from MythBox to MythBox,
regardless of where they are or if a particular tree is in /etc/exports. I
just think a clean client/server model (with requisite protocol between them)
will end up paying huge dividends in terms of flexibility ... my 2 cents :-)


> > On a related note, are you planning to move MythMusic into the main MC
> > executable, or is the plan for it to stay separate (?). Just wondering
> > about how to best start sticking mythLCD into other things.
>
> I think I'm going to keep it separate for now. Hm. How well does lcdproc
> deal with having multiple programs try and talk to it?
>

The lcdproc server is desiged to handle many clients, so that's not a
problem. I'll need to add a public method to lcddevice though in the form of
switchToNothing(), so that, say, mythfrontend can lower the priority of all
it's lcd screens and let a completely different lcddevice object in MythMusic
get all the lcd screen time. Very easy to do. In fact, I'll do it now.

BR,

Thor


--
----------------------------------------------------------------
Thor Sigvaldason <thor@sigvaldason.com>
For my PGP/GnuPG public key, send an e-mail to thorskey@sigvaldason.com
----------------------------------------------------------------
Re: libmyth [ In reply to ]
>
> Very easy to do. In fact, I'll do it now.
>

That's done, and the library builds properly with or without LCD_DEVICE
declared (well, an unused variable error or two when it's not declared, but
that's nothing).

BTW, everything else built cleanly on a fresh checkout for me.

One odd thing though. I redid the Makefile for mythlcd (the executable) so
that it would link against the library. Linking failed, however, with an
undefined reference to globalsettings (of type Settings). I stuck one into
mythlcd's main.cpp and it built and ran fine, but seems the library has some
sort of dependency that I'm not sure you intended (?).

BR,

Thor


--
----------------------------------------------------------------
Thor Sigvaldason <thor@sigvaldason.com>
For my PGP/GnuPG public key, send an e-mail to thorskey@sigvaldason.com
----------------------------------------------------------------