Leaderboard

StyleControls VCL v. 4.41 just released! http://www.almdev.com StyleControls VCL is a powerful, stable package of components, which uses Classic drawing, system Themes, GDI+ and VCL Styles. This package contains the unique solutions to extend standard VCL controls and also has many unique, advanced controls to create applications with UWP-like design. Also with this package you can really improve applying and using of VCL Styles in your application.

I mentioned that I am working on the Delphi Tools Manager in my post about GExperts supporting import and export for the Tools menu. Today I finished the first version of this tool. It supports all Delphi versions from 5 to 10.3 (it is written in Delphi 10.2). So, what does it do: It shows a list of all entries in the Delphi IDE’s tool menu in a similar manner as the Tools Options dialog. It allows the same actions as that dialog: Add/Delete/Edit an entry and change the order of the entries. It shows the details of each entry when it is selected. It allows exporting and importing entries, using the same DTME file format as GExperts Dragging one or more DTME files on the form will add them to the list Read on in the blog post at https://blog.dummzeuch.de/2019/06/16/delphi-tools-manager-1-0-0-released/

If you have documentation you cannot just yolo refactor code every release and break something...

I don't buy that argument. People are using the software now. And software is never finished. There is always more to be done. So if you wait until it is done, then you never document it. My personal experience, and very strongly felt, is that writing documentation is a key part of finalising and debugging specification. So many times have I experienced this. Only when you write the documentation do you realise some of the issues that users will face. Deal with them before releasing and you don't have to spend as much time in back compat hell. My view is that writing documentation in a timely fashion actually saves time and resources in the long run.

I dispute that. I don't see anything wrong with a business model that concentrates on enhancing and developing their core market. Imagine what could have been achieved on Windows if all the resource that was used on the new platforms had been spent on Win32 and Win64? Remember also that the vast majority of the income is still from the Windows tools.

Sure it's down to a lack of resources. But that's a consequence of expanding to new platforms. Each additional platform comes with a maintenance cost. That cost is paid for out of revenue. The bulk of the revenue comes from customers that are using the legacy platforms. If Emba continue to neglect their core business (Windows development tools) then eventually customers will look elsewhere.