Not only did this approach mean that the extension needed to be reinstalled on every daily or monthly update of VS Code, it opened up to a new class of issues which we could not easily diagnose or fix, since the core product was being modified after we shipped it. Without a proper extension mechanism, Roberto was forced to patch the installed sources in order to make the vscode-icons extension work properly. It would be impossible to come up with a single set of icons that everyone agreed upon. It was clear from the start that we needed to make icon theming an extension point to VS Code.
200 thumbs up said we needed to listen to this feedback and look at this again. The 10 people on the VS Code team at that time hardly constituted a statistically significant data set.
To us, icons felt heavy and provided little value. The team loved the simple, clean look of an icon-less tree. When we started work on the "Monaco" editor, icons in the Explorer didn't make the cut for a lightweight editor. was an intern in Zurich lab and spent a couple of hours hacking in a basic set of icons because he wanted to differentiate between files and folders when quickly glancing at the tree. These words all describe the first time we added icons to the File Explorer tree in VS Code, back in 2014.
Admin menu items can be added with register_post_type() and add_menu_page(), which both have an option to set an icon.
0 kommentar(er)
