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 198115 - embedded history tab in files topcomponent
Summary: embedded history tab in files topcomponent
Status: NEW
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.0
Hardware: PC Mac OS X
: P1 normal (vote)
Assignee: Ondrej Vrabec
URL: http://wiki.netbeans.org/EditorHistor...
Keywords: PLAN
Depends on: 200419 200424 200425 200427 200428 204249
Blocks:
  Show dependency tree
 
Reported: 2011-04-27 07:31 UTC by Tomas Stupka
Modified: 2015-04-03 09:23 UTC (History)
5 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Stupka 2011-04-27 07:31:02 UTC
consider showing a files history (localhistory, vcs history) in a tab directly in the files topcomponent
Comment 1 Petr Jiricka 2011-07-26 15:22:41 UTC
For reference, here is the relevant wiki page: http://wiki.netbeans.org/EditorHistoryTab
Comment 2 Vladimir Voskresensky 2011-07-29 09:17:54 UTC
It's nice that MultiViews are now easily registered, but can we see somewhere UI request/review why "Local History" is now exposed so widely for all editors?
+ 
due to this change now all data objects depend on multi view module and for applications based on nb platform it introduces one more dependent module.
How to prevent this if only basic editor functionality is needed in application?
Comment 3 Tomas Stupka 2011-07-29 09:27:10 UTC
(In reply to comment #2)
> It's nice that MultiViews are now easily registered, but can we see somewhere
> UI request/review why "Local History" is now exposed so widely for all editors?
see UI Spec in http://wiki.netbeans.org/EditorHistoryTab 


> due to this change now all data objects depend on multi view module and for
> applications based on nb platform it introduces one more dependent module.
> How to prevent this if only basic editor functionality is needed in
> application?
cc yarda
Comment 4 Jan Becicka 2011-08-02 09:10:49 UTC
There is no guide for existing multi view implementations.
I found this:

Rewrite already existing multiviews
a possible inspiration could be the Form module. See org.netbeans.modules.form.FormDesigner.java and org.netbeans.modules.form.FormEditorSupport.java.

FormDesigner and FormEditorSupport has about 4000 lines of code.
Comment 5 Jaroslav Tulach 2011-08-05 12:58:45 UTC
> > due to this change now all data objects depend on multi view module and for
> > applications based on nb platform it introduces one more dependent module.
> > How to prevent this if only basic editor functionality is needed in
> > application?
> cc yarda

The MultiDataObject.registerEditor method might be of some help. It finds out whether core.multiview API is around or not and calls to it using reflection. Thus, if using MultiDataObject.registerEditor is enough, you don't need to change your dependencies at all.