On Fri, 11 Feb 2022 at 17:56, Ernie Rael <[email protected]> wrote: > But from what I can > tell, the biggest problems with them was more about how they were used, > not the infrastructure that downloaded them.
No, from my perspective, the biggest issues have been caused by the infrastructure that downloaded them ... > NB can download/install stuff from the plugin portal; Yes, it can, let's use that! JavaFX, and until now nb-javac, are shipped in a "fake" update centre inside the IDE. It can get flaky, and the version of the dependency is baked into the IDE, so that to ship updates requires a new IDE release just to change the links and hash. Not to mention that for the end user, they actually end up going through multiple update notifications - one to change the hashes, one to download the modules, which is confusing. > Possibly download/install on > demand though ergonomics, though I've heard some grumblings in that area. Yes, lots from me! :-) Not all the paths that trigger this in ergonomics actually work very well (eg. in Tools / Options), and it's quite possible to bypass the ergonomics support entirely. What's wrong with putting X module in the plugin portal, and a friendly notification that "This project requires X plugin", and a button that guides people through the install process? More guidance, less voodoo, is a good thing. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
