I’ve managed to start Argo by initializing the GUI before the init of
Modules subsystem, in Main.

Will this be changed in the trunk? 

 

I also noticed that module classes are loaded twice. Is this ok?

 

Regarding loading the Tabs, I’ve done it with:

            ((DetailsPane)
ProjectBrowser.getInstance().getDetailsPane()).getTabs().addTab(title, p);

Is this the planned way for modules doing it?

 

Sergio.

 

  _____  

From: Sérgio Lopes [mailto:[EMAIL PROTECTED] 
Sent: segunda-feira, 26 de Novembro de 2007 13:57
To: [email protected]
Subject: [argouml-dev] Loading tabs for the DetailsPane

 

Hi,

 

I’ve noticed that ConfigLoader#loadTabs(…) has been deprecated. I wonder
which is the standard way for modules to add tabs to the Details panel?

 

After a quick search I’ve tried to do it in ModuleInterface#enable():

ProjectBrowser.getInstance().getDetailsPane().add(p);

but Argo failed to start. Then I’ve tried

ProjectBrowser.getInstance().addPanel(p, Position.South) ;

with the same result.

Apparently, this happens because when ProjectBrowser.getInstance() forces
the instantiation of ProjectBrowser with a ‘null’ ToDoPane, instead of the
lazy instantiation by Main#initializeGUI(…).

 

Regards,

Sergio.

 

 

--------------------------------------------------------------

Sérgio Adriano Fernandes Lopes

 

Address: Dpto Electronica Industrial            e-mail:
<mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]

         Universidade do Minho           Tel.: +351 253 510387

         Campus de Azurem                Fax: +351 253 510189 

         4800-058 Guimaraes

         PORTUGAL

--------------------------------------------------------------

 



Reply via email to