IDE Development

This is an old revision of IDE Development, edited by Mattias2 at . The current revision is 51220.

/* Working */

This page contains notes for lazarus core developers about ongoing development.

Multi form properties / using DataModules from other forms in the designer

Note: This paragraph is referenced by Lazarus 0.9.26 release notes and Lazarus 0.9.28 release notes and Lazarus 0.9.30 release notes.

Short Description

This feature allows to use components of other designer forms. A common example is to use the TDataSource on a DataModule for the DataSource property of a db control. Designer forms can only reference each other if they have a CreateForm statement in the lpr file (Project Options / Forms).

Working

ToDo

Translations, i18n, lrt files, po files

Short Description

This feature automatically creates and updates .po files for packages and projects.

Working

ToDo

Frames

Short Description

Frames are special child forms. The goal is to edit them like forms in the IDE designer, and to use them as components on designer forms.

Working

compile lazarus clean with passing -dEnableTFrame (not necessary starting from svn release 16909)

ToDo

VFI - Visual Form Inheritance

Short Description

Forms can inherit from other forms. The .lfm streams of ancestors are read/applied before the current lfm. The .lfm of the descendant is the difference between ancestor and current state. The IDE allows to open and edit inherited forms. VFI does not only apply to TForm, but TDataModule, TFrame and any registered base designer class. For the full features compile with -dEnableTFrame.

Working

ToDo

CodeTools Debugging

Short Description

The codetools and its integration in the IDE is a complex part and a bug can create strange side effects, happen sometimes only after a long time and are hard to reproduce. The IDE needs some debugging tools to show the internal structures and run consistency checks.

Working

ToDo

Create auto generated files in the output directory

Short Description

The IDE auto creates some files, like the .lrs files of the .lfm files. These files should be auto created in the output directory. This has the advantage that they are not in the source directory, making browsing and version control systems easier.

Working

ToDo

The jedi code formatter

Short Description

Working

ToDo

Builtin CHM help

Short Description

Use the cross platform lhelp program to view chm help files from the IDE

Working

ToDo

Translated compiler messages

Short Description

The IDE can only parse English compiler messages. The same for linker and make messages. It would be nice to show the translated messages. The FPC sources contain the translated texts, for example compiler/msg/errord.msg for german. Since FPC 2.4.0 the compiler knows the option -vq which shows the message number. This could be used to find for an English message the translation (if there is any) or from the translation back to the English one. The main problem is to distinguish compiler, linker and make messages.

Working

ToDo

Debugger

Short Description

Working

ToDo