This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 32259 - Add support for the creation of a non-default status line
Summary: Add support for the creation of a non-default status line
Status: RESOLVED DUPLICATE of bug 32255
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: David Strupl
Depends on:
Blocks: 32488
  Show dependency tree
Reported: 2003-03-24 21:52 UTC by David Strupl
Modified: 2008-12-22 21:46 UTC (History)
3 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description David Strupl 2003-03-24 21:52:38 UTC
The status line component should be pluggable.
Also the place where the status line appear should
be customizable --- at least status line on the
bottom edge of the main window should be supported.
Comment 1 David Strupl 2003-03-30 16:47:54 UTC
On branch platform_32247:

Checking in core/src/org/netbeans/core/windows/;
/cvs/core/src/org/netbeans/core/windows/,v  <--
new revision:; previous revision: 1.17

Added a possibility to specify a custom status line component.
Comment 2 Jesse Glick 2003-03-31 17:21:27 UTC
Please don't use services lookup for this, it is not well-suited to
that. For now, just find InstanceCookie from a particular place in
SFS; can move to Naming or whatever later.
Comment 3 David Strupl 2003-04-02 20:14:24 UTC

Checking in;
/cvs/core/src/org/netbeans/core/windows/,v  <--
new revision:; previous revision:
Comment 4 Peter Zavadsky 2003-04-07 08:22:06 UTC
More generally, do you think all GUI components should be pluggable,
or just the status line?

It seems to me as an interesting idea. On the other hand I guess, if
it is supported it should be allowed just at platform, not IDE, level.

And it would be probably an API (or SPI?) of specific window system
impl (core-windows) not open API. I guess.

Is this supposed to be solved that way?

Comment 5 David Strupl 2003-04-07 08:28:56 UTC
Yes - correct solution should include an API, preferably 
in the Window system that would allow to do this.
Please check also isssue 32255.
Comment 6 Marian Mirilovic 2003-11-26 12:55:27 UTC
Because Window System v1 will not be supported from now by our team, all old
winsys issues (now "core/window system v1" issues) are going to be closed as

Changes in API which emerged both from UI spec 
and problems with adjusting to the older API are described in the document
 It shows also recommends how the client code should be adjusted to the new
window system.

If you think this issue apply also to the new winsys then change the
subcomponent (to "core/window system") and REOPEN it.
Comment 7 David Strupl 2003-11-26 14:35:06 UTC
If the new winsys allows me to specify a custom status line component
- this is done. Otherwise reopenning.

If you do any change with respect to this - please allow also putting
the status line at the lower edge of the main window.
Comment 8 Jesse Glick 2003-11-26 15:39:51 UTC
The new status line *is* at the bottom of the main window. But you
cannot put it anywhere else.

Still important?

I have a separate issue open for letting you put it in the menu bar as
you could in 3.5.
Comment 9 David Strupl 2003-11-26 17:08:53 UTC
The point is to be able to plug in my JComponent as the status line.
If this is possible -- this is solved. I didn't check the trunk - is
it possible?
Comment 10 Peter Zavadsky 2003-11-27 10:14:47 UTC
No, it is not possible now.
There is just the mentioned issue #37289 to be able put the status
line into toolbar, but not replace the component.

So, now I'm thinking how to alow you to provide the component. Whether
via certain place in layer or what.
Comment 12 David Strupl 2004-02-13 16:55:17 UTC
I will make this issue the same as 32255 in order not to go into 2
review processes. They are very similar and I will provide only one
patch over there (that will solve both).

*** This issue has been marked as a duplicate of 32255 ***