Hi,
If you permit me to add, a way to edit fxd files thru forms would be
very nice too.
On 3/22/07, Dirk Meyer <[EMAIL PROTECTED]> wrote:
> "Ky Phan" wrote:
> > Hello Freevo users, I'm a student and I'm interested in this part (see
> > subject) of the project. I have web app development experienc
Thanks, Dirk. I'll get on it.
On 3/22/07, Dirk Meyer <[EMAIL PROTECTED]> wrote:
"Ky Phan" wrote:
> Hello Freevo users, I'm a student and I'm interested in this part (see
> subject) of the project. I have web app development experience with
webpy,
> Rails and PHP and I believe that I can help ma
Hi,
Thanks to Jason's help the xmltv grabber for kaa is
finished and the patch is attached.
Hope it works as expected.
BTW I noticed that browsing the TVGuide is very very slow.
Is this something you guys are working on?
Will that improve with the new GUI stuff?
Regards
Tanja
Index: epg/sr
Dirk Meyer wrote:
> I just took a quick look. Only the stuff in the tgz is needed in the
> games subdir? Looks very promissing. Maybe make emulator not a plugin
> and inherit special emulators from it.
>
Yes only the stuff in the tgz is need in the games subdir. the patch i
supplied is also need
Hi,
Some time ago I said I wanted to work on the favorites and scheduled
plug-ins. Well I finally got time to do so. So attached you can find the
new scheduled TV plug-in.
I also changed the tvserver. This was needed because when an recording
was removed and the new list was retrieved, it was sti
Mathias Weber wrote:
> Dirk Meyer wrote:
>> Please send the code as tgz of the games directory + a patch of all
>> non games files.
>
> ok here is the games directory as tar.gz and the patch for the rest.
I just took a quick look. Only the stuff in the tgz is needed in the
games subdir? Looks very
Mathias Weber wrote:
> Dirk Meyer wrote:
>> Mathias Weber wrote:
>>> Dirk Meyer wrote:
Please send the code as tgz of the games directory + a patch of all
non games files.
>>> ok here is the games directory as tar.gz and the patch for the rest.
>>
>> Thanks. I'm very busy at work this we
Dirk Meyer wrote:
> Mathias Weber wrote:
>> Dirk Meyer wrote:
>>> Please send the code as tgz of the games directory + a patch of all
>>> non games files.
>> ok here is the games directory as tar.gz and the patch for the rest.
>
> Thanks. I'm very busy at work this week (last week vacation and CeB
On 2007-03-22 10:52, Hans Meine wrote:
> What is the rationale for the try..except then?
> Cutting off the traceback? (That's the only effect I can see right now.)
>
To handle unexpected exceptions (i.e. not core.ParseError) originating
from inside a parser. In this case we should log the exc
Hans Meine wrote:
> Am Donnerstag, 22. März 2007 15:41:29 schrieb Dirk Meyer:
>> thing that could happen inside this block. What about:
>> | except (KeyboardInterrupt, SystemExit), e:
>> | raise e
>
> What is the rationale for the try..except then?
> Cutting off the traceback? (That's the only
Am Donnerstag, 22. März 2007 15:41:29 schrieb Dirk Meyer:
> thing that could happen inside this block. What about:
> | except (KeyboardInterrupt, SystemExit), e:
> | raise e
What is the rationale for the try..except then?
Cutting off the traceback? (That's the only effect I can see right now.
On 2007-03-22 10:41, Dirk Meyer wrote:
> | except (KeyboardInterrupt, SystemExit), e:
> | raise e
>
> That should work as expected.
>
Yes, this is what I had in mind too, but didn't want to make any changes
before talking about it.
--
Jason Tackaberry wrote:
> except (KeyboardInterrupt, SystemExit):
> +# FIXME: kaa.metadata is a library, and it is not its place
> +# to institute behaviour on these exceptions. Rather it
> +# should bubble up these exceptions and let th
On 2007-03-22 09:43, Dirk Meyer wrote:
> or maybe use the global Parser idea:
>
> | Parser = RiffInfo
>
Ok, I did it this way.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and
Jason Tackaberry wrote:
> On 2007-03-22 08:35, Dirk Meyer wrote:
>> What about naming all parser classes Parser() just like Freevo names
>> all plugins PluginInterface. In that case we would
>>
>> | register('video/avi', ('wav','avi'), 'video.riff')
>>
>
> I'd prefer adding a function get_parser
On 2007-03-22 08:35, Dirk Meyer wrote:
> What about naming all parser classes Parser() just like Freevo names
> all plugins PluginInterface. In that case we would
>
> | register('video/avi', ('wav','avi'), 'video.riff')
>
I'd prefer adding a function get_parser to each of them, that just
return
On 2007-03-22 08:24, Dirk Meyer wrote:
> o Basic knowledge of kaa.base and minimal knowledge of kaa.metadata
> (you can learn this while coding). No need of the internals of
> Freevo is required.
>
Yeah, kaa.base is going to be pretty easy to learn. Just read the
documentation. Oh wait ..
"Killian Faughnan" wrote:
> Preferably something in the kaa.popcorn area as I've seen the entry
> in the wiki and it looks to be something I would enjoy. Would
> someone be able to provide more details on what would be required
> for this? Will I need to work with C along with python, or just
> pyt
Jason Tackaberry wrote:
> Dirk Meyer wrote:
>> There was a reason why the flac parser was at the end because it had
>> some false positive detections. We need some extra attribute about the
>> rating of a parser to sort them when checking all possible parser.
>>
>
> If a parser has a problem wit
Dirk Meyer wrote:
> There was a reason why the flac parser was at the end because it had
> some false positive detections. We need some extra attribute about the
> rating of a parser to sort them when checking all possible parser.
>
If a parser has a problem with false positives (like the mp3 p
"Ky Phan" wrote:
> Hello Freevo users, I'm a student and I'm interested in this part (see
> subject) of the project. I have web app development experience with webpy,
> Rails and PHP and I believe that I can help make a great web app to control
> freevo over the web.
> I just wanted to introduce my
Dirk Meyer wrote:
> I don't think that was such a good idea. Some parser are better an
> than other:
>
> There was a reason why the flac parser was at the end because it had
> some false positive detections. We need some extra attribute about the
> rating of a parser to sort them when checking all
Jason Tackaberry wrote:
> Import parsers on-demand -- significantly speeds up startup time when the
> correct parsers can be discovered by file extensions;
I don't think that was such a good idea. Some parser are better an
than other:
> -import audio.ogg
> -import audio.m4a
> -
23 matches
Mail list logo
