You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a growing pattern for UI-specific plugins like the InputWidget implementations. These are HandlerPlugins or WrapperPlugins that should only be chosen if their associated UI(s) matches the activated UI(s). Rather than have this logic specifically at the level of InputWidget and InputPanel, we should generalize things to a common UIPlugin, all of which share the "is my UI active?" logic.
We could then use it for cases like imagej-updater's UpdaterUI plugins, which right now activate blindly whenever they are on the classpath.
Another case for this sort of functionality is Command plugins that are only applicable to a particular UI. For example, the WindowsTileVertical plugin of scijava-ui-swing is only supposed to be visible in the SwingMDIUI, but currently there is no way to restrict it. Think further about this.
Activity
PromptUserToUpdate: do not update while headless
ctrueden commentedon Mar 26, 2015
Another case for this sort of functionality is
Commandplugins that are only applicable to a particular UI. For example, theWindowsTileVerticalplugin ofscijava-ui-swingis only supposed to be visible in theSwingMDIUI, but currently there is no way to restrict it. Think further about this.