Open Chris2011 opened 7 years ago
Seems also that on saving the file there are different refresh (I see the cursor blinking from pointer to write). Removing the plugin now netbeans don't get 77% of my cpu, seems that the actual plugin also with the fix offormat is not yet stable to use it.
I think the refresh is normal, because of adding the formatted text again to the editor, maybe there can be an other possibility to reformat it with the normal NB functionality but map the settings from the editor config file.
Can someone have a deeper look into this problem, with more knowledge? I think this is one big problem and needs a fix for this.
Anything new here? Anyone?
Can please someone have a look who has more knowledge about it, than me? @bennyn or @Mte90 can you maybe have a look please? Otherwise the plugin will be unusable.
I am not using anymore this plugin and migrated to Vim. I am using Netbeans only for few projects right now.
@Chris2011 I switched to WebStorm a few years ago so I am not up-to-date with NetBeans development but PRs for this project here are more than welcome. Do you have an idea how to improve the performance problem and have less calls to writeWithEditorKit
?
@bennyn I have to understand, why this is happening or why does this implemented as it was. Maybe a rewrite will fix the problem anyway(?).
@bennyn hey, can you please add prio: high on that? This is a big problem of this plugin.
One of the biggest problems, that I figured out, is that when you save your changes, it will run very often the writeWithEditorKit method or the runnables inside. This is a performance problem I think, because first you feel and see it. You see the spinning wheel after you hit save and you feel changed in the editor window. So I only tested it in my dev enviroment with no plugins, only with this plugin but It could be a big problem in the live enviroment.
So this method should be refactored. I added a sout, that you can see how often it will called.
Cheers
Chris