Ticket #811 (closed enhancement: moved)
Opened 2011-10-10T12:22:44-05:00
Last modified 2014-05-06T09:34:42-05:00
Include a stripped-down Fiji Script Editor
Reported by: | dscho | Owned by: | dscho |
---|---|---|---|
Priority: | major | Milestone: | imagej2-b8-analysis |
Component: | Scripting | Version: | |
Severity: | major | Keywords: | |
Cc: | curtis | Blocked By: | |
Blocking: | #1516 |
Description
Fiji's Script Editor uses the RSyntaxTextArea component (which is LGPL, but let's not depend on it in core IJ2). So we need to split out the RSyntaxTextArea support, probably using some sezpoz approach to have "JTextArea-based syntax highlighting providers" and using a very simple wrapper around JTextArea (which does not do syntax highlighting by default). We might even use the jeditsyntax ( http://syntax.jedit.org/) which is MIT licensed (and which is used by Micro-Manager's Script Panel), and either integrate it directly into the package or make jeditsyntax a new artifact.
Change History
comment:3 Changed 2012-09-06T19:02:42-05:00 by dscho
- Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta5
comment:4 Changed 2012-09-27T15:04:55-05:00 by dscho
Happily, RSyntaxTextArea is BSD-licensed in the meantime, so we postpone the down-stripping to a later point in time.
comment:6 Changed 2013-03-07T11:15:51-06:00 by bdezonia
- Milestone changed from imagej2-b7-ndim-data to imagej2-b8-analysis
comment:7 Changed 2013-03-22T15:48:57-05:00 by dscho
We have a functional Script Editor now.
These steps are missing for this ticket to be closed:
- all of Fiji's scripting languages need to be supported
- we should allow for 3rd-party Templates so that Fiji can ship its ImageJ 1.x-based ones
- Fiji needs to use the Script Editor itself (this most likely requires an ImageJ2 context, to be initialized at Fiji startup)
comment:8 Changed 2013-04-16T17:03:27-05:00 by dscho
- Cc curtis added
- Component changed from Other to Scripting
The ScriptService needs to be enhanced to open scripts in the editor (see 9f20b3ec6c297a356ec5da44d5ce85ff04327290). For this, we need to introduce a ScriptEditorService.
comment:9 Changed 2014-05-06T09:34:42-05:00 by curtis
- Status changed from accepted to closed
- Resolution set to moved
all of Fiji's scripting languages need to be supported
They are, except macros; see https://github.com/imagej/imagej-legacy/issues/7
we should allow for 3rd-party Templates so that Fiji can ship its ImageJ 1.x-based ones
See https://github.com/imagej/imagej/issues/78
Fiji needs to use the Script Editor itself