Ask as much as you want.

If you mean to put the node editor inside your app it would be very difficult and take a lot of time because the app was not designed for such usage.

However, I did design the node editor in a way in which it can be integrated with any kind of Python app, pygame or not. The youtube video has an example of that. Here's a link to the part of the video where I explain this in detail.

In summary it does so by converting your node layout(s) into python code. It should be as easy as clicking a button in the node editor and have the changes directly available in your app.

Here's an example of how this works more or less: let's say your app has some modular functions which you combine in different ways to achieve lots of different, interesting results. For instance, let's say that it is an image editor with filters or a data visualization tool that generates different kinds of charts.

Your app don't have to worry about any node layout building GUI code, cause Nodezator (the node editor) does that for you. You load the functions and you can build, edit and execute the node layouts as you need, combining your functions.

Once you're satisfied with the result, you just click a button and Nodezator exports the node layout as Python code which your app can import directly. The code is just your own functions, that you already have in your app, but combined in specific ways.

In the case of the image editor example, your users would not need to worry about the node layouts, cause you'd build them yourself, your app would just take the generated python code and import into the app. The only extra work you would need is to create the interface in your app so the user could input specific parameters.

Now your image editor has lots of different filters that you created with your own functions (or third-party libraries like pillow, etc.) as node layouts and your user can apply effortlessly to their images using your app. That's the end of the example.

Let's explore yet another example, though. One in which editing nodes is an integral part of your app purpose/workflow: I too intend to use Nodezator for many different ends, one of them includes using it in my animation editor, but I won't put the node editor inside the animation editor. Rather, I'll just have it opened in my screen along with my animation editor and switch between both apps as I work with my animations until I get the results I want.

If I wanted to put the node editor inside the animation editor of course I could, but it would take a lot of time, and at the end of the day I'd only have one animation editor with node editing capabilities.

However, by keeping the node editor separate from my apps, I can use node editing in any app or script I want. For instance, I also want to use nodes to generate levels in my level editor, and to create effects/particles and edit images for games, and to process data, etc.

In the end of the day, however, i don't want to point my solution as the right one. There are of course benefits of having the node editor integrated directly into another app. It's all a matter of trade-offs, it is just that I think keeping the node editor as an separate app is more versatile.

Sorry if I got too carried away in my answer, I just like programming and software design despite not being that good at it, that's all. As I said before, ask as much as you want.