Would it be possible to add a "devmode" option to the plugin.ini file?
So that instead of compiling the plugin at startup/plugin enable, it would compile the plugin whenever its activated?
That would make it so much easier to create plugins.
[SOLVED] Option to have plugin run in "Dev mode"
Moderator: kfury77
Forum rules
Please follow these guidelines when posting feature requests. This will help to increase the value of your contribution.
Please follow these guidelines when posting feature requests. This will help to increase the value of your contribution.
- Do not create new topics for already requested features. Add your comments to the existing feature request topics instead;
- Create separate topic for each feature suggestion. Do NOT post a number of non-related feature suggestions in a single topic;
- Give your topic a meaningful title. Do NOT create topics with meaningless titles, such as "My Suggestion" or "My Problem".
[SOLVED] Option to have plugin run in "Dev mode"
When creating plugins for Webuilder, the most time consuming thing it the endless disable/enable of the plugin in order to activate/see code changes.
Would it be possible to add a "devmode" option to the plugin.ini file?
So that instead of compiling the plugin at startup/plugin enable, it would compile the plugin whenever its activated?
That would make it so much easier to create plugins.
Would it be possible to add a "devmode" option to the plugin.ini file?
So that instead of compiling the plugin at startup/plugin enable, it would compile the plugin whenever its activated?
That would make it so much easier to create plugins.
Last edited by pmk65 on Sun Apr 17, 2016 12:08 pm, edited 1 time in total.
There are 10 types of people in the world: Those who understand binary and those who don't.
Re: Option to have plugin run in "Dev mode"
I know what you mean, I have to deal with the same problem. I'll think about what could be done.
Blumentals Software Programmer
Re: Option to have plugin run in "Dev mode"
If you could access the "Manage plugins -> Disable/Enable" functionality from within plugin code, then we could make a "Save plugin" plugin 
So that when it has saved the code it would call the Disable and then the Enable functions. That would be a fairly simple way to solve the "problem".
So that when it has saved the code it would call the Disable and then the Enable functions. That would be a fairly simple way to solve the "problem".
There are 10 types of people in the world: Those who understand binary and those who don't.