Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "LDT/User Area/New Noteworthy/New Noteworthy 1.1"
(→Smarter Completion Trigger) |
(→Multi-files Template for Execution Environment) |
||
Line 84: | Line 84: | ||
<small>since 1.1M2</small> | <small>since 1.1M2</small> | ||
− | + | When you create your execution environment, it's now possible to include template made of severals folders and files, in order to help your users to initialize their projects. See the [https://bugs.eclipse.org/bugs/show_bug.cgi?id=407228 create Execution Environment tutorial] to get more details. | |
+ | |||
+ | '''Note''': Existing Execution Environments using the old archive format are still supported. | ||
==Debugger Introspection Extensibility== | ==Debugger Introspection Extensibility== |
Revision as of 13:35, 30 October 2013
Contents
New & Noteworthy 1.1
Lighter Documentation
since 1.1M1
It is now possible to describe code with significantly less documentation. We analyze the code, filling documentation blanks from it, making documentation more fluent.
Code analysis
since 1.1M1
Tables are a key concept of Lua. It is mandatory for Koneki LDT to handle them right to enable you to code at ease.
Table Detection
since 1.1M1
We managed to summarize #table
s nicely in outline. It is obviously now possible to enjoy table content.
- Fields
- Functions or Methods
- Nested tables
Note:' If you click on #table
fields, you will get code navigation to their definition.
Module Detection
since 1.1M1
Turn your table into a module quite simple: it is simply return it. As below.
Completion Enhancements
Smarter Completion Trigger
since 1.1M2
Auto-completion is now available after function calls or "object" invocations. It is no more disturbed by whitespace.
More Globals Variables Suggested
since 1.1M2
On auto-completion, globals variables from the others files in the buildpath (also called sourcepath) of your project will be suggested but at a lower relevance than the others variables. Be careful that the globals variables may not be initialized where suggested, using it without safe checks may thrown runtime errors.
Note: The suggestion of globals from others files can be disabled in the Lua preference page. Disabling this feature can enhance global performances.
Natural Completion On Strings
since 1.1M1
It now possible to trigger completion on #string
variable without using the string
module. You have completion for mystring:sub(...)
.
#string
variable from assignment#string
variable from explicit typingBetter Error Handling
since 1.1M1
To speed up syntax error troubleshooting, the output given is now the Lua 5.1 interpreter one. During the process, syntax error detection became about 10 times faster.
Formatter Defaults
since 1.1M1
For a better out of the box experience, formatter now uses Lua's 2 spaces indentation standard by default.
Formatter Enhancements
since 1.1M2
The formatter is smarter when formating Lua expression written on several lines.
Multi-files Template for Execution Environment
since 1.1M2
When you create your execution environment, it's now possible to include template made of severals folders and files, in order to help your users to initialize their projects. See the create Execution Environment tutorial to get more details.
Note: Existing Execution Environments using the old archive format are still supported.
Debugger Introspection Extensibility
since 1.1M2
The debugger can now be extended with inspectors to decode custom data. Inspectors allow the debugger to display data in a human readable way. See the custom debugger introspection tutorial for further details. As explained in the tutorial, the inspector for LuaJIT cdata is shipped in the product.
Smarter Auto Close
since 1.1M1
Auto close got smarter and feels more natural. It is a silent improvement. If you did not notice it, it indicates it works just fine.