Plugin 'Classic UI' is not compatible with the IDE because the IDE contains module 'com.intellij.jetbrains.client' which conflicts with the plugin

已回答

Upgraded to CLion 2024.2 and found that the “Classic UI” is not relegated to a plugin in favor of VS code ui.

When the plugin is enabled, when using ssh (remote dev) I get above error in startup and cannot use the classic UI. How to use the classic mode with remote dev setup?

3

I see. Unfortunate that it is only be VS Code UI going forward. It doesn't have the same flexibility as the classic one.

5

Wow, incredibly frustrating. I will probably cancel my subscription over this. Several issues here:

  1. You replaced a UI I loved with one I hate
  2. The plugin to get the old UI back doesn't work
  3. The error message that means “the plugin doesn't work with remote development” is completely unscrutable
  4. I don't see any indication that you intend to fix any of the above.
15

Dear JetBrains team,

this problem is also present in PyCharm.

It's really difficult to use a unified diff window. I like to use commit as dialog, because I'm used to. Now the dialog will always cover the unified diff view, which is in main window. And - the diff view does not even show the file name. The name is only shown in commit dialog. This is no nice user experience.

It feels like you are trying to copy VS Code more and more. But it had a reason why I am using PyCharm and not VS Code. However, in this case I will use the original VS Code and not the worse copy of it. Sorry.

6

@Se-folz I agree with your sentiment and those of the others in this thread. I just wanted to let you know that I found this thread because I too was trying to figure out how to get the diff in the commit dialog rather than in the main editor area. I subsequently found out that if you go to Settings → Version Control → Commit and uncheck “Use non-modal commit interface” you'll get the old commit window.

I feel like the docked, in-editor diff viewer is designed for people who code without using split panes at all. It's so annoying how the thing gets squished into whichever pane is active. My panes are only sized to fit a single file's width, not the two files side-by side of a diff view (let alone three in the case of conflict resolution).

0

Just ran into this today when trying remote development for the first time. JetBrains is a great product but the new UI is just so much more confusing.

3

The new UI is absolutely terrible. I am a developer! I WANT my cluttered interface where I can see everything I need without having to go through multiple menus looking for stuff! You just hampered my productivity with this garbage. If you are going to force me to use VSCode whether I want to or not, then I might as well cancel my IntelliJ license and get VSCode. Can't beat the price of free I guess.

2

Fwiw, you can add some actions to the toolbar (Right click and Add …).

Upgraded to 2025.2 just last week and Debug/Release switch is gone. Couldn't figure out how to add, or switch from any menu,

0

The new UI is horrible. I don't see a reason why you can't make the Classic UI work on Gateway. So Pathetic…

0

I've been using IntelliJ and several other JetBrains tools since 2011 +/- I remember it was the version 11. And I don't want to change the way of work. I'm always using the Classic UI from the 1st day.

0

Okay… the new interface won me over. I've been using the new design and there are things I like about it. The dark color theme is better than classic.

I had to configure the new interface to make it more useful though. This blog post about bridging the gap got me to adjust the look how I wanted it - mainly having the persistent menu and “compact mode" was the game changer.

https://blog.jetbrains.com/idea/2024/10/bridging-the-gap-between-the-classic-and-new-uis/

0

请先登录再写评论。