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.
Desc: core/multiview module is module offering client general mechanism for displaying several perspectives, or views of data, which will be used consistently across whole IDE window system. API changes: two new interfaces will be exposed, with methods basically stolen from TopComponent class. Also XML config format will be exposed. All APIs will be non-stable. Dependencies: Module depens on openide. Core module is depending on core/multiview. Answers to part of arch questions attached.
Created attachment 14023 [details] arch answers for init phase
I will lead the review, Mila, Tomas and Pavel are the other assigned reviewers.
I don't see any of the docs actually listing the new API-visible interfaces.
the suggested APIs as commited by dsimonek. http://core.netbeans.org/source/browse/core/multiview/src/org/netbeans/core/multiview/Attic/
Created attachment 14479 [details] API javadoc
Created attachment 14480 [details] updated arch questions&answers
Accepted with TCRs: http://openide.netbeans.org/tutorial/reviews/opinions_41085.html
Oops, I need to reassign the issue to submitter.
all TCR and TCA are closed. closing this one as well.
I was asked to share my experience with using the multiview API - as part of (post)review of the API. So just briefly: - It was a pleasure to work with a clean Java API without hacking XML in layers and similar stuff ;) - It is a bit tricky to make the multiview work in the current environment using current components (keeping compatibility) - i.e. the editor support stuff and synchronization of the multiview TopComponent according to elements that are also TopComponents - opening the right elements in the right momements, delegating the right calls, etc. And there were many bugs in the core multiview impl. - Close relation between the element providers is required and lot of work needs to be done by the "multiview coordinator". The amount of new code needed in the form editor was really big. - The API seems to be a bit heavyweight to me for the other uses case it was planned for - i.e. for any "subtabs" UI, not only within the editor (documents). - The API does not allow to indpendent elements to be added to existing multiviews. This was not needed yet; the API will likely need to evolve in the future (but that should not be a problem). As for the review itself, it caught several problems and helped with smoother integration, but on the other hand nobody envisioned the problems of having "TopComponents in a TopComponent" - which was a source of many bugs. But implementing multiview was certainly a gain for the IDE. ;)
This issue was solved long time ago. Because nobody has reopened it neither added comments, we are verifying/closing it now. If you are still able to reproduce the problem, please reopen. Thanks in advance.