Move view control to a separate class?

Question

Programming

There is such a class . In the course of innovations, a lot of code appeared in it, which is responsible for both logic and presentation. I already noticed what could be moved to another class (everything that affects the display of objects).
If we follow the MVC pattern, then the Editor class would be a Controller, the display control would be moved to the View (how then would the class be called, according to the subject area?), and the Model could then be left in the Editor, while investing in 200 lines of code.
What would be the guidelines for naming a class and separating data, control, and presentation?

Answer 1

At the moment, I removed the view control from the class . Without bothering, I called EditorView :)

Answer 2

most likely, you do not have a clear model of what you are doing, otherwise you would not have asked this question,
take a regular sheet of paper and draw all the components with their functions on it, maybe then you will understand how you best organize everything else