Re: [Freevo-devel] Re: Rendezvous

2004-04-18 Thread Aubin Paul
On Sun, Apr 18, 2004 at 09:37:57AM +0200, Lars Eggert wrote: > Oh - then it doesn't do what I thought it would do. I was actually > hoping to have my music and photos shop up in iTunes and iPhoto > automatically, i.e., share it via Rendezvous. I may have to look at howl > directly to see how to

Re: [Freevo-devel] Re: Rendezvous

2004-04-18 Thread Lars Eggert
Aubin Paul wrote: It was more of a proof of concept in broadcasting the webserver to a Safari/HOWL enabled PC. It could concievably work with the recordserver as well, but no one else wanted to persue it ;) Oh - then it doesn't do what I thought it would do. I was actually hoping to have my music

Re: [Freevo-devel] Re: Rendezvous

2004-04-17 Thread Michael Ruelle
One of the reasons I think it hasn';t been persued is that currently depending on what method you call of the record server it can be very tricky to develop something other than in the freevo/python environment we setup. We use some persistence calls that pass python objects. Unfortunately the pers

Re: [Freevo-devel] Re: Rendezvous

2004-04-17 Thread Aubin Paul
It was more of a proof of concept in broadcasting the webserver to a Safari/HOWL enabled PC. It could concievably work with the recordserver as well, but no one else wanted to persue it ;) I believe the module I included in CVS has support for both finding and broadcasting... Aubin On Sat, Apr

Re: [Freevo-devel] Re: Rendezvous

2004-04-17 Thread Ross Karchner
Is the Rendevous plugin meant to help users find the web interface, or to help the freevo app and webserver find a recordserver? Aubin Paul wrote: I used it a few times after I initially wrote it, but I haven't been using it recently. I'm guessing some things have changed and I never updated it

Re: [Freevo-devel] Re: Rendezvous

2004-04-17 Thread Aubin Paul
I used it a few times after I initially wrote it, but I haven't been using it recently. I'm guessing some things have changed and I never updated it to work. I can probably take a more serious look on Wednesday... On Sat, Apr 17, 2004 at 03:06:38PM +0200, Lars Eggert wrote: > Am I the first to run

Re: [Freevo-devel] Re: Rendezvous

2004-04-17 Thread Lars Eggert
Dirk Meyer wrote: This needs to be version only. freevo.version only is possible when Freevo is installed into the system python path. Try to remove the freevo. stuff That helped some. Now it dies here: failed to load plugin freevorendezvous start 'freevo plugins -l' to get a list of plugins Trace

[Freevo-devel] Re: Rendezvous

2004-04-17 Thread Dirk Meyer
Lars Eggert wrote: > Aubin Paul wrote: > >> Looks like the problem is the filename; can you try it with the file >> renamed and the plugin.activate changed to that? It seems to not like >> the '-' > > Tried already, getting this then: > > failed to load plugin freevorendezvous > start 'freevo plugi

[Freevo-devel] Re: Rendezvous

2004-01-07 Thread Dirk Meyer
Aubin Paul wrote: > On Tue, Jan 06, 2004 at 08:36:59PM +0100, Dirk Meyer wrote: >> This is only for one plugin (and a bad hack). What about making >> something like >> >> plugin.register('whaterver', type='webserver') >> >> Than web and recorderserver call plugin.init(). If the following >> stuff

Re: [Freevo-devel] Re: Rendezvous

2004-01-06 Thread Aubin Paul
On Tue, Jan 06, 2004 at 08:36:59PM +0100, Dirk Meyer wrote: > This is only for one plugin (and a bad hack). What about making > something like > > plugin.register('whaterver', type='webserver') > > Than web and recorderserver call plugin.init(). If the following > stuff: That seems logical to me

[Freevo-devel] Re: Rendezvous

2004-01-06 Thread Dirk Meyer
Rob Shortt wrote: > Aubin Paul wrote: >> Ok, it's working, but it's clunky because the plugin is activated >> under the OSD interface when it really should be in the webserver.py >> helper. Anyone want to hazard a guess on the best way to do this? > > Sure. :) > > I had to get recordserver to use p

[Freevo-devel] Re: Rendezvous

2004-01-06 Thread Dirk Meyer
Aubin Paul wrote: > Ok, it's working, but it's clunky because the plugin is activated > under the OSD interface when it really should be in the webserver.py > helper. > > Anyone want to hazard a guess on the best way to do this? I knew this day would come. So we need a plugin interface for the we