|
From: Benoit X. <bx...@ob...> - 2007-07-06 16:56:04
|
Hi
I'm trying to change the StatusBar to split it to have a section for
scrolling messages. I'm a bit surprised that quite a few interfaces are
using StatusBar which is a concrete class.
Should I use only the StatusBarCommandGroup???
At the moment, my approach is to have:
- my lifecycleAdvisor to override getStatusBarCommandGroup()
- returning a StatusBarCommandGroup that overrides createStatusBar() =
(but
requires a StatusBar itself!!! so I must extends that class even if I do =
not
intend to use it...
Is my approach ok?
However this seems extension of the StatusBar seems to cause some issue, =
the
initialize method on StatusBar is called which then creates items in the
JPanel=85
Could the StatusBar be refactored to be an interface?
=20
I=92m willing to provide a patch if you=92re ok with this:
Interface StatusBar {
ProgressMonitor getProgressMonitor()=20
void setMessage(String message)=20
void setMessage(ImageIcon icon, String message)=20
void setErrorMessage(String message)=20
void setErrorMessage(ImageIcon icon, String message)=20
void setVisible(boolean visible)
}
=20
Let me know, we=92re a bit stuck at the moment=85
Thanks!
Benoit
No virus found in this outgoing message.
Checked by AVG Free Edition.=20
Version: 7.5.476 / Virus Database: 269.10.1/888 - Release Date: =
06/07/2007
06:36
=20
|