GroovyConsole

• 

  Zendesk API User

  • 12. März 2013 11:47

  Author: mkresse - 3/12/2013 11:47
  

  Works great, especiallly for quickly trying out new stuff. Using groovy's closures, one can avoid this verbose nested try-setlock-finally-try-setlock-idiom in a nice way.

  However, a few points for improvement could be:

  • printing the stacktrace for Exeptions, currently only the Exception.getMessage() is displayed
  • adjusting size of textarea when being resized (ex. via simple borderlayout or even jsplitpane?)
  • CTRL+RETURN as an additional shortcut for running the script (commonly used in cases like this)

  Besides this, I am perfectly happy - thanks for sharing your work :-)

  0
• 

  Zendesk API User

  • 12. März 2013 15:50

  Author: stephan - 3/12/2013 15:50
  

  Thanks for your input. The display of the areas after resize will be fixed in the next version. The CTRL-RETURN shortcut will not be possible, as this already triggers the code completion in the editor. Can you please give me an example for the missing stacktraces?

  0
• 

  Zendesk API User

  • 14. März 2013 10:13

  Author: mkresse - 3/14/2013 10:13
  

  Sure: throw new Exception("no stacktrace"); :smileygrin:

  Using oracle jdk 1.7 on windows 7, this does not print a stacktrace, neither on the java console nor the groovy-result-field.

  BTW, if missing code completion is not an issue, http://groovy.codehaus.org/Groovy+Console might be an alternative.

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.