[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: progress monitors

From: Andy Cutright <Andy.Cutright_at_borland.com>
Date: 2005-01-07 17:07:44 CET


i've found a workaround. there's a NullProgressMonitor implementation
provided by eclipse.

> -----Original Message-----
> From: Mark Phippard [mailto:MarkP@softlanding.com]
> I added that and some other options. I guess I just never
> considered they
> would be used any other way or in anything but Subclipse. If you are
> running headless, why wouldn't you just work directly with core or
> clientAdapter?
> Mark

our application is distributed and will have both GUI and headless
components. we're working within the eclipse/ OSGI framework, so we're
exploring using the team infrastructure. the GUI part should naturally
interact with the available subclipse functionality. keeping code
differences to a minimum, the headless and GUI components should share
as much code as possible. i'm trying to drive the headless stuff as
though the subclipse GUI code is calling it.

your implementation is perfectly reasonable. i imagine my use-case isn't
common. i think though eclipse typically lets the caller decide whether
to pass a monitor. either way, though, i've found a workaround :) thanks
for the feedback,

Received on Sat Jan 8 03:07:44 2005

This is an archived mail posted to the Subclipse Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.