> This is the idea behind Renderer and Application implementing co::ObjectFactory and using co::ObjectMap to add/update/remove shared object -- which I just realize is not exposed through the API in Sequel, even though the init and frame data objects are managed through this mechanism. Have a look at the aforementioned classes, and I'm happy to figure out an API to expose the ObjectMap API.
Yes yes... I actually had a look a while ago playing around with seq and I also realized that this would be the way to go i.e trying to expose this ObjectMap API somehow so good to know that we are on the same page :) >I'm happy to help - just ask ahead. I will ! thanks ! >I would like to move forward with Sequel using a concrete use case like yours to provide a stupidly simple API for 90% of the Equalizer features. I am more than happy to help and proceed with this forward ... I really believe there is a huge potential for various Eq use cases .. I ll be away from office for the next 2 weeks but I am getting back to you as soon as I return.. Best, Petros ----- Creative Engineer Ars Electronica Futurelab [email protected] -- View this message in context: http://software.1713.n2.nabble.com/Pixel-Coordinates-configuration-file-OF-Equalizer-tp7583381p7583439.html Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com. _______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
