From: Patrick W. <pat...@ny...> - 2008-07-31 20:56:21
|
But we shouldn't have to poll the filesystem to be aware of a commit. All Git operations should notify the workspace or our plugin to refresh automatically. Right? -- Patrick On Thu, 2008-07-31 at 16:54 -0400, Paul Munson Bethe wrote: > I tried using that, but I don't think it does what you think it does (that was part of my 2 days). > > If you can figure out how to use this instead, you are welcome... > but I think the idea for it was if you had a better method than file-system polling. > > But you see, when you commit a file, that file does not change. So hitting refresh does nothing. > And since the .git/ is a meta-file, it is not treated as an IResource... > That is why I went the route I did. > > -P > > > ----- Original Message ----- > From: Patrick Winters <pat...@ny...> > Date: Thursday, July 31, 2008 4:48 pm > Subject: Auto Refresh Provider > To: gitclipse-devel <git...@li...>, Paul Munson Bethe <pm...@ny...> > > > > Paul, > > I found this just now after I saw your DotGitMonitor. You can define > > a RefreshProvider in the framework that auto-polls resources and > > subdirectories and handles changes. > > > > http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/refresh/RefreshProvider.html > > -- > > Patrick > > > > |