Difference between revisions of "LMD VCL - LMD IDE-Tools FAQ"
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Head-Overview}} [[Category:FAQ]] [[Category:LMD-Tools]] | {{Head-Overview}} [[Category:FAQ]] [[Category:LMD-Tools]] | ||
| + | |||
| + | == General == | ||
| + | |||
| + | == LMD DesignPack == | ||
| + | |||
| + | == LMD IDE-Tools == | ||
| + | |||
| + | === How to programmatically close the LMD collection editor (e.g. when saving the contents of a design page).=== | ||
| + | This should be done using EditorWindows property. This property is available in property inspector and designer components. Which property to use depends on your application configuration: By default all non-modal editor windows are associated with property inspector's EditorWindows. | ||
| + | But, it is possible to redirect all windows to designer's EditorWindows. If you use designer manager component this will be done automatically, otherwise you can implement ILMDEditorWndsProviderService service yourself to redirect non-modal editor windows to some editor-window-manager. | ||
| + | |||
| + | The idea of redirecting editor windows to designer's manager is to be able to hide/show all designer's windows, for example, when current designer changes (in case more then one designer is active at the same time). | ||
| + | |||
| + | |||
| + | == LMD ScriptPack == | ||
| + | |||
| + | === How to use Scripting with my own Delphi Classes instead of the Built In Delphi objects ? === | ||
| + | You should "import" the unit with your class declarations to the Script Pack. This can be done using Script Pack Importer, that is available in Delphi "Tools" main menu (when Script Pack is installed). See also [http://www.lmd.de/downloads/tutorials/scriptpack/index.html LMD ScriptPack] Tutorial. | ||
| + | |||
| + | === Which Script Languages are supported by LMD ScriptPack? === | ||
| + | By default the MS Windows Active Scripting Architecture supports two scripting engines (VBScript and JScript). No additional files are required here. | ||
| + | Any number of additional script engines can be added to the architecture, which must separately installed. A small overview can be found [http://www.dotnetframework.de/Scripting/ScriptingEngines.aspx here] (text is german). Additional engines can be found on the net. | ||
| + | |||
| + | === When putting TLMDScriptDebugger on a form, an exception like "Class not registered" is thrown === | ||
| + | This exception appears when MS ScriptDebugger is not installed. Get it from [http://www.microsoft.com/downloads/details.aspx?familyid=2f465be0-94fd-4569-b3c4-dffdf19ccd99&displaylang=en Microsoft WebSite]. | ||
| + | |||
| + | === How to use Tcl and TLMDScriptControl? === | ||
| + | At first you need to install an ActiveScripting compatible engine (for example from [http://www.ActiveState.com ActiveState]). In case of ActiveState engine, Tcl must be registered manually via | ||
| + | Tcl\lib\TclScript\register.tcl | ||
| + | TLMDScriptControl uses "TclScript" as ProgID for Tcl scripts, hence after that no further preparations are required.<br> | ||
| + | |||
| + | == LMD SyntaxEdit == | ||
Latest revision as of 20:06, 15 January 2008
<< Back to Overview page
General
LMD DesignPack
LMD IDE-Tools
How to programmatically close the LMD collection editor (e.g. when saving the contents of a design page).
This should be done using EditorWindows property. This property is available in property inspector and designer components. Which property to use depends on your application configuration: By default all non-modal editor windows are associated with property inspector's EditorWindows. But, it is possible to redirect all windows to designer's EditorWindows. If you use designer manager component this will be done automatically, otherwise you can implement ILMDEditorWndsProviderService service yourself to redirect non-modal editor windows to some editor-window-manager.
The idea of redirecting editor windows to designer's manager is to be able to hide/show all designer's windows, for example, when current designer changes (in case more then one designer is active at the same time).
LMD ScriptPack
How to use Scripting with my own Delphi Classes instead of the Built In Delphi objects ?
You should "import" the unit with your class declarations to the Script Pack. This can be done using Script Pack Importer, that is available in Delphi "Tools" main menu (when Script Pack is installed). See also LMD ScriptPack Tutorial.
Which Script Languages are supported by LMD ScriptPack?
By default the MS Windows Active Scripting Architecture supports two scripting engines (VBScript and JScript). No additional files are required here. Any number of additional script engines can be added to the architecture, which must separately installed. A small overview can be found here (text is german). Additional engines can be found on the net.
When putting TLMDScriptDebugger on a form, an exception like "Class not registered" is thrown
This exception appears when MS ScriptDebugger is not installed. Get it from Microsoft WebSite.
How to use Tcl and TLMDScriptControl?
At first you need to install an ActiveScripting compatible engine (for example from ActiveState). In case of ActiveState engine, Tcl must be registered manually via
Tcl\lib\TclScript\register.tcl
TLMDScriptControl uses "TclScript" as ProgID for Tcl scripts, hence after that no further preparations are required.
