How to speed-up plugin testing

For discussion and help with the Construct 3 Plugin SDK

Post » Tue Apr 11, 2017 4:21 am

To develop and test a plugin, designer will
1. edit runtime.js in text editor
2. zip folder (rename to "c3addon")
3. open C3 edior
4. install c3addon
5. close and open c3 editor again
6. open a test c3p file and run it
(7. find bug, repeat from step 1 again)

Is it possible to reduce these steps to speed up plugin testing?
For example
- install addon from local folder without zip/rename
- update new addon on-fly without reopen c3 editor again
B
108
S
26
G
258
Posts: 4,430
Reputation: 145,179

Post » Tue Apr 11, 2017 5:02 am

+1

and another request why there is alot of files 5 files to edit for each plugin , why not simply merge the json files together and the JS files together ? , like in C2 , edittime.js = 2 json files and the runtime = 3 js files ?
B
28
S
9
G
9
Posts: 294
Reputation: 7,064


Return to Plugin SDK

Who is online

Users browsing this forum: No registered users and 0 guests