You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the groovy console's power is somewhat limited by the user's privileges, I think it would make sense to have users store their saved scripts into their own location. This location would show up on the "Open" dialog, in addition to the common/provided scripts & samples inside /etc/groovyconsole/scripts. Some benefit include
All users can save scripts, without the possibility to overwrite someone else's scripts
Custom scripts can be protected within the normal ACL process (by default, users have full access to their own user location under /home/users)
Users can modify sample scripts and save them within the tool, while they may only have read-access to the /etc/groovyconsole path
Possible difficulties:
browsedialog widget supports one tree root, but a custom tree loader may overcome this difficulty
browsedialog may not support having a dynamic path, but again, it may be overcome by a custom tree loader
The text was updated successfully, but these errors were encountered:
Since the groovy console's power is somewhat limited by the user's privileges, I think it would make sense to have users store their saved scripts into their own location. This location would show up on the "Open" dialog, in addition to the common/provided scripts & samples inside /etc/groovyconsole/scripts. Some benefit include
Possible difficulties:
The text was updated successfully, but these errors were encountered: