ogg.k.ogg.k at googlemail.com
2008-May-01 10:22 UTC
[ogg-dev] [PATCH] browser_plugin - kate support, build fixes, and misc
> > - kate support (what else) - this bumps the Javascript API to 1.1 > > I've not yet committed this to trunk. It does sound pretty coolCan 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 ? Cheers
Conrad Parker
2008-May-01 11:30 UTC
[ogg-dev] [PATCH] browser_plugin - kate support, build fixes, and misc
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 reason is that we're trying to stabilize the trunk, and you described this as a work in progress. The other reason is that it'd be good to get some other feedback -- I'm not so familiar with the internals of oggplay, though I'm happy to do maintenance and am trying to learn my way around the code too :-) If you like I'll push it into a branch, and we can encourage some more testing from there.> There were no comments so far about the changes to the Javascript > API, so I'll assume people have no problem with those ?It'd be good to get feedback from shane and mdale on that ... Conrad.
ogg.k.ogg.k at googlemail.com
2008-May-01 11:49 UTC
[ogg-dev] [PATCH] browser_plugin - kate support, build fixes, and misc
> sure, the main reason is that we're trying to stabilize the trunk, and > you described this as a work in progress. The other reason is thatOh, right. The first version of the patch was definitely WIP, I'd posted hoping someone would comment on (mostly) the Javascript API changes since that will be visible externally. The second one I posted is more or less done from a functional point of view, barring feedback, if any (or bugs). If you're referring to me mentioning Cairo and Pango, that is more longer term (I've just starting the rendering lib recently) and I don't plan to add this to the plugin soon, so any substantial changes from me will be based on any feedback I may receive. If you're stabilizing though, then that's fine, I just wanted to know if there were changes that would be requested for inclusion. And of course, there's the little problem of having a no-op implementation for Mac and Windows :) Is this a problem for you/others ? Thanks
Michael Dale
2008-May-02 07:15 UTC
[ogg-dev] [PATCH] browser_plugin - kate support, build fixes, and misc
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>: > >>>> - 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 reason is that we're trying to stabilize the trunk, and > you described this as a work in progress. The other reason is that > it'd be good to get some other feedback -- I'm not so familiar with > the internals of oggplay, though I'm happy to do maintenance and am > trying to learn my way around the code too :-) > > If you like I'll push it into a branch, and we can encourage some more > testing from there. > > >> There were no comments so far about the changes to the Javascript >> API, so I'll assume people have no problem with those ? >> > > It'd be good to get feedback from shane and mdale on that ... > > Conrad. >
ogg.k.ogg.k at googlemail.com
2008-May-22 17:41 UTC
[ogg-dev] [PATCH] browser_plugin - kate support, build fixes, and misc
> sure, the main reason is that we're trying to stabilize the trunk, and > you described this as a work in progress. The other reason is that > it'd be good to get some other feedback -- I'm not so familiar with > the internals of oggplay, though I'm happy to do maintenance and am > trying to learn my way around the code too :-)Is anything happening somewhere else ? I don't see changes being made on this tree at all. I'm looking at http://svn.annodex.net/browser_plugin (which kinda seems to be the right one since it has a few of the mods I sent). Thanks
Possibly Parallel Threads
- [PATCH] browser_plugin - kate support, build fixes, and misc
- [PATCH] browser_plugin - kate support, build fixes, and misc
- [PATCH] browser_plugin - kate support, build fixes, and misc
- [PATCH] browser_plugin - kate support, build fixes, and misc
- [PATCH] browser_plugin - kate support, build fixes, and misc