|
Us plugin developers, we need to test our code. But what process do we have to go through to test it?
Publish -> Install
You may find that simple but it becomes tedious as you start to debug your code and find more bugs, and glitches. The worst is when you made a typo. Each time you want to test a new version of your code, here's the process:
Publish -> Close place -> Update plugin -> Open a new place
What happens as we find more bugs? Glad you asked:
Publish -> Close place -> Update plugin -> Open a new place -> Publish -> Close place -> Update plugin -> Open a new place -> Publish -> Close place -> Update plugin -> Open a new place -> Publish -> Close place -> Update plugin -> Open a new place -> Publish -> Close place -> Update plugin -> Open a new place -> Publish -> Close place -> Update plugin -> Open a new place -> Publish -> Close place -> Update plugin -> Open a new place -> Publish -> Close place -> Update plugin -> Open a new place
Get my point yet? It becomes annoying. In fact, I love making plugins, but this is one thing that discourages me. You could be thinking I'm lazy, but the time adds up:
Publish: 30 sec for it to load the window, 10 seconds to actually update
close & update: update time can range, it really depends on how big the plugin is. It's usually 5-30 seconds
open a new place: about 5 seconds to load it up.
So that's 1 min and 15 seconds to simply set up a good environment for testing the plugin. So once we find, say 10 bugs, that time has now been increased to
12 min and 30 sec
That's 12 min wasted setting up the place!!! Not to mention the initial creation setup for publishing where you have to add a name and description.
But what if there was a better way to do this? What if we could immediately load up a plugin from a script/model to test it without needing to publish/update/change places.
I propose a spot under the plugins tab of the RibbonBar menu of studio (I don't know SystemMenu so I have no idea where I'd put this) a "Plugin Simulator" subtab, which would have, by default, nothing.
How would we add a plugin to simulate? Open up the context menu of a script (right-click menu) and press the NEW option, "Simulate as Plugin" which would replace whatever was in the Plugin Simulator subtab with this plugin.
Allowing us to do this would save a lot of time, and make it easier to test. Not to mention it reduces the risk of people taking it when you publish and have to install it yourself.
I will start the supports :D
Support Ratio; 1:0 |
|
|
|
|
XenonLiJoin Date: 2009-08-19
Post Count: 5013 |
support, it was really hard to make my terrainify plugin because of the long testing cycle |
|
eLunateJoin Date: 2014-07-29
Post Count: 13268 |
Support. I've not even bothered making a plugin yet simply because I can't test if I'm using the plugin keyword properly. |
|
|
I'm not a plugin developer myself, but I can see your pain.
Support |
|
North1233Join Date: 2014-02-06
Post Count: 9978 |
OP supported his own idea.
THIS IDEA IS NOW INVALID, EVERYONE LEAVE!
Hand over the cheese!~If the tortise beat the hare, why won't my turtle beat my dog? |
|
lokkutJoin Date: 2009-03-18
Post Count: 1794 |
This is easy to get around, just make it a lua script and run it directly from your PC.
You need to check if things are possible, before complaining that it's not. |
|
soviedJoin Date: 2012-02-09
Post Count: 4359 |
support |
|
|
Support Ratio; 7:0
@lok
That's technically unsupported by roblox. It's the deprecated way of making plugins a while ago, and even that takes a few seconds to setup. This way is quick, efficient, and supported.
I also tend to steer away from deprecated stuff. |
|
|
KapKing47Join Date: 2012-09-09
Post Count: 5522 |
Support
"My Life is going Good... but..." |
|
NyxisJoin Date: 2012-11-15
Post Count: 3374 |
Support.
Even though publishing a plugin to test it is not necessary.
You can simply:
1. Create a new Text Document in the Plugins folder
2. Paste the script into the document
3. Save it as a ".lua" file
4. Restart Studio |
|
|
Another genius idea, support.
siggy:Destroy() -- Twitter @umaybleed |
|
|
|
NeonifiJoin Date: 2014-04-12
Post Count: 459 |
Support, I'm no plugin-maker, but it's annoying when I want to use a plugin and have to go through a ton of crap just to use it, to find out it's terrible although the comments spam it's good [bot much?].
'I rest my case.' |
|
SpamroachJoin Date: 2012-11-12
Post Count: 2775 |
An idea to make something quicker and easier? Support. |
|
|
|
PvNJoin Date: 2010-04-10
Post Count: 22145 |
no cuz i want to ruin da ratio |
|
|
@PvN
So you're no supporting the ratio, not the idea :D
Name one bad thing about the idea ;D |
|
|
Support because I found this on google when I searched for a way to test plugins without this cycle.
Also necrobump.
~Upload code to codepad-dot-org with Lua syntax highlighting to preserve indentation and make it easier to read!~ |
|
|
Support Ratio; 14:0
btw @nice In the meantime use the plugin hotswap. It works miracles. |
|