You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (Jira)" <ji...@apache.org> on 2020/09/30 11:26:00 UTC
[jira] [Closed] (GROOVY-9133) Groovy Console could support an
AutoRun feature
[ https://issues.apache.org/jira/browse/GROOVY-9133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul King closed GROOVY-9133.
-----------------------------
Fix Version/s: 3.0.0-beta-2
Assignee: Paul King
Resolution: Fixed
Looks like I forgot to close this earlier. Thanks to everyone involved.
> Groovy Console could support an AutoRun feature
> -----------------------------------------------
>
> Key: GROOVY-9133
> URL: https://issues.apache.org/jira/browse/GROOVY-9133
> Project: Groovy
> Issue Type: Improvement
> Components: Groovy Console
> Reporter: Paul King
> Assignee: Paul King
> Priority: Major
> Labels: contrib
> Fix For: 3.0.0-beta-2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> To aid with visualisation of script runs, once a script execution is complete, a timer could be set to auto-trigger the next run.
> Perhaps an autorun delay (default to 1000 msec?) under preferences?
> Perhaps [en|dis]abled via Script -> Enable Autorun (similar to Enable indy compilation).
> Perhaps even once enabled, it still requires the user to kick off the first run manually. Similarly, if the source buffer is modified, it would await a further explicit run action from the user.
> In one sense, the same result could be achieved by the user having a loop with a delay but the idea here is to combine this feature with other visualisation features, e.g. "auto clear output on script run" and "visualisation of script results".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)