Re: AW: AW: [Gnash-dev] 0.8.3 target date?

[Udo Giacomozzi]

Hello Benjamin,

Friday, April 4, 2008, 10:09:32 AM, you wrote:
BW> In that case it's probably advisable to implement the virtual methods just 
to
BW> remove the unimplemented log message ("not yet implemented in this gui"),
BW> as it never will be.

Agree, committed...


BW> Is there supposed to be a difference at all between plugin and standalone
BW> handling of FsCommands? Or is the plugin really supposed to quit if it 
receives
BW> that command?

No, "quit" makes only sense for the standalone player (think Flash
being used for a presentation CD or something, not for web).


BW> There is a generic enable/disable directive in gnashrc, but that may not be
BW> good enough if the plugin is supposed to handle all FsCommands. I'd want
BW> it not to quit, for instance, but to handle JavaScript

That's why I said that it's wrong to ignore *all* fscommand calls for
the plugin. A plugin should not (cannot) "quit". I'm not sure if a
plugin can do fscommand("fullscreen") because normally you do
  Stage["displayState"] = "fullScreen";
for that (even if embedded in a web page).

BW> (though that is also done through getURL, isn't it?).

Yes, but it's up to the Flash developer which method to use.


Udo