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.
There is a request from our HIE, to have the multiview toggle buttons at the bottom instead at the top of multiview component. Provide that possibility on some switch.
reassigning
OK, here is our view of the problem: We frankly don't know if tabs on top or bottom are better or worse from HIE perspective, but to support both possibilities would be expensive more than it seems now. Consider this: - editor (form etc) toolbar issues, they can't be on bottom - look of buttons will probably have to be changed, as they don't look good alone. - tab placement will be global for product; OK how will behave modules designed for one type of tabs in another environment? - such "look defragmentation" among products is not desirable AFAIK Note, I'm not saying tabs on bottom is bad idea or good idea, no polemic. But due to the expensivness I mentioned, I would request HIE groups to try to settle on one solution. Tabs on top anywhere or tabs on bottom anywhere, this would be good solution for us. In other case, we would need to know real reasons why we should have multiview tabs on top for one application and on bottom for another. Please consider this to be official request to HIE groups, thank you.
We don't require to change the NB UI at all. Only thing we require is to provide a global switch, which will make the multiview tabs (only them!) to appear at the bottom instead of at the top. The arguments claiming it is expensive are not true, here are the answers: 1) editor toolbars can't be at bottom -> we don't want them to be at te bottom, let them be at the top as always; 2) look of buttons would need to be changed, since they look bad alone -> we don't want them to be changed, our HIE is satisfied with their look even they are alone; 3) tabs placement will be global, how it affects modules designed for other types of tabs -> we don't want have other tab types, use the same type, we only want them to appear at the bottom instead of the top, all modules using multiview are managed by us; 4) "look defragmentation" between products -> this argument doesn't make the implementation expensive, and it is up to HIE independent on this issue. We don't see any big expense.
Yo, at first it won't be too much work. But even if we are lucky at first, maintenance of extra option will always cost something. That's OK, but we should have a reason to do that - and I didn't see any single reason from any HIE group yet, so I'm not going to blindly implement it without asking. That's why I just kindly requested HIE groups (they are on cc) to sit together and gave me some real reasons why is Netbeans and Creator so different that we should support extra multi-view placement options. Or they may decide to settle on one tab placement. Now I'm awaiting the results of such talk.
Given the rave UI spec mentions the tabs to be placed on top, is this thiss an issue to work on for promoe? http://ucsd.sfbay/projects/developer-tools/projects/RAVE/thresher/UISpecs/multiview.html
The reason to have different Multiview switchers in Creator and in NB doesn't exist anymore. We discussed it with Creator's team in US and they will use NB implementation of Multiviews. We need to check if NB implementation fit in mentioned UI spec. What do you think Jeff?
Closing this, since now our HIE doesn't require that.