Releasing an editor utility widget as a product?

Hey! I’m creating an editor utility widget that will serve as an interface for my server. What are some methods that can be used to make this product more easily distributable while maintaining security?

My current plan was to offer a download link to a folder that contains my editor utility widget, along with the necessary structs and build files. The user could run the widget, and send/receive web requests to my protected server.

Is there a way that I can distribute just the compiled object files, or even just the editor widget without including the source files? Is there a more accessible option for the user like installing a plug-in that runs my widget in a window?

I’m hoping to make the process as user-friendly as possible while abstracting as much of the source code away from the user; within reason.

So far I have an editor utility widget that instantiates other editor utility widgets inside of it, each of which has a bit of client side functionality before calling a python script on my server. I could continue to push more functionality to my server, but would like to avoid it if possible. I don’t suspect that hiding the design heirarchy from the user is possible unless the child editor utility widgets were only compiled object files as well.

Thanks, and stay secure. :closed_lock_with_key:

I don’t think it can be more secure than what you currently have. I think you are ineligible for posting this on the marketplace due to their content policy, so you would need to host the files yourself.

Basically if you have created a proper and secure server which allows the editor utility widget to only read from the server and not change underlying data, you will be fine in most cases! :slight_smile:

Remember, if someone has access to the build, they could change the underlying code of the utility widget, causing havoc on your server, etc.

Is there a way for the user to have just a built version of the editor utility widget? Something that they can run?

Depends on how it is built, and I am a little rust on these details. If you touch the source code and widget relies on C++ code which needs to be built, then it’s likely not possible. See if you can turn the code into a code plugin which the user can enable. Then they would be able to add it to any project than starting with your project build from scratch.

Thanks for the tip. I’ll look into code plugins next.

My project has a bit of C++ code but its mostly using blueprints and the editor widget’s node graph.