Zombie alert: the dead glx2 script editor has come back to life.

From the release notes:

2016.09.10 GLX2 3.0.19



Fraser Gordon and I sat down for half an hour at the LiveCode 16 conference in Edinburgh and figured out what was causing the problem with taking up the CPU cycles. The engine problem still isn't fixed, but that gave me enough knowledge of what's going on to come up with a workaround for it, so I'm bringing this project back on line.

http://quality.livecode.com/show_bug.cgi?id=16880



new features:



Line numbers. Yes, finally.

Unit test generation. Click a command declaration, then select from the contextual menu. The tests will be created in a file named "tests.text" in the same directory as the stack file.

Documentation generation. Inline javadoc-style - select from the contextual menu.

Pressing enter on a compiled script closes the tab ala the built-in editor. I never thought that was a thing.



bugs fixed:



Lots of little things I had time to fix up while waiting.

For one thing, the splitter bar between the handlers and script panels is more accessible now.



known issues:



Line wrapping doesn't change the line numbering. If you turn on line wrapping, the line numbers after a line wraps will be wrong. I don't currently know any way of telling when a line is being wrapped.

Still some problems recognizing that text inside a block comment is not actionable.

Swapping back and forth between glx2 and the IDE's script editor gets a bit wonky.

Very little testing has been done on any Windows platform. If it works, it works.


Also, I haven't quite figured out placement of the status bar in conjunction with Richard Gaskin's 4Wdevolution vertical menu bar.

https://bitbucket.org/mwieder/glx2/downloads

--
 Mark Wieder
 ahsoftw...@gmail.com

_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to