I can see the benefit of this approach, basically a driver can offer a stream of data packets that contain a representation of itself and 'canvas' clients could subscribe to this and render it.

If you can come up with a patch that is compatible with current functionality it would probably make it in to trunk. There are no plans for non compatible releases of player at the moment so it would have to only make additions to the current interfaces. I think this should be possible.


On 25 January 2010 22:55, David Olsen <razorunreal@gmail.com> wrote:

I've been having issues with the design of the graphics2d interface. I
think that rather than sending graphics data as commands, it should be
published as data.

Say, for example, you have two different graphics canvases, and you
want both of them to show graphics produced by a single driver.
Currently this is not possible, because the driver can only subscribe
to one of them. There are also issues when the driver producing
graphics is started before the one providing a canvas. The graphics
producer does not find the canvas at startup, so nothing is drawn. I
expect it's possible to poll periodically until a canvas is available,
but I would prefer this to be something the canvas does, not spread
through every graphics producer.

The current design works fine for stage but not other situations. For
example, consider adding graphics2d support to playerv.


The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
Playerstage-users mailing list