Skip navigation links
org.netbeans.modules.autoupdate.ui 1.47.1

Auto Update UI
Stable

See: Description

Auto Update UI 
Package Description
org.netbeans.modules.autoupdate.ui.api  

The AutoUpdate UI module contains user visible elements (actions in menu, dialogs), that allow any users to download new, or existing modules from a pre-registered or manually registered update centers. In addition the module also provides an API to allow other modules to invoke pieces of the user related work flow (dialogs, wizards) directly at moments independent on the rest of the provided UI.

What is New (see all changes)?

Use Cases

Download and Install
Primary purpose of the API is to share classical UI for downloading and installing additional modules. Read about PluginManager.openInstallWizard.

Exported Interfaces

This table lists all of the module exported APIs with defined stability classifications. It is generated based on answers to questions about the architecture of the module. Read them all...
Group of java interfaces
Interface NameIn/OutStabilitySpecified in What Document?
AutoUpdateUIExportedStable

this module exposes bits of its UI and user related workflow actions (related to installing, upgrading, etc.) by providing an API calls for other modules to invoke bits of here-in available functionality.

Group of property interfaces
Interface NameIn/OutStabilitySpecified in What Document?
org.netbeans.modules.autoupdate.ui.actions.PluginManagerAction.initialTabExportedUnder Development

There is an action registered with @ActionID(id = "org.netbeans.modules.autoupdate.ui.actions.PluginManagerAction", category = "System") that opens the plugin manager dialog and reacts to a special event: new ActionEvent(this, 100, nameOfTabToOpen). The tab names include { "update", "available", "local", "installed" }.

Implementation Details

Where are the sources for the module?

The sources for the module are in the NetBeans Mercurial repositories.

What do other modules need to do to declare a dependency on this one, in addition to or instead of a plain module dependency?

You modules can use the AutoUpdateUI API directly (of course you almost certainly need also Autoudate Services), just be aware that this module comes with a UI. It is not always practical to depend on modules that provide a UI from low level infrastructure modules - if that is your case, consider separating calls to AutoUpdateUI into separate bridge module.

Read more about the implementation in the answers to architecture questions.

Skip navigation links
org.netbeans.modules.autoupdate.ui 1.47.1

Built on June 22 2019.  |   Copyright © 2017-2019 Apache Software Foundation. All Rights Reserved.