The Op paradigm seems to be pretty tied to being associated with a Node*, so it may be tough to fool it into working with another object without having the header for the Node class. I suppose you could probably put together your own stub class with all the proper entry points through trial and error though.
There's also the question of how an Op's relationship to a Node* works when Op::create is called with only a class name. I would be inclined to think that a new Op would expect to inherit a Node* from another existing Op (from which create would normally be called), but it could be that the data would just be initialized to NULL, and that the Op class already knows how to deal with that scenario. Definitely an interesting idea though. -Nathan From: Johannes Saam Sent: Monday, December 29, 2014 11:21 AM To: Nuke plug-in development discussion Subject: Re: [Nuke-dev] Using nukes own ops outside of nuke Yeah thats what i was hoping to do... the question is WHAT is the exact order nuke calls it in? has anyone ever tried that sucessfully? On Mon, Dec 29, 2014 at 11:13 AM, Steve Booth <[email protected]> wrote: An Op is just a class. By Isolation, it can be instantiated and called by any other C++ class, but you'd have to call it in exactly the same way Nuke does, and you would have to provide definitions for all classes and methods it utilizes. Steve From: [email protected] [mailto:[email protected]] On Behalf Of Johannes Saam Sent: Monday, December 29, 2014 10:46 AM To: Nuke plug-in development discussion Subject: [Nuke-dev] Using nukes own ops outside of nuke Hey ! Merry christmas everyone :) I have a little bit of an RnD theoretical question.... Could we use nuke ops outside nuke? Meaning could i have an Iop input that i call validate request and engine on myself and feed it data? And of course get the data afterwards? Meaning could i use a nuke blur or even better a nuke network and use it to process other data that i specify? Its more of a theoretical one but any thoughts are greatly appreciated. Rock on jo _______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev -------------------------------------------------------------------------------- _______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
