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) |
(→Code analysis) |
||
(19 intermediate revisions by the same user not shown) | |||
Line 13: | Line 13: | ||
<small>since 1.1M1</small> | <small>since 1.1M1</small> | ||
− | Tables are a key concept of Lua. It is mandatory for '' | + | Tables are a key concept of Lua. It is mandatory for ''LDT'' to handle them right to enable you to code at ease. |
=== Table Detection === | === Table Detection === | ||
Line 23: | Line 23: | ||
* Functions or Methods | * Functions or Methods | ||
* Nested tables | * Nested tables | ||
− | '''Note: | + | '''Note:''' If you click on table fields, you will get code navigation to their definition. |
[[Image:ScreenTypeDetection.png|center]] | [[Image:ScreenTypeDetection.png|center]] | ||
<center><small>Table detection</small></center> | <center><small>Table detection</small></center> | ||
Line 31: | Line 31: | ||
<small>since 1.1M1</small> | <small>since 1.1M1</small> | ||
− | Turn your table into a module quite simple: | + | Turn your table into a module is quite simple: ''simply return it''. As below. |
[[Image:ScreenModuleDetection.png|center]] | [[Image:ScreenModuleDetection.png|center]] | ||
<center><small>Module detection</small></center> | <center><small>Module detection</small></center> | ||
Line 41: | Line 41: | ||
<small>since 1.1M2</small> | <small>since 1.1M2</small> | ||
− | Auto-completion is now available after function calls or "object" invocations. It is no | + | Auto-completion is now available after function calls or "object" invocations. It is no longer disturbed by whitespaces. |
− | [[Image: | + | [[Image:ScreenEnhanceAutocompletion.png|center]] |
<center><small>Completion after invocation</small></center> | <center><small>Completion after invocation</small></center> | ||
Line 55: | Line 55: | ||
'''Note 2''': This feature could be disabled in the Lua preference page as it could impact autocompletion performance. | '''Note 2''': This feature could be disabled in the Lua preference page as it could impact autocompletion performance. | ||
+ | |||
+ | [[Image:ScreenGlobalsCompletion.png|center]] | ||
+ | <center><small>Completion on global variables</small></center> | ||
+ | |||
+ | [[Image:ScreenGlobalsPreferencePage.png|center]] | ||
+ | <center><small>Preference page</small></center> | ||
===Natural Completion On Strings=== | ===Natural Completion On Strings=== | ||
Line 60: | Line 66: | ||
<small>since 1.1M1</small> | <small>since 1.1M1</small> | ||
− | It now possible to trigger completion on <code>#string</code> | + | It now possible to trigger completion on <code>#string</code> variables without using the <code>string</code> module. You have completion for <code>mystring:sub(...)</code>. |
[[Image:RegularStringCompression.png|center]] | [[Image:RegularStringCompression.png|center]] | ||
Line 83: | Line 89: | ||
<small>since 1.1M2</small> | <small>since 1.1M2</small> | ||
− | The formatter is smarter when formating Lua | + | The formatter is smarter when formating Lua expressions written on several lines. |
+ | |||
+ | [[Image:ScreenFormatterEnhancements.png|center]] | ||
+ | <center><small>Formatted code</small></center> | ||
==Multi-files Template for Execution Environment== | ==Multi-files Template for Execution Environment== | ||
Line 89: | Line 98: | ||
<small>since 1.1M2</small> | <small>since 1.1M2</small> | ||
− | When you create your execution environment, it's now possible to include | + | When you create your execution environment, it's now possible to include templates made of severals files and folders, in order to help your users to bootstrap their projects. See the [https://bugs.eclipse.org/bugs/show_bug.cgi?id=407228 create Execution Environment tutorial] to get more details. |
− | '''Note''' | + | '''Note:''' Existing Execution Environments using the old archive format are still supported. |
==Debugger Introspection Extensibility== | ==Debugger Introspection Extensibility== | ||
Line 97: | Line 106: | ||
<small>since 1.1M2</small> | <small>since 1.1M2</small> | ||
− | 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 [ | + | The debugger can now be extended with inspectors to decode custom data. Inspectors allow the debugger to display data in a more human readable way. See the [[LDT/User_Area/Debugger/ValueDisplay|custom debugger introspection tutorial]] for further details. As explained in the tutorial, the inspector for LuaJIT's cdata is shipped with ''LDT''. |
+ | |||
+ | [[Image:Introspection.png|center]] | ||
+ | <center><small>Debugging a car object using a custom inspector</small></center> | ||
==Smarter Auto Close== | ==Smarter Auto Close== | ||
Line 103: | Line 115: | ||
<small>since 1.1M1</small> | <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 | + | ''Auto close'' got smarter and feels more natural. It is a silent improvement. If you did not notice it, it means it works just fine. |
Latest revision as of 12:11, 16 July 2014
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 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 is quite simple: 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 longer disturbed by whitespaces.
More Globals Variables Suggested
since 1.1M2
All globals variables declared in files of your project's buildpath/sourcepath are now suggested in autocompletion.
Note 1: This means LDT could propose you globals variables which may not be available at runtime.
Note 2: This feature could be disabled in the Lua preference page as it could impact autocompletion performance.
Natural Completion On Strings
since 1.1M1
It now possible to trigger completion on #string
variables 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 expressions 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 templates made of severals files and folders, in order to help your users to bootstrap 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 more human readable way. See the custom debugger introspection tutorial for further details. As explained in the tutorial, the inspector for LuaJIT's cdata is shipped with LDT.
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 means it works just fine.