gvSIG feature requests #4761
Scripting preferences
| Status: | New | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Low | Spent time: | - | |
| Assignee: | - | |||
| Category: | Scripting | |||
| Target version: | - | |||
| gvSIG version: | 2.4.0 | Add-on resolve version: | ||
| Keywords: | Add-on resolve build: | |||
| Has patch: | Proyecto: | |||
| Add-on name: | Unknown | Hito: | ||
| Add-on version: |
Description
A great enhancement from the Scripting user perspective would be to have the Scripting preferences, just like in the case of EPSG Registry (jCRS), in order to have more control on the Scripting plugin initialization process which is is pretty slow at the moment. Further the Scripting composer usually opens in background (at least on Windows), so the whole process could be further optimized and more usable.
History
#1
Updated by Antonio Falciano over 6 years ago
A quick and dirty workaround in order to have the Scripting plugin ready to use at startup consists in an autorun.py script like the following:
# encoding: utf-8
from org.gvsig.andami import PluginsLocator
def main(*args):
''' Scripting composer '''
a = PluginsLocator.getActionInfoManager() \
.getAction("tools-scripting-composer")
a.execute()
It opens the Scripting Composer in background.#2
Updated by Joaquín del Cerro Murciano over 6 years ago
- Target version changed from 2.4.0-2850-final (rev. org.gvsig.desktop-2.0.220) to 2.5.1-3044
#3
Updated by Joaquín del Cerro Murciano about 4 years ago
- Priority changed from Normal to Low
#4
Updated by Álvaro Anguix about 4 years ago
- Target version deleted (
2.5.1-3044)