similar to: [PATCH] browser_plugin - kate support, build fixes, and misc

> I've tried to separate out the general bugfixes from the new > implementation work in this patch: Sorry, I should have done that, I do tend to fix stuff I find while coding and neglect splitting up afterwards. Bad me. > I've not yet committed this to trunk. It does sound pretty cool > though. I don't see any problem with adding pango etc. support, it's > pretty

Hi, I've added kate support to liboggplay (a prerequisite to getting kate tracks to work with the mozilla plugin, which I've now got working on Linux). In addition to the Kate code: - a new oggplay-uninstalled.pc file - configure.ac checks for C++ compiler - no check for fishsound version - it wanted 0.8.0, but the svn itself was 0.7.1 !? - don't use imlib2 (nor dump-first-frame) if

2008/4/30 ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com>: > > > Let me know if this works for you or not; eg. it may be necessary to > > > also put X_EXTRA_LIBS etc. in src/Makefile.am. > > > > will try this. > > It worked fine for me, with no need to add anything to Makefile.am. > good > > > > - bad pointer

where is the latest javascript api documented? it does not look like http://wiki.xiph.org/index.php/OggPlayJavascriptAPI has been updated recently. I had trouble getting oggplay to run at all on my machine ubuntu (7.10) But I would be interested in revisiting the issue... --michael Conrad Parker wrote: > 2008/5/1 ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com>: >

> hmm, perhaps we should add some configure arguments like > --with-firefox-cflags= and --with-firefox-libs= I've made it a single one, --with-gecko-sdk= and also default include path and xpidl path to that if specified. Also included are a patch that renames LIBOGGPLAY_* vars to OGGPLAY_* to match the latest change to configure.ac, and one that allows the audio to be compiled out -

> > - kate support (what else) - this bumps the Javascript API to 1.1 > > I've not yet committed this to trunk. It does sound pretty cool Can you let me know the reasons (eg, wanting to test first, concerns over the substance of the changes, or other) ? There were no comments so far about the changes to the Javascript API, so I'll assume people have no problem with those ?

> where is the latest javascript api documented? it does not look like > http://wiki.xiph.org/index.php/OggPlayJavascriptAPI has been updated > recently. Well, I was aware of that page, but I wasn't going to change it by myself before the patch would be accepted :) If it is, I'll update the page. Here's an overview for now: + long getNumKateTracks(); returns the number of

> > Let me know if this works for you or not; eg. it may be necessary to > > also put X_EXTRA_LIBS etc. in src/Makefile.am. > > will try this. It worked fine for me, with no need to add anything to Makefile.am. > > > - bad pointer dereference fix (mouse callback) > > > > I couldn't find that particular hunk, could you please provide a patch > >

2008/4/28 ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com>: > Hi, Hi, I've tried to separate out the general bugfixes from the new implementation work in this patch: > this patch adds: > > - kate support (what else) - this bumps the Javascript API to 1.1 I've not yet committed this to trunk. It does sound pretty cool though. I don't see any problem

>> hmm, perhaps we should add some configure arguments like >> --with-firefox-cflags= and --with-firefox-libs= > > I've made it a single one, --with-gecko-sdk= and also default > include path and xpidl path to that if specified. Hi, I noticed this hasn't been applied, so I'm sending it again as it's quite simple and, I think, unobtrusive. It allows building

On 21/04/2008, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com> wrote: > Hi, > > I've added kate support to liboggplay (a prerequisite to getting kate tracks > to work with the mozilla plugin, which I've now got working on Linux). > great! > In addition to the Kate code: > > - a new oggplay-uninstalled.pc file configure.ac:366: required

2008/5/1 ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com>: > > > - kate support (what else) - this bumps the Javascript API to 1.1 > > > > I've not yet committed this to trunk. It does sound pretty cool > > Can you let me know the reasons (eg, wanting to test first, concerns > over the substance of the changes, or other) ? sure, the main

2008/5/5 ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com>: >> hmm, perhaps we should add some configure arguments like >> --with-firefox-cflags= and --with-firefox-libs= > > I've made it a single one, --with-gecko-sdk= and also default > include path and xpidl path to that if specified. (applied after an email reminder, r3605) > Also included are a

> I think you forgot to include oggplay-uninstalled.pc.in in the patch :-) Attached, plus the oggplay.pc.in as well, as I added @KATE_CFLAGS@ to both. Also attached is a patch to avoid miscounting the number of active tracks (a bug in my previous patch), and the current patch to the mozilla plugin (still work in progress, the Javascript API will change a little) if anyone feels like

> There seems to be some inconsistency in the changes to the type of > sample_in_record and its accessor: the field was changed from int to > ogg_int64_t in src/liboggplay/oggplay_callback_info.h, and the return > type of the accessor function was changed from int to long in the > corresponding .c file and public header. Having heard no more about this, I'll make a patch that

2008/4/22 Conrad Parker <conrad at metadecks.org>: > sorry, my bad -- recent releases have been coming out of > http://svn.annodex.net/libfishsound/branches/1.0-stable > The latest version is 0.9.1. > > trunk is mostly up-to-date with that, and has some extra, incomplete, stuff. As this was confusing, I've renamed the libfishsound branches to what anyone would expect:

Hi, I've eventually released the first version of my rendering library for Kate streams, and I've recently been hacking away at adding it to liboggplay. That was the missing "overlay" mode to the browser_plugin patch I sent a while ago. Now, I'm not too sure how to expose those overlays to liboggplay users: the obvious solution is to add a RGBA video type, and expose the

2008/4/23 ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com>: > > I think you forgot to include oggplay-uninstalled.pc.in in the patch :-) > > Attached, plus the oggplay.pc.in as well, as I added @KATE_CFLAGS@ > to both. > Also attached is a patch to avoid miscounting the number of active tracks > (a bug in my previous patch), thanks, applied in

Hi, This is an updated patch, replacing the previous one. It allows rendering Kate streams using libtiger (itself using Pango and Cairo). It allows video to be converted to RGB, and overlaying of a Kate stream onto a video. While there, there are various fixes/tweaks (the asm versions of the YUV to RGB converters would move the data pointer, so anyone using those at a later time would access bad

FYI: I included video/ogg into liboggplay, too. For audio/ogg, another application would probably make more sense. Cheers, Silvia. On Sun, Aug 17, 2008 at 11:35 PM, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > On 7/22/08, Nils Dagsson Moskopp > <nils-dagsson-moskopp at dieweltistgarnichtso.net> wrote: >> (...) the registered mime type application/ogg > >