[sldev] Media Rendering Plugin Framework Interaction

[Lawson English]

Philippe (Merov) Bossut wrote:
> Hi Daniel,
>
> On Mon, Nov 9, 2009 at 2:16 PM, Daniel Whitely 
> <daniel.whitely at googlemail.com <mailto:daniel.whitely at googlemail.com>> 
> wrote:
>
>     I have some questions concerning the new Media Rendering Plugin Frame
>     Work.Is it possible to capture mouse and keyboard input on a prim
>     (i.e a
>     plane which represents an  application window) inside the virtual
>     world
>     and pass them to the external application that the prim
>     represents? This
>     would become handy for application sharing. I've read your MediaWiki,
>     but this functionality is nowhere described or clearly stated, aside
>     from some hints in the Media Plugin System Messages.
>
>     Is someone working on or already exists an project showing this
>     feature?
>
>
> First, the current implementation of the new pluginapi in Snowglobe is 
> not complete. In particular, we do not have the whole media-on-a-prim 
> stuff that has been developed internally. I have as a task to merge 
> that in trunk in the next Snowglobe 1.3 release 
> (https://jira.secondlife.com/browse/SNOW-301). First though, we need 
> to stabilize and ship 1.2...
>
> As for capturing input, it is possible to capture mouse events and 
> pass them to the plugin. If you look into the current Snowglobe trunk 
> code base, there is an example plugin doing just that in 
> indra/test_apps/llplugintest/demo_media_plugin_2.cpp (it's a simple 
> "draw brush" on the animated surface). There is however little 
> documentation on all this right now that is available. We are working 
> on it though.
>
> For keyboard capture though, I don't think there's any provision right 
> now to pass those events to the plugin. That's something that Aimee 
> already pointed out in her earlier experiments. Something to think 
> about then.
>

A little brainstorming about how future plugins might work and what they 
might be able to do:

http://wiki.secondlife.com/wiki/User:Saijanai_Kuhn/Plugins_discussion

In principle ANY internal event could be useful for some plugin or 
another. Of course, some events would need to be passed to and from the 
plugin at different points than other events, and some events might not 
currently be "events" in a unified sense, but everything from the raw 
(perhaps already parsed into LLSD) packets, to GUI events, raw 
mouse/keyboard events, and data from/to early parts of the rendering 
pipeline might be useful in some context.


Lawson