Ryan Gammon wrote:

> How does a t indicate that it supports Xembed?
>
> Our embedded player (running in a separate process) is building on a 
> GtkPlug widget, so we should be Xembed compatible. 

Here's a sample bit of code that I used in my test plugin.  It's very easy.

--Chris

NPError
NP_GetValue(void *future, NPPVariable variable, void *value)
{
    NPError err = NPERR_NO_ERROR;
    printf("NP_GetValue %d\n", variable);
    switch (variable) {
    case NPPVpluginNameString:
        *((char **)value) = "The Plugin";
        break;
    case NPPVpluginDescriptionString:
        *((char **)value) = "This is a description";
        break;
    case NPPVpluginNeedsXEmbed:
        *((PRBool *)value) = PR_TRUE;
        break;
    default:
        err = NPERR_GENERIC_ERROR;
    }
                                                                                

    return err;
}

>
>
> Christopher Blizzard wrote:
>
>> Rob Lanphier wrote:
>>
>>> Hi all,
>>>
>>> I received the following question regarding the Helix Player from 
>>> one of
>>> the Christopher Blizzard on the Mozilla project: "Are you using the new
>>> xembed stuff that I've been working on?  Or is it an old Xt plugin?"
>>>
>>> I've cc'd him on this mail so just reply all to respond.
>>>
>> Both the Sun folks and I have been working on an interface so you can 
>> use an Xembed widget (and not have to use Xt, unless you want to.)  
>> If the plugin indicates that it supports Xembed, the browser will use 
>> a gtk_socket and pass off the xid of that socket as the 
>> window->window argument to setwindow.  I know that the Sun folks have 
>> been using this as the interface for their next JVM.  It should make 
>> focus a good bit more sane even across toolkits and make it much 
>> easier to host out of process plugins.
>>
>> I have exactly zero documentation on this, fwiw.  The only thing I 
>> can say is that it's completely compatbile with the old interfaces in 
>> the sense that older plugins should work as expected and new plugins 
>> have to indicate that they support this particular interface.
>>
>> --Chris
>>
>>> Thanks
>>> Rob
>>> -----Forwarded Message-----
>>> From: Christopher Blizzard <blizzard at mozilla.org>
>>> To: robla at robla.net
>>> Subject: Re: [Bug 178805] [gtk2] should port bug 154206 [hack to 
>>> make existing linux flashplayer & real binaries work with gcc 3.1 
>>> builds] to gtk2
>>> Date: Wed, 22 Oct 2003 16:54:36 -0400
>>>
>>> bugzilla-daemon at mozilla.org wrote:
>>>
>>>  
>>>
>>>> http://bugzilla.mozilla.org/show_bug.cgi?id=178805
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------- Additional Comments From robla at robla.net  2003-10-20 14:42 
>>>> -------
>>>> FYI, RealNetworks has released a new (prerelease) Mozilla plugin as 
>>>> part of the
>>>> Helix Player project (https://player.helixcommunity.org).  It's 
>>>> open source,
>>>> based on GTK2, and we've done builds with both GCC 2.95 and GCC 
>>>> 3.2, so many of
>>>> the annoying compiler mismatch issues should go away with the 
>>>> selection of the
>>>> right build.  We're planning on having a release quality build 
>>>> early next year.
>>>>
>>>>
>>>>
>>>>
>>>>   
>>>
>>> Are you using the new xembed stuff that I've been working on?  Or is 
>>> it an old Xt plugin?
>>>
>>> --Chris
>>>  
>>>
>>
>>
>> -- 
>> ------------
>> Christopher Blizzard
>> http://www.mozilla.org
>> ------------
>>  
>>
>


-- 
------------
Christopher Blizzard
http://www.mozilla.org
------------



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe at player.helixcommunity.org
For additional commands, e-mail: dev-help at player.helixcommunity.org