Skip to main content
Jump to: navigation, search

Team FAQ

Revision as of 16:24, 22 June 2006 by (Talk | contribs) (Added some more FAQs)

Team API Questions

History API

I have an IHistoryPage implementation. How do I hook it up into the History View?

You have a number of options here:

  • Provide your own action that will show your object in the History View. You can get a handle to the History View by calling TeamUI.getHistoryView().You then call IHistoryView.showHistoryFor(Object) and pass the object that your action is triggered from.
  • Supply your own drag and drop adapter (see below)

What is the lifecyle of an IHistoryPage?

  • The user requests the history for an object (either by selecting an action, or dragging and dropping the object on the History View, or by clicking on an object with linking enabled on the History View).
  • For an IResource:
    1. Check to see if the resource is currently being displayed in the History View; if it is then IHistoryPage.refresh gets called to refresh the HistoryPage's contents.
      • If the resource is not found in the current page being displayed in the view, check to see if there are other view instances around (i.e. some History Views have been pinned) and if they contain the resource. If they do, bring them to the top, and refresh the page.
    2. If the view that the resource has been dropped on is pinned, first check to see if another view already contains that resource (if it does it is brought to the top and refreshed), if none does a new History View instance gets created.
    3. Try to get the RepositoryProvider from the resource, and get the IFileHistoryProvider from the RepositoryProvider. If an IFileHistoryProvider can be obtained, adapt it to a IHistoryPageSource. If no IFileHistoryProvider can be obtained from the RepositoryProvider, try to adapt the RepositoryProvider itself to an IHistoryPageSource.
    4. Check to see if the current page in the History View can handle the dropped item (call IHistoryPage.isValidInput), if it's not, it uses the IHistoryPageSource to create the page.
    5. Call setInput on HistoryPage, which will in turn call inputSet.
    6. Set the resource name as the content description.
    7. Dispose of the old page being shown in the view by calling dispose and dispose of the old page's subAction bars.
  • For an Object:
    1. Check to see if the Object adapts to IHistoryPageSource
    2. If the History View is currently showing a History page already, see if it knows how to display the dropped object; if it doesn't know how to display it create a new page and show it (same steps as in the resource case above)

How do I add drag-and-drop for my IHistoryPage?

  • The History View supplies a GenericHistoryDropAdapter which will handle DND for all IResources.
  • If you wish to add handling of custom objects, you need to provide an implementation of IDropActionDelegate and extend the org.eclipse.ui.dropActions extension point.

What is the difference between IHistoryPage.getName() and IHistoryPage.getDescription()

  • getName() is the name displayed in the History View for the Object being shown.
  • getDescription() can be a longer string describing the Object being shown.

What is an IHistoryPage expected to do on a setFocus() call?

Since clients are expected to subclass HistoryPage for their HistoryPage implementations, and HistoryPage extends Page, clients must provide a setFocus() implementation in their class. Clients can use this to pass the focus to whatever widget they are using for their page. This allows keystrokes to be routed to the current History Page.

When does createControl() get called?

When the History View needs to create a new history page, it will call IHistoryPageSource.createPage(Object). It will then call the createControl() on the returned Page.

Back to the top