3 ms·
There is on problem with Lazarus approach. IDE and visual form layout editors require specialized property editors. And amount of code for design time support
by c-smile 7y ago
There is on problem with Lazarus approach.
IDE and visual form layout editors require specialized property editors. And amount of code for design time support is significant usually.
Yet, data produced by layout editors is not DIFF friendly. Ability to edit UI definitions in text forms is valuable for collaborative work. That's why Delphi/Lazarus is popular among INDIE developers but not in large companies.
- badsectoracula 7y agoI'm not sure what you have in mind, Lazarus (and AFAIK Delphi at least since version 7, most likely earlier too) saves the form as a text file which you can diff and i do that all the time when looking at changes in my code before submitting them. In fact the format is very readable and has a syntax like: object ScriptConsole: TScriptConsole Left = 349 Height = 331 Top = 710 Width = 487 ... object Cmd: TEdit Align = alBottom end ... end (this is part of the code from a form of a project of mine called ScriptConsole) It only stores properties changed from their defaults which makes for very compact files and focusing on the stuff you have actually worked on. If anything i find the XML files that other tools (like Qt Designer and wxFormBuilder) use harder to read.
- c-smile 7y agoAh, missed that one, thanks. Format looks like .frm files of VB6. And that's somehow closer to C++ (than Delphi) as widgets there are COM objects.