Difference between revisions of "LMD 2010 - History LMD IDE-Tools"
| Line 8: | Line 8: | ||
==== Release 3.02 (02-Oct-2009) ==== | ==== Release 3.02 (02-Oct-2009) ==== | ||
| + | |||
| + | ''IDE-Tools'' | ||
| + | |||
| + | [*] Some minor fixes.<br>[+] New advanced IDE demo shows new debugging features of the LMD-ScriptPack and new debug related IDE-Tools controls. Also this demo implements Delphi like layouts using LMD-DockingPack. | ||
| + | |||
| + | ''ScriptPack''<br> [+] New Modules collection has been added to the debugger. Items in the collection is of TLMDDebugModule class. A debug module is the abstract representation of the debugging module/source-file. It was added mainly to implement two following ideas: first, to allow to setup and maintain the breakpoints during design-time in the scripting-IDE (e.g. while the script project is not running and no script controls are exsist); and second, to allow to associate more then one script control with the same debug module at run-time (e.g. like more then one form of the same class can be created in Delphi application at run-time).<br> [*] Despite the old DebugName property is supported in the script control, its value is only a consequence of the new DebugModule property. The new DebugModule property should be used to associate a script control with the debug module. <br> [*] The breakpoints are now set on the debug module as a whole, not on the concrete script control. So, all associated with the module script controls will break at run-time.<br> | ||
''SyntaxEdit''<br> [+-] ILMDLineMark and ILMDMark merged into one ILMDMark interface. <br> | ''SyntaxEdit''<br> [+-] ILMDLineMark and ILMDMark merged into one ILMDMark interface. <br> | ||
| Line 14: | Line 20: | ||
TLMDCustomEditView.DebugFrameLineColor/DebugFrameLineBg/DebugFrameActiveLineColor/DebugFrameActiveLineBg/DebugFrameTopLineColor/DebugFrameTopLineBg. <br> | TLMDCustomEditView.DebugFrameLineColor/DebugFrameLineBg/DebugFrameActiveLineColor/DebugFrameActiveLineBg/DebugFrameTopLineColor/DebugFrameTopLineBg. <br> | ||
Those properties works as correspondent Breakpoint support properties (TLMDEditDocument.Breakpoints and other), and used to mark stack frame lines from some custom IDE debugger. <br> | Those properties works as correspondent Breakpoint support properties (TLMDEditDocument.Breakpoints and other), and used to mark stack frame lines from some custom IDE debugger. <br> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==== Release 3.01 (08-Sep-2009) ==== | ==== Release 3.01 (08-Sep-2009) ==== | ||
Revision as of 16:58, 5 October 2009
<< Back to Main Page or Product Resources page
Contents
Introduction
This documents contains history logs for LMD IDE-Tools 3.0 and corresponding standalone packs.
First official release: 25-Aug-2009
Major version numbers are:
LMD IDE-Tools 3.0, LMD DesignPack 5.1, LMD ScriptPack 6.0, LMD SyntaxEdit 2.1
Legend
[+] Feature added
[*] Feature changed
[-] Bug fixed
History Logs
Release 3.02 (02-Oct-2009)
IDE-Tools
[*] Some minor fixes.
[+] New advanced IDE demo shows new debugging features of the LMD-ScriptPack and new debug related IDE-Tools controls. Also this demo implements Delphi like layouts using LMD-DockingPack.
ScriptPack
[+] New Modules collection has been added to the debugger. Items in the collection is of TLMDDebugModule class. A debug module is the abstract representation of the debugging module/source-file. It was added mainly to implement two following ideas: first, to allow to setup and maintain the breakpoints during design-time in the scripting-IDE (e.g. while the script project is not running and no script controls are exsist); and second, to allow to associate more then one script control with the same debug module at run-time (e.g. like more then one form of the same class can be created in Delphi application at run-time).
[*] Despite the old DebugName property is supported in the script control, its value is only a consequence of the new DebugModule property. The new DebugModule property should be used to associate a script control with the debug module.
[*] The breakpoints are now set on the debug module as a whole, not on the concrete script control. So, all associated with the module script controls will break at run-time.
SyntaxEdit
[+-] ILMDLineMark and ILMDMark merged into one ILMDMark interface.
Also, all interfaces/classes/methods related to ILMDLineMark now working as aliases to correspondent ILMDMark code, and marked as deprecated (old with ILMDLineMark using code should still work).
[+] Added support for custom debugger frame markers: see types/properties:
TLMDDebugFrameKind, TLMDEditDocument.DebugFrameLines/GetDebugFrameKind/SetDebugFrameKind,
TLMDGutter.DebugFrameTopImg/DebugFrameActiveImg/DebugFrameImg,
TLMDCustomEditView.DebugFrameLineColor/DebugFrameLineBg/DebugFrameActiveLineColor/DebugFrameActiveLineBg/DebugFrameTopLineColor/DebugFrameTopLineBg.
Those properties works as correspondent Breakpoint support properties (TLMDEditDocument.Breakpoints and other), and used to mark stack frame lines from some custom IDE debugger.
Release 3.01 (08-Sep-2009)
ScriptPack
[-] BTS #0732: intermittent "Undeclared identifier"in PascalScript has been fixed.
[-] BTS #0731 and #0730: endless loop while parsing code has been fixed.
[-] BTS #0728: loosing some property values because of unproper form handle recreation in design-panel has been fixed.
Release 3.0 (25-Aug-2009)
Initial Release.
