We'll continue to update the wiki page as we learn more about what additional information folks need.We have put together much more detail on the various debugging options available to plugin developers on a page discussing how to set up a plugin development environment.
Setting up an Indigo Plugin Development Environment
Debugging
The debugging section also describes a new EXPERIMENTAL (as of right now) method to do real-time debugging of a plugin running on an Indigo server over IP (i.e., running the PyCharm debugger on machine other than the one running the Indigo server.) Although experimental, it has been running very stably in testing.
How to setup IDE and workflow to develop an Indigo Plugin
Re: How to setup IDE and workflow to develop an Indigo Plugi
Cross posting this one given the context of the above discussion.
I came here to drink milk and kick ass....and I've just finished my milk.
My Plugins and Scripts
My Plugins and Scripts
Re: How to setup IDE and workflow to develop an Indigo Plugi
Thanks Jay.
I've had a look at the Wiki post. Much appreciated.
My basic problem still remains in that the Indigo license I have runs on a standalone server (Mac Mini), which runs in a headless mode.
Is there any way to do develop and test the plugins on my dev machine and once ready move to the main server.
I can try and develop using a VNC session to Mini, but that is less than ideal. And in fact borders on painful. In effect, it involves setting up the server as a dev machine (with all tools etc.). Plus keystrokes etc are laggy and it is a pretty average experience to develop a plugin that way.
Like a lot of the other licensed software, is there a merit in considering a "dev" license of some sort Indigo?
I've had a look at the Wiki post. Much appreciated.
My basic problem still remains in that the Indigo license I have runs on a standalone server (Mac Mini), which runs in a headless mode.
Is there any way to do develop and test the plugins on my dev machine and once ready move to the main server.
I can try and develop using a VNC session to Mini, but that is less than ideal. And in fact borders on painful. In effect, it involves setting up the server as a dev machine (with all tools etc.). Plus keystrokes etc are laggy and it is a pretty average experience to develop a plugin that way.
Like a lot of the other licensed software, is there a merit in considering a "dev" license of some sort Indigo?
- matt (support)
- Site Admin
- Posts: 21502
- Joined: Mon Jan 27, 2003 1:17 pm
- Location: Texas
- Contact:
Re: How to setup IDE and workflow to develop an Indigo Plugi
I just sent you an email and added an extended trial license to your account.