AW: [Gnash-commit] gnash ChangeLog server/as_object.cpp server/as_...

[Benjamin Wolsey]

> Log message:
>         * server/gnash.h: add "interfaceEventCallback" callback for passing
>           AS events to the gui.
>         * server/as_object.{cpp,h}: make callback a static method of as_object
>           class, as that's where it's used.
>         * gui/Player.{h,cpp}: register Player as a listener for interface 
> event
>           callbacks and pass on to gui.
>         * gui/gui.{cpp,h}: make Mouse.hide and Mouse.show unimplemented in the
>           gui, not in mouse_as_object.
>         * server/asobj/Mouse.cpp: send mouse events using callback.
> 


This allows passing actionscript events such as mouse hide / show and the AS3 
stage.stageDisplayState to whatever happens to be listening: normally the GUI.

It's implemented as a callback because a direct call to the gui code would make 
it (a) impossible to use gnash as a standalone library or (b) necessary to have 
a gui library, which would also always have to be built. This way means that 
gprocessor gets a reprieve and that python bindings will still be useable.

There are two arguments (event and argument) passed, both as strings. This 
seems slightly less neat than using an enumeration of known events, but makes 
it much easier to implement custom AS classes, which would simply have to pass 
a string that a custom frontend would listen for.

I would envisage events being sent in a form related to the actionscript: 
Mouse.hide sends Mouse.hide as its event; Stage.stageDisplayState something 
like (*callback)("Stage.stageDisplayState", "StageDisplayState.FULL_SCREEN"); 
(though I haven't looked into that actionscript function at all). The gui class 
should then work out what to do with it.

Any comments on the interface and instances of other actionscript functions 
that need to access the gui would be welcome while it's still no trouble to 
change it.


bwy


      E-Mails jetzt auf Ihrem Handy.
www.yahoo.de/go