"RokuJoel" wrote:
... The Eclipse plugin, if you can get it working, is a major improvement in many ways though:
- Click on an error in the console and the source file/line will appear in the editor
- Source directory file-contents search
- Syntax Highlighting
- one-click build-to-the-same device
Right, "if you can get it working"

. Its dependence to particular version of Eclipse and general fragility have dissuaded me from touching it with a 10-foot pole. It's a systemic problem - complex systems break in complex ways - and i don't want to spend most of my time chasing peripheral problems (like crummy IDE module dependencies) from becoming central (breaking development).
The features you enumerated above are essential indeed! But i got them working already with a much simpler and more reliable setup. In OSX, it was some config tweaks to TextWrangler (a free
programmer's editor) and you got .BRS syntax highlighting, hot-key to package&deploy to device, naturally it has already the multi-file search, un/comment, text shift left/right, bracket-matching, support for JSON/XML/many more... and i think i got the jump-to-error-line too.
I was thinking of writing a "guide to lightweight Roku development" post after some fruitful PM exchange with squirreltown (what happened to that guy?) that made me realize not everybody feels comfortable keeping an open Terminal window. It actually made me improve my process by integrating the build script in the editor. (Anybody think they need specific instructions on how to do it? There is not much to it.) And that was umm... almost two years ago :shock:. Heck, i haven't even written you (RokuJoel) yet a personal "thank you" note for your above-and-beyond assistance publishing a channel before the end of 2015!