Bug 10

Description Jean-Michel Lemieux 2001-10-10 21:34:55 EDT

There seems to be a need for a VCM Event notification model, along the lines
of the activity notification and resource change notification.  This would only
notify listeners when local VCM API had been manipulated, it wouldn't notify
changes that have occurred on the server.  For example, notification of the
following events (and possibly others) would greatly improve my ability to
maintain a well refreshed UI:

- repository creation/deletion
- team stream creation/deletion
- team stream lock/unlock
- setSharing of project to team stream
- project version creation/deletion
- catchup/release to/from team stream

Without such a notification method, we're left with a LotusNotesian "Press F9
to refresh" UI model. For example, the user has a view open that shows a list
of the currently known team streams.  The user then creates a new team stream.
S/he will then have to press F9 on the team stream view to make it include the
TS they've just created.  We cannot link the team stream creation wizard and the
team stream view at the UI level, because they might well have been created by
different plugins that don't know about each other.

Also, repository deletion is not currently supported.  By deletion I mean removal
of the repository from the list of the workspace's known repositories.  Once the
known repositories list is persistent, there will be a need to remove items from
the list to prevent it from growing indefinitely.

NOTES:

BB (2/1/01 11:57:12 AM)
	For a first cut, see
		>IVCMEvent 0.4 000
		>IVCMListener 0.4 000
		>IVCMProvider 0.3 010

JA 2/1/01
Some possible additional event types:

- change in resource transience.
 -create/delete project version

As a side note, you might consider using IVCMListener.handleEvent
instead of IVCMListener.vcmEvent.  It is more in line with other event/listener
pairs in Eclipse.

BB (2/2/01 2:51:14 PM)
	We should change IActivityListener.activityEvent too. (-> IActivityListener.handleEvent)

KM (4/6/01 12:13:55 PM)
	Prioritization:
	Important:
	- update labels (navigator) and property sheets when loading/versioning (explicit refresh)
	- update sync info on resource change (vcm provider becomes a delta listener)
	- update prop sheet when change in sharing

	Nice to have but can be dropped:
	- show creation of new repo connections, streams
	- update repo stream children when releasing
	- update version list when versioning

BB (5/11/2001 12:29:33 PM)
	Implemented events for creation/deletion of repositories/team streams.

JohnA (5/11/2001 6:24:49 PM)
	Implemented event listening for creation/deletion of repositories/team streams.