I just finished creating a new CWS 'helixplayer' that is based on SRC680m93 and that contains the 'avmedia' and 'scp2' modules.
I added the patch contributed by Ryan with some minor modifications to get it compiled properly. I also made the necessary changes to support multiple engines. On Unix these are currently JMF and Helix (in this order). 'scp2' project contains the necessary changes to get the new lib installed and registered properly. With the currently committed changes, the Helix backend is able to be instantiated and to playback audio on my system out of the box (with a Real/Helixplayer installed, of course). Video playback is currently not possible and needs further investigation by somebody knowing the helix details. Best regards Kai Kai Ahrens wrote: > Hi Ryan, > > many thanks for your current contributions. This looks > like a very good starting point, so that I'd be happy > to create an initial CWS that can be used to add the > still necessary enhancements. > > I'll come back to the mailing list as soon as > I created the CWS and added the changes. > > Please let's follow up on the [email protected] > mailing list. > > Best regards > Kai > > Ryan Gammon wrote: > >>Hi guys, >> >>I've been thinking about where we're at with helix & openoffice, and >>thought I'd summarize where we're at right now so we can figure out some >>next steps. >> >>The original patch is here: >>http://www.openoffice.org/issues/show_bug.cgi?id=41419 >> >>I've gotten a variety of feedback back on this patch -- thanks to all >>who commented :) >> >>In terms of work to be done, here's where I think we're at: >> >>1. Getting the code into CVS -- ideally via the creation of a CWS for >>helix integration work into ooo's avmedia. We could also potentially do >>this in helixcommunity.org if that's easier. >> >>2. Fixing the places in my code where I'm assuming a modified ooo api -- >>I changed some code in avmedia in the interests of getting things >>working. I now need to go back and fix it up to work with the original >>API. eg, Player::createPlayerWindow(). >> >>3. Supporting multiple media engines at runtime -- currently (or at >>least, last time I looked), avmedia selected the media engine at compile >>time. >> >>4. Sorting out embedding -- Currently embedding is accomplished by >>reparenting a helix video area on top of a JavaChildWindow. This is a >>SystemChildWindow with some extra bits. Ideally JavaChildWindow could be >>split into a more general EmbeddingChildWindow, and could enable the >>extra Java glue if the component being hosted is Java-based. If the >>EmbeddingChildWindow could implement support for XEmbed on unix, even >>better. >> >>One comment mentioned that there's a SAL_USE_VCLPLUGIN=gtk option that >>potentially might do some XEmbed stuff with GtkSocket, but I haven't >>figured that out yet. Any pointers here appreciated. >> >>5. Making the helix side cross-platform. Currently, the helix side is >>largely copied & pasted from the linux mozilla plugin. The RealPlayer >>plugin variant I'm using is a linux-only thing. There've been >>suggestions that we look at using out of process UNO & creating a UNO >>component for helix. If anyone has pointers here, it'd be much >>appreciated. In the process, we could potentially make this work on >>other supported helix platforms like windows & mac as well. >> >>This is kinda a spare time project for me, so if there's anyone who >>feels like pitching in, I'm happy to help :) >> >>Looking forward to your comments. >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
