Re: [platform-core-dev] RE: Special notification rules need for move/ren

[Michael_Valenta@xxxxxxxxxx]

Yes, that is right. I don't think there's much Core could do anyway since only the ClearCase plugin knows that the resources have changed state (i.e. the checked out status of a resource is not a general property of a resource but is clearcase specific). As John pointed out, Core does provide the ISynchronizer which is included in the delta mechnism but it's not useful for you since ClearCase keeps the meta-data for a resource elsewhere already.

It's fairly straightforward to create your own notification mechanism. What we do for CVS is to accumulate a list of a resource whose CVS state has changed during an operation and then notify the DecoratorManager to update the labels for the resources once the operation is complete.

"Hack, Peter" <PHack@xxxxxxxxxxxx> Sent by: platform-core-dev-admin@xxxxxxxxxxx 01/29/2003 06:06 PM Please respond to platform-core-dev

To:        "'platform-core-dev@xxxxxxxxxxx'" <platform-core-dev@xxxxxxxxxxx>         cc:                 Subject:        [platform-core-dev] RE: Special notification rules need for move/rename/delete hooks?

                 Yes, this is the kind of behavior I want to end up
with.  I know the move/rename/delete hooks are restricted
in what they can do and:

a)  wanted to use an existing mechanism, if possible
b)  wanted to conform to the restrictions on hooks
c)  wanted the approach to be "blessed" by core experts

                 So it sounds like there is no existing, generic
mechanism that we can use.  We'll have to invent something
like you did for CVS, right?
                 Thanks!
                                                                    Peter

> To: platform-core-dev@xxxxxxxxxxx
> Subject: RE: [platform-core-dev] Re: Special notification 
> rules need for m                 ove/rename/delete
>  hooks?
> From: Michael_Valenta@xxxxxxxxxx
> Date: Tue, 28 Jan 2003 13:07:58 -0500
> Reply-To: platform-core-dev@xxxxxxxxxxx
> 
> This is a multipart message in MIME format.
> --=_alternative 00639AB185256CBC_=
> Content-Type: text/plain; charset="us-ascii"
> 
> Peter,
> 
> We have similar requirements with the CVS plugin. We 
> basically implemented 
> our own notification mechanism which is used to ensure our 
> decorators are 
> up-to-date. We make use of the move/delete hook, resource 
> deltas and CVS 
> operations to determine what change have taken place. From 
> these entry 
> points, we determine all the resources whose CVS sync state 
> has changed 
> and manually trigger a decorator refresh for these resources. 
> 
> Is this the type of mechanism you are talking about?
> 
> Michael
> 
_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-core-dev