Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[platform-core-dev] Re: Special notification rules need for move/rename/delete hooks?

We're not using the ISynchronizer mechanism here.  We're also
not running into any errors.  The move/rename/delete operations
are completing successfully.  So, everything is working just
fine.

However, I'm looking for a mechanism that the move/rename/delete
hook can use to inform interested parties that the state of the
directory has changed.  The ClearCase plugin would use this
mechanism to force itself to re-examine the directory.  It would
discover that the directory is now checked out and would paint
the directory's icon with the "checked out" decoration.  I'm not
sure what kind of delta would be most appropriate for this kind
of change (CONTENT?  CHANGED?).

Without this feature, a user does not have an accurate visual cue
that the directory is checked out (which they have on other
resources) and makes it easier for the user to forget that they
have to check in the directory before others can see the results
of the move/rename/delete.

				Peter

> -----Original Message-----
> Subject: Re: [platform-core-dev] Special notification rules 
> need for move/rename/delete
>  hooks?
> To: platform-core-dev@xxxxxxxxxxx
> From: "John Arthorne" <John_Arthorne@xxxxxxx>
> Date: Mon, 18 Nov 2002 10:10:06 -0500
> Reply-To: platform-core-dev@xxxxxxxxxxx
> 
> 
> Sorry for the slow response... we had a busy week with M3 testing last
> week.  What kind of delta would you expect to appear on a 
> checkout of a
> folder?  We don't track folder timestamps, so changed folders 
> don't appear
> as a content change.  Are you storing local sync info via the 
> ISynchronizer
> interface?  If you try performing a folder checkout within 
> the context of
> the move/delete hook are you running into an error?
>                                                              
>                       "Hack, Peter"                           
>                                                              
>                       <PHack@xxxxxxxxxxxx>            To:     
>   "'platform-core-dev@xxxxxxxxxxx'"                          
>                       Sent by:                         
> <platform-core-dev@xxxxxxxxxxx>                                     
>                       platform-core-dev-admin@        cc:     
>                                                              
>                       eclipse.org                     
> Subject:  Re: [platform-core-dev] Special notification rules need    
>                                                        for 
> move/      rename/delete hooks?                                 
>                                                               
>                                                              
>                       11/13/2002 12:23 PM                     
>                                                              
>                       Please respond to                       
>                                                              
>                       platform-core-dev                       
> 
>         When performing a move/rename/delete, ClearCase must
> check out the parent directory(s) of the files/directories
> being moved/renamed/deleted.  Depending on a preference set
> by the user, the parent directory(s) may be left in this new,
> checked out state.  I want this change picked up by Eclipse
> so plugins can act appropriately (ex. the ClearCase plugin
> would decorate the directory as checked out and enable the
> "Check in" menu item).
> 
>                                 Peter


Back to the top