Hi, just wondering if it is possible to remove icon(s) from a components control panel. What file determines what is produced on the control panel?

Cheers in advance

This stuff is located in JDom for the rendering
Namespace : html.menu.cpanel
Cpanel menu:and buttons here:
JDom is gonna disapear in future. All this will be handled with a component helper. Maybe very soon. It could be the next monday, or following.
At the moment, you can override JDom in you component, placing the modified files in "dom" directory of your back-end component.
Just respect the same folders tree, and your custom file will override the native JDom. It is not using the fork system. It was designed before and JDom is independant.

Hope it helps, otherwise, I can give you more details.
If you hold patience, I tell you, this is gonna evolve soon.

For that, I didn't hack JDOM, but just disable the display of Menu Item ... [helper.php]Works fine too

Thanks @liubov,

Of course you can do that way, and the future rewrite will include a XML file for configuring menus.
I was explaining for HTML custom (removing all icons).
But, now I understand the question was about removing a button, not an image.
For rendering customs, the CSS is also good.

You may answered better than me. So the two solutions are explained.

Thanks,
Customized CPanel handle with XML will be a great feature, with a key Icon => show/hide

Thanks . Got it and will now be able to sort.

Are you going to remove the plugin Jocelyn?
That will have a huge impact on projects I made, because I call the JDom in fork to create custom actions, buttons etc.

No, I am not gonna end with JDom now.
And will still be available and usable when you want.

JDom remains a great piece but will be used more for embeding snipplets of code, such as the Google map (or charts...) for instance.
And in case, it is still great to instance headless controls (without JForms)

But JDom is not the best for grids (memory optimization), and almost useless for the forms.
It was designed long time ago, but now Joomla has filled the gap, and building native is better and required.

So don't worry, because your component will still have some JDom inside, but ONLY where Joomla is not able natively.
It is a long way after successive versions where I will remove the CALLS step by step.
But don't worry, it will always be included by default because Cook will grow with more advanced plugins (the direction).
And for purists, I will may include an option for avoiding JDom, but restricting the exetended features.

For your forks, if they use JDom, it will always work. the problem would be if you made your customs in JDom classes which would become not called anymore.

I am not worried, I fully agree that native is better

The feature is done.

Since 3.1.9, you can now manage menus through the XML menu file.

menu.xml at the component root.
(FRONT and BACK)

This file is forkable, but will replace all.

Real good job, and curious to play with ...