[jbosstools-issues] [JBoss JIRA] (JBIDE-10252) Add/display a progress bar on the Application Wizard page when retrieving the list of cartridges

Andre Dietisheim (Issue Comment Edited) (JIRA) jira-events at lists.jboss.org
Mon Dec 12 15:55:09 EST 2011


    [ https://issues.jboss.org/browse/JBIDE-10252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650209#comment-12650209 ] 

Andre Dietisheim edited comment on JBIDE-10252 at 12/12/11 3:54 PM:
--------------------------------------------------------------------

afaik things are already set up to show up in the first page of the wizard. 

{code}
	@Override
	protected void onPageActivated(DataBindingContext dbc) {
		try {
			WizardUtils.runInWizard(new Job("Loading cartridges...") {

				@Override
				protected IStatus run(IProgressMonitor monitor) {
					try {
						model.loadCartridges();
					} catch (OpenShiftException e) {
						return new Status(IStatus.ERROR, OpenShiftUIActivator.PLUGIN_ID, "Could not load cartridges", e);
					}
					return Status.OK_STATUS;
				}
			}, getContainer());
		} catch (Exception e) {
			// ignore
		}
	}
{code}

The code is called when the page is activated. This approach actually works pretty well on most pages in the current OpenShit Express Application wizard, they all run the job that is scheduled #onPageActivated (and display the progress bar in the wizard). I suspect the page activation to behave differently for the 1st page in a wizard (and call #onPageActivated before the dialog really shows up). 
When trying to fix quickly, I switched from running the job #onPageActivated to some #onVisible method. That did not seem to help.
                
      was (Author: adietish):
    afaik things are already set up to show up in the first page of the wizard. 

{code}
	@Override
	protected void onPageActivated(DataBindingContext dbc) {
		try {
			WizardUtils.runInWizard(new Job("Loading cartridges...") {

				@Override
				protected IStatus run(IProgressMonitor monitor) {
					try {
						model.loadCartridges();
					} catch (OpenShiftException e) {
						return new Status(IStatus.ERROR, OpenShiftUIActivator.PLUGIN_ID, "Could not load cartridges", e);
					}
					return Status.OK_STATUS;
				}
			}, getContainer());
		} catch (Exception e) {
			// ignore
		}
	}
{code}

The code is called when the page is activated/gets visible. This approach actually works pretty well on most pages in the current OpenShit Express Application wizard, they all run the job that is scheduled #onPageActivated. I suspect the wizard to behave differently when it's the 1st page in a wizard and call #onPageActivated before the dialog really shows up. What I can't explain currently is that I switched from running the job #onPageActivated to some #onVisible method.
                  
> Add/display a progress bar on the Application Wizard page when retrieving the list of cartridges 
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-10252
>                 URL: https://issues.jboss.org/browse/JBIDE-10252
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 3.3.0.M4
>            Reporter: Xavier Coulon
>            Assignee: Xavier Coulon
>            Priority: Minor
>             Fix For: 3.3.0.Beta1
>
>
> The first time the user want to create a new Openshift Application, the wizard needs to retrieve the list of available Cartridges from Openshift. This operation can take a few seconds and the UI is blocked until the response is received and processed.
> The wizard page should display a progress bar along with a message, so that the user understands that a remote operation is performed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list