Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "LDT/User Area/New Noteworthy/New Noteworthy 1.2"

 
(20 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
<small>since 1.2M1</small>
 
<small>since 1.2M1</small>
  
−
By adding a file ".doclua" describing an API in lua documentation language in your project sourcepath, you will have auto-completion on the described API.  
+
By adding a <code>.doclua</code> file describing an API in Lua Documentation Language in your project ''source path'', you will have auto-completion for described API.  
  
−
''Screenshoot''
+
[[File:ScreenDoclua.png|center]]
−
* Script explorer containing a doclua file
+
−
* Editor with auto-completion on the lib described in the doclua file.
+
  
 
== Debugging fix and enhancements ==
 
== Debugging fix and enhancements ==
Line 15: Line 13:
 
<small>since 1.2M1</small>
 
<small>since 1.2M1</small>
  
−
Here some fixes to improve debugging experience and troubleshooting:
+
Here are some fixes to improve debugging experience and troubleshooting:
 
* Avoid a crash when evaluating an expression from the watch view.
 
* Avoid a crash when evaluating an expression from the watch view.
−
* Use of the interpreter Lua path if the ''LUA_PATH'' environment variable is not set.
+
* Use of interpreter's <code>LUA_PATH</code> if <code>LUA_PATH</code> environment variable is not available.
 
* The debugger now logs his version and his connection status.
 
* The debugger now logs his version and his connection status.
−
* Better error loging during remote debug sessions.
+
* Better error logging during remote debug sessions.
−
 
+
[[File:ScreenDebuggerVersion.png|center]]
−
''Screenshoot''
+
−
A screen of the debuggers logs in the consoleVIew ?
+
  
 
== Extending a type ==
 
== Extending a type ==
Line 28: Line 24:
 
<small>since 1.2M1</small>
 
<small>since 1.2M1</small>
  
−
Using the '''@extend''' keyword in a module or type will extend it with all the field, functions of the given super type.
+
Using the <code>@extend</code> keyword in a <code>module</code> or <code>type</code> will extend it with all fields and functions of given super type.
−
See [[detailed documentation]].
+
See [[LDT/User_Area/Documentation_Language#Type_comment_block| detailed documentation]].
  
−
''Screenshoot''
+
[[File:ScreenExtendingType.png|center]]
−
Show autcompletion on a super field just after the @extend keyword.
+
  
−
== Handleing table field ==
+
== Handling table field ==
  
 
<small>since 1.2M1</small>
 
<small>since 1.2M1</small>
  
−
On a variable documented with type ''#table'', his fields are now displayed in the outline and available in the autocompletion.
+
On a variable documented with type ''#table'', its fields are now displayed in the outline and available from auto-completion.
−
 
+
[[File:ScreenFunctionReturnedTable.png|center]]
−
''Screenshoot''
+
−
* After a local variable commented by -- #table initialized with a function define some
+
  
 
== Rename ==
 
== Rename ==
Line 47: Line 40:
 
<small>since 1.2M1</small>
 
<small>since 1.2M1</small>
  
−
Pressing "ALT+SHIFT+R" on a lua variable enable to rename it and all his occurences.
+
Pressing <code>ALT+SHIFT+R</code> on a Lua variable enables to rename it and all its occurrences.
 +
[[File:ScreenRename.png|center]]
  
−
''Screenshoot''
+
== Integration of Metalua 0.7.2 ==
−
* While renaming a variable with occurences
+
−
 
+
−
== Integration of metalua 0.7.2 ==
+
  
 
<small>since 1.2M1</small>
 
<small>since 1.2M1</small>
  
−
LDT is now based on the version 0.7.2 of metalua.
+
LDT is now based on <code>Metalua 0.7.2</code>.
 +
 
 +
== Add map/list support ==
 +
 
 +
<small>since 1.2M2</small>
 +
 
 +
Using the <code>#list</code> or <code>#map</code> to type a variable or a field.
 +
See [[LDT/User_Area/Documentation_Language#List|detailed documentation]].
 +
 
 +
[[File:ScreenInlineMap.png|center]]
 +
<center><small><em>Using <code>map</code> in-line notation on a field</em></small></center>
 +
 
 +
[[File:ScreenInlineList.png|center]]
 +
<center><small><em>Using <code>list</code> in-line notation on variable to describe function result</em></small></center>
 +
 
 +
It is also possible to give a map or list behavior to a [[LDT/User_Area/Documentation_Language#Type|type]] by using <code>@map</code> or <code>@list</code> keywords.
 +
 
 +
[[File:ScreenMap.png|center]]
 +
<center><small><em>Using <code>@map</code> on a type</em></small></center>
 +
 
 +
[[File:ScreenList.png|center]]
 +
<center><small><em>Using <code>@list</code> on a type</em></small></center>
 +
 
 +
== Add __call support ==
 +
 
 +
<small>since 1.2M2</small>
 +
 
 +
Using the <code>@callof</code> keyword in a <code>function</code> to make a type ''callable''.
 +
See [[LDT/User_Area/Documentation_Language#Callof_sample|detailed documentation]].
 +
 
 +
[[File:ScreenCallOf.png|center]]
 +
<center><small><em><code>@callof</code> in action</em></small></center>
 +
 
 +
== Choose interpreter automatically ==
 +
 
 +
<small>since 1.2M2</small>
 +
 
 +
Interpreters are now linked to Execution Environments, this allows ''LDT'' to run applications with a compatible interpreter automatically.
 +
 
 +
[[File:ScreenAddInterpreterEE.png|center]]
 +
<center><small><em>Specify an Execution Environment which match your interpreter</em></small></center>
 +
 
 +
[[File:ScreenLaunchConf.png|center]]
 +
<center><small><em>You are warned when you launch an application with an inappropriate interpreter</em></small></center>
 +
 
 +
== LuaJIT Integration ==
 +
 
 +
Now, when you add your <code>LuaJit</code> to LDT, you can inspect ''FFI CData''.
 +
 
 +
[[File:ScreenAddLuaJITInterpreter.png|center]]
 +
<center><small><em>Adding a <code>LuaJit</code> interpreter to LDT</em></small></center>
 +
 
 +
[[File:ScreenLuaJITDebug.png|center]]
 +
<center><small><em>How <code>Cdata</code> are displayed in debugger</em></small></center>

Latest revision as of 10:53, 16 July 2014

New & Noteworthy 1.2

Add a library documentation to a project

since 1.2M1

By adding a .doclua file describing an API in Lua Documentation Language in your project source path, you will have auto-completion for described API.

ScreenDoclua.png

Debugging fix and enhancements

since 1.2M1

Here are some fixes to improve debugging experience and troubleshooting:

  • Avoid a crash when evaluating an expression from the watch view.
  • Use of interpreter's LUA_PATH if LUA_PATH environment variable is not available.
  • The debugger now logs his version and his connection status.
  • Better error logging during remote debug sessions.
ScreenDebuggerVersion.png

Extending a type

since 1.2M1

Using the @extend keyword in a module or type will extend it with all fields and functions of given super type. See detailed documentation.

ScreenExtendingType.png

Handling table field

since 1.2M1

On a variable documented with type #table, its fields are now displayed in the outline and available from auto-completion.

ScreenFunctionReturnedTable.png

Rename

since 1.2M1

Pressing ALT+SHIFT+R on a Lua variable enables to rename it and all its occurrences.

ScreenRename.png

Integration of Metalua 0.7.2

since 1.2M1

LDT is now based on Metalua 0.7.2.

Add map/list support

since 1.2M2

Using the #list or #map to type a variable or a field. See detailed documentation.

ScreenInlineMap.png
Using map in-line notation on a field
ScreenInlineList.png
Using list in-line notation on variable to describe function result

It is also possible to give a map or list behavior to a type by using @map or @list keywords.

ScreenMap.png
Using @map on a type
ScreenList.png
Using @list on a type

Add __call support

since 1.2M2

Using the @callof keyword in a function to make a type callable. See detailed documentation.

ScreenCallOf.png
@callof in action

Choose interpreter automatically

since 1.2M2

Interpreters are now linked to Execution Environments, this allows LDT to run applications with a compatible interpreter automatically.

ScreenAddInterpreterEE.png
Specify an Execution Environment which match your interpreter
ScreenLaunchConf.png
You are warned when you launch an application with an inappropriate interpreter

LuaJIT Integration

Now, when you add your LuaJit to LDT, you can inspect FFI CData.

ScreenAddLuaJITInterpreter.png
Adding a LuaJit interpreter to LDT
ScreenLuaJITDebug.png
How Cdata are displayed in debugger
Retrieved from "https://wiki.eclipse.org/index.php?title=LDT/User_Area/New_Noteworthy/New_Noteworthy_1.2&oldid=367308"

This page was last modified 10:53, 16 July 2014 by Eclipsepedia anonymous user Unnamed Poltroon.

Back to the top