We already did some IDE improvement with Juha Manninen, if he agrees I would like to work with him.
Yes I am ready. Your improvements for the component list were good. I know the component palette code now well after I made it configurable.
Your changes shown in the video look good and I believe they can be applied.
However they will not be enough. We must rethink "out of the box" the whole palette GUI. Now it has some serious issues:
1. The palette tab-control and the list window are not truly equal alternatives to each other. The palette can be hidden but not moved or docked anywhere else. This will be even a bigger problem if tabs are split into multible rows which is a reasonable feature request.
I think the main window is not part of the docking system mainly because of the palette. This is one more reason to redesign it.
2. It should be possible to hide the whole palette or list when there are no Forms or DataModules where to put components, and maybe replace it with something else. The current DataModule filtering is kind of a half-ass solution. It hides the components which cannot be placed on a DataModule, logically it should hide all of them if there is neither a Form nor a DataModule.
Delphi has solved this problem with a context aware component list.
Number 2 is a complex issue. What to show instead of components in a context aware system? Should the IDE main menu be context aware, too? Et cetera ...
Number 1 should be improved by making the palette a separate dockable window. It requires changes to the palette API in IDEIntf. Now it is hard-coded to some GUI controls. I can look at that.
Then the main window should be included in docking as a dock-host window. Unfortunately I don't know AnchorDocking well.