On Fri, Oct 17, 2008 at 10:28 PM, Sam Gross <[EMAIL PROTECTED]> wrote:
> I'll take a look at getting the XPCOM plugin to work in FF2/Gecko 1.8 this > weekend. I was able to get the Mac version to work in Firefox 2 with > relatively few changes, so I hope the same will be true on other platforms. > Right, I don't think it will be that hard, but the primary issue seems to be the gecko sdk on the web page doesn't include all the bits we need, so it probably means extracting it from a FF2 build. > We may also want to decide if we want to place some or all of the xulrunner > SDK in the tools/ directory before the merge to trunk. I think putting the > entire SDK would be in the tools/ directory would be much too large, but we > may be able to place only the pieces necessary to compile the XPCOM and > NPAPI plugins. (I think Gears takes this approach). > Good point, although I think that is a blocker for a 2.0 release but not merging it into trunk (I wouldn't expect many people to need to build their own plugin, and those that do will probably be doing it because we don't support their favorite FF platform and they will need to get the xulrunner/gecko SDK for their platform anyway). I also want to take advantage of your work on the shared memory channel at some point, but that will probably be after it is merged to trunk since the performance seems to be at least on par if not better than the existing hosted mode. -- John A. Tamplin Software Engineer (GWT), Google --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
