[eq-dev] Affecting Collage objects outside an Equalizer application

[Stefan Eilemann]

On 20. Feb 2012, at 18:08, cpapado [via Software] wrote:

> However, that's a bit of a clunky approach. So I was wondering to what extend is collage decoupled from EQ and whether I can use collage from outside of an EQ application.

Collage is, as a library, completely independent of Eq. It is not as stable yet, but we definitely want it to be used independently. The object API can be considered fairly stable by now.

>  I'd like to initialize collage, have it connect as a client to the server running on the application node, then map my distributed objects and affect them. After that, I'd like to have all my render clients (and application node) sync to the latest version of the distributed object and use that for rendering. 
> 
> Of course I got no clue on where to begin :P. 

Why do you want to connect to the server and not directly to the application?

Your application then has to open a listener connection with a well-defined port, simply add a connection description to your eq::Client before initLocal().

Then either the app or your qt application has to create and register the master objects using LocalNode::registerObject (Client is a LN) and the other one has to map it using mapObject. My feeling is the Eq app should be the master. The Qt app calls a Object::commit after changing stuff. The Eq app either subscribes to Object::notifyNew(Head)Version and redraws on changes, or simply sync()s all objects before each frameStart. Make sure you set the appropriate dirty bits on master objects to redistribute slave commit changes.

Section 9 of the Programming Guide has more background information. Feel free to ask more detailed questions when things are unclear.


HTH,

Stefan.



--
View this message in context: http://software.1713.n2.nabble.com/Affecting-Collage-objects-outside-an-Equalizer-application-tp7301888p7302042.html
Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com.