Plugin dialog showing modules I don't want user to see.

Thanks but I like it. I do wish I had more control over which tabs are visible and which are not etc. I would like to be able to control restarts after module activation as well as module deactivation. Maybe I can do this and I just haven't investigated enough.

However it does do most of what I want right from the start. I think there is enough value there to suggest improvements as opposed to doing my own. This is the same reason I use the standard Java file selection and color dialogs etc. Not only does it save me a lot of time, there is a lot of benefit to users when applications do the same function in the same way.


Peter Hansson wrote:
> Personally I do not use the standard NB Auto Update UI for NetBeans Platforms Apps. You are not forced to, you know that, right ?
> 
> 
> I find that there are often too many things I would like to change:   for some apps updating should be purely a background task (without the user having to do anything at all), for some apps I want full control over what modules are shown to user, for some modules you may want to have some kind of in-app purchase procedure, etc, etc.
> 
> 
> As it turns out the two major apps I'm involved with have ditched (any type of) Auto Update UI altogether. The reason is that there are actually no options that I want the user to choose from, so no UI.
> 
> 
> So instead of trying to get the standard Auto Update UI to do exactly what you want then why not consider doing your own UI or consider if your app needs any UI in this area at all. Just some thought.
> 
> 
> Peter
> 
> 
> On Thu, Feb 4, 2016 at 12:06 AM, mccorb <address-removed (address-removed)> wrote:
> 
> > Geertjan,
> > 
> > I appreciate the input.
> > 
> > I think until they fix it (I hope it gets fixed) I will just fall back to 8.0.2 to do a release. I reported the bug and referred to this thread.
> > 
> > thx,
> > 
> > 
> > 
> > geertjan wrote:
> > 
> > > There might be a hacky way to do it from a ModuleInstall in a similar
> > > way to what Yenta does:
> > > 
> > > https://bitbucket.org/jglick/yenta (https://bitbucket.org/jglick/yenta)
> > > 
> > > Gj
> > > 
> > > 
> > > On 29-1-2016 9:59, robert4444 wrote:
> > > 
> > > 
> > > > In my application I have the 3 first one, and JUnit and TestNG (all in Libraries category of Plugin Manager).
> > > > None of these is explicitly set in my pom, so I don't want them or I don't want to see them.
> > > > I think these are dependencies from the application.
> > > > For me the best solution would be to be able to hide an entire category in the Plugin Manager, but I have no idea how to do that !!
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
>