Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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"
| Line 2: | Line 2: | ||
== Lighter Documentation == | == Lighter Documentation == | ||
| + | |||
| + | <small>since 1.1M1</small> | ||
It is now possible to describe code with significantly ''less'' documentation. We analyze the code, filling documentation blanks from it, making documentation more ''fluent''. | It is now possible to describe code with significantly ''less'' documentation. We analyze the code, filling documentation blanks from it, making documentation more ''fluent''. | ||
| Line 8: | Line 10: | ||
== Code analysis == | == Code analysis == | ||
| + | |||
| + | <small>since 1.1M1</small> | ||
Tables are a key concept of Lua. It is mandatory for ''Koneki LDT'' to handle them right to enable you to code at ease. | 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 === | === Table Detection === | ||
| + | |||
| + | <small>since 1.1M1</small> | ||
We managed to summarize <code>#table</code>s nicely in outline. It is obviously now possible to enjoy table content. | We managed to summarize <code>#table</code>s nicely in outline. It is obviously now possible to enjoy table content. | ||
| Line 22: | Line 28: | ||
=== Module Detection === | === Module Detection === | ||
| + | |||
| + | <small>since 1.1M1</small> | ||
Turn your table into a module quite simple: it is ''simply return it''. As below. | Turn your table into a module quite simple: it is ''simply return it''. As below. | ||
| Line 30: | Line 38: | ||
===Completion trigger enhancement=== | ===Completion trigger enhancement=== | ||
| + | |||
| + | <small>since 1.1M2</small> | ||
Auto-completion is now available just after a table index have been called or invoked. White spaces after or before dots and colons are also supported and will not break auto-completion anymore. | Auto-completion is now available just after a table index have been called or invoked. White spaces after or before dots and colons are also supported and will not break auto-completion anymore. | ||
===More globals variables are suggested=== | ===More globals variables are suggested=== | ||
| + | |||
| + | <small>since 1.1M2</small> | ||
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. | 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. | ||
| Line 40: | Line 52: | ||
===Natural Completion On Strings=== | ===Natural Completion On Strings=== | ||
| + | |||
| + | <small>since 1.1M1</small> | ||
It now possible to trigger completion on <code>#string</code> variable without using the <code>string</code> module. You have completion for <code>mystring:sub(...)</code>. | It now possible to trigger completion on <code>#string</code> variable without using the <code>string</code> module. You have completion for <code>mystring:sub(...)</code>. | ||
| Line 49: | Line 63: | ||
==Better Error Handling== | ==Better Error Handling== | ||
| + | |||
| + | <small>since 1.1M1</small> | ||
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''. | 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== | ==Formatter Defaults== | ||
| + | |||
| + | <small>since 1.1M1</small> | ||
For a better out of the box experience, formatter now uses Lua's ''2 spaces indentation'' standard by default. | For a better out of the box experience, formatter now uses Lua's ''2 spaces indentation'' standard by default. | ||
==Formatter Enhancements== | ==Formatter Enhancements== | ||
| + | |||
| + | <small>since 1.1M2</small> | ||
The formatter is smarter when formating Lua expression written on several lines. | The formatter is smarter when formating Lua expression written on several lines. | ||
| Line 62: | Line 82: | ||
==Template of Execution Enthronement can contains more than one file== | ==Template of Execution Enthronement can contains more than one file== | ||
| − | The Execution Environment archive format has changed to allow to create projects initialized with default folders and files. Existing Execution Environments using the old archive format are still supported. See the [ | + | <small>since 1.1M2</small> |
| + | |||
| + | The Execution Environment archive format has changed to allow to create projects initialized with default folders and files. Existing Execution Environments using the old archive format are still supported. See the [https://bugs.eclipse.org/bugs/show_bug.cgi?id=407228|create Execution Environment tutorial]. | ||
==Debugger Introspection Extensibility== | ==Debugger Introspection Extensibility== | ||
| − | The debugger can now be extended to decode custom user data. See the [ | + | <small>since 1.1M2</small> |
| + | |||
| + | The debugger can now be extended to decode custom user data. See the [https://github.com/jdesgats/org.eclipse.koneki.ldt/blob/newintrospection/libraries/luadbgpclient/docs/inspectors.md| custom debugger introspection tutorial] for further details. As explained in the tutorial, the inspector for LuaJIT user-data is shipped in the product. | ||
==Lua Shebang== | ==Lua Shebang== | ||
| + | |||
| + | <small>since 1.1M2</small> | ||
The Lua shebang is now supported by the Lua Editor. | The Lua shebang is now supported by the Lua Editor. | ||
==Smarter Auto Close== | ==Smarter Auto Close== | ||
| + | |||
| + | <small>since 1.1M1</small> | ||
''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. | ''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. | ||
Revision as of 12:45, 30 October 2013
Contents
- 1 New & Noteworthy 1.1
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 #tables 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
Completion trigger enhancement
since 1.1M2
Auto-completion is now available just after a table index have been called or invoked. White spaces after or before dots and colons are also supported and will not break auto-completion anymore.
More globals variables are 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.
Template of Execution Enthronement can contains more than one file
since 1.1M2
The Execution Environment archive format has changed to allow to create projects initialized with default folders and files. Existing Execution Environments using the old archive format are still supported. See the Execution Environment tutorial.
Debugger Introspection Extensibility
since 1.1M2
The debugger can now be extended to decode custom user data. See the custom debugger introspection tutorial for further details. As explained in the tutorial, the inspector for LuaJIT user-data is shipped in the product.
Lua Shebang
since 1.1M2
The Lua shebang is now supported by the Lua Editor.
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.