On Mar 15, 2018 10:59, <toni.ep...@eppleton.de> wrote: These things can happen in parallel. I for my part cannot help much with Python or Groovy features, but I can help with the POCs to improve NB UI and make it future proof. If for example we manage to replace JavaFX WebView with something better, contributors like Chris Lenz will be able to use more HTML5 features for writing their plugins and the performance of HTML-based plugins will improve.
I agree with that. Maybe some of the Swing/JavaFX developers will also try it out and realize that developing with modern ui patterns like MVVM can dramatically speed up development, and lead to more testable and stable code while reducing the LOC. This would have the immediate effect of better code that needs less maintenance. MVVM is certainly possible now considering the components already have their own model, so VM there, then other logic is a translation of the Angular concept of a service, and data models which differ from the component model is that. Now, one can certainly write better or worse UI code in a tightly coupled manner. But, and I have seen it, one can also do that with Angular. So, I get what you are saying here, and only agree in that there are plenty of people who don't know how to decouple UI logic, and the Angular style guide does a better job of getting people down the right path than the Swing tutorials. But we can also offer them a way to still run their ( in my opinion horribly archaic đ ) Swing code. Ha...see what you did there. You have gone to the dark side, but it's cool. I still like you! As a side effect we could also replace the embedded Browser for debugging web applications with a real browser and make Web Development in NB even more attractive. Projects like the Oracle JET support in NetBeans, but also EE projects could directly benefit from that. Yeah, as part of the web support, such things sound reasonable for those purposes no matter what. You're right these changes are driven by longer term goals, but they will also create huge short term improvements. I will wait to see on it then. In the mean time I will work on my parallel bits :-) And since there's a lot of confusion here between "web technologies" and "web applications": I for my part don't want to run NetBeans in a Browser. I want NetBeans to remain a traditional Desktop application, which can use modern HTML5 UIs Got it. and is prepared for the end of Swing. Dark man; dark. Lol. Thanks Wade
