Eclipse Community Forums: Eclipse Platform » -> How tied is the connection between IProgressMonitor and platform.core

Home » Eclipse Projects » Eclipse Platform » -> How tied is the connection between IProgressMonitor and platform.core

-> How tied is the connection between IProgressMonitor and platform.core [message #129902]

Tue, 16 September 2003 00:12

Eclipse User

Hi there,

I was talking with Simon (Arsenault) about the platform dependence of
the IWizard
implementations. He stated out that the IProgressMonitor implementations
mainly
depend/are part of the platform.core packages of eclipse. Therefore the
'normal'
wizards also depend on the core packages.

The question we couldn't answer this far:

Q: Why is the IProgressMonitor depending that much on the platform rather
then
being part of JFace?

Thanks

Martin (Kersten)

PS: Orginal-thread 'SWT vs. JFace' can be found at the eclipse.platform.swt
newsgroup.

Re: -> How tied is the connection between IProgressMonitor and platform.core [message #129917 is a reply to message #129902]

Tue, 16 September 2003 01:06

Eclipse User

Originally posted by: ThisisFake.Fakeness.xyz

On Tue, 16 Sep 2003 06:12:58 +0200, Martin Kersten wrote:

> Hi there,
>
> I was talking with Simon (Arsenault) about the platform dependence of
> the IWizard
> implementations. He stated out that the IProgressMonitor implementations
> mainly
> depend/are part of the platform.core packages of eclipse. Therefore the
> 'normal'
> wizards also depend on the core packages.
>
> The question we couldn't answer this far:
>
> Q: Why is the IProgressMonitor depending that much on the platform rather
> then
> being part of JFace?
>
>
> Thanks
>
> Martin (Kersten)
>
> PS: Orginal-thread 'SWT vs. JFace' can be found at the eclipse.platform.swt
> newsgroup.

I can see how the visual aspects of ProgressMonitor would be related
strongly to JFace, but aren't their other elements of this class that are
not related to JFace? I dont entirely know how the class works, but it
seems rather strange to be passing around a Graphic object into functions
that don't know about graphics. so I imagine the non-graphic aspects are
what depends on the core so much. so the graphic elements can come from a
UI package, but the updating functionality should be from the core I would
imagine.

thats my opinion, but I am new to eclipse.

CL

Re: -> How tied is the connection between IProgressMonitor and platform.core [message #130051 is a reply to message #129917]

Tue, 16 September 2003 06:22

Eclipse User

> > Q: Why is the IProgressMonitor depending that much on the platform
rather
> > then
> > being part of JFace?
> I can see how the visual aspects of ProgressMonitor would be related
> strongly to JFace, but aren't their other elements of this class that are
> not related to JFace? I dont entirely know how the class works, but it
> seems rather strange to be passing around a Graphic object into functions
> that don't know about graphics. so I imagine the non-graphic aspects are
> what depends on the core so much. so the graphic elements can come from a
> UI package, but the updating functionality should be from the core I would
> imagine.
>
> thats my opinion, but I am new to eclipse.

Well the question is, would this class be a usefull add to JFace. You know
Wizards are usefull for every kind of application. And a ProgressMonitor
is also a very usefull thing to create wizards. So it would be nice add.
Maybe
the functionallity may be split. You know having a JFace implementation of
ProgressBar and a more 'core' dependend implementation.

Would ease some tasks I think,

Martin (KErsten)

Re: -> How tied is the connection between IProgressMonitor and platform.core [message #130362 is a reply to message #130051]

Tue, 16 September 2003 14:24

Eclipse User

Originally posted by: richkulp.NO--SPAM.us.ibm.com

The main reason that I can think of for IProgressMonitor being in the
core is so that core functions can "use" a progressmonitor without
having to pre-req any visual plugins. This happens with many of the core
API, then can be passed in an IProgressMonitor. This way they can do
there stuff, update the monitor as required, all without forcing UI code
to be present.

Rich

Re: -> How tied is the connection between IProgressMonitor and platform.core [message #130455 is a reply to message #129902]

Tue, 16 September 2003 16:53

Eclipse User

Originally posted by: John_Arthorne.oti.com_

The interface is defined in core (for the reason Rich states), but the
implementation is typically in the UI. If you're hacking JFace, it
should be easy to copy this interface (and perhaps a couple of other
small utilities) over without having to worry about further coupling
with core.
--

Martin Kersten wrote:
> Hi there,
>
> I was talking with Simon (Arsenault) about the platform dependence of
> the IWizard
> implementations. He stated out that the IProgressMonitor implementations
> mainly
> depend/are part of the platform.core packages of eclipse. Therefore the
> 'normal'
> wizards also depend on the core packages.
>
> The question we couldn't answer this far:
>
> Q: Why is the IProgressMonitor depending that much on the platform rather
> then
> being part of JFace?
>
>
> Thanks
>
> Martin (Kersten)
>
> PS: Orginal-thread 'SWT vs. JFace' can be found at the eclipse.platform.swt
> newsgroup.
>
>

Re: -> How tied is the connection between IProgressMonitor and platform.core [message #131296 is a reply to message #130455]

Wed, 17 September 2003 17:24

Eclipse User

> The interface is defined in core (for the reason Rich states), but the
> implementation is typically in the UI. If you're hacking JFace, it
> should be easy to copy this interface (and perhaps a couple of other
> small utilities) over without having to worry about further coupling
> with core.
Yeah but this would make some problems. One of my concerns is
having a plugin component which does only depend on Wizard and
want to test it using SWT rather than a PDE test case.

Also I would be glad to see IProgressMonitor becoming a part of
the JFace API. I guess it is a helpfull and important capability of
the current wizard implementation. It also wouldn't create any
broken API I guess - Having two versions of IProgressMonitor.
One being part of JFace and one 'dummy' being part of core
and extending the jface version.

Is there a reason, why the ProgressMonitor shouldn't become
part of JFace? Simon stated that beside the ProgressMonitor
dependency, the wizard is free of dependencies.

Thanks,

Martin (Kersten)

> --
>
> Martin Kersten wrote:
> > Hi there,
> >
> > I was talking with Simon (Arsenault) about the platform dependence
of
> > the IWizard
> > implementations. He stated out that the IProgressMonitor implementations
> > mainly
> > depend/are part of the platform.core packages of eclipse. Therefore the
> > 'normal'
> > wizards also depend on the core packages.
> >
> > The question we couldn't answer this far:
> >
> > Q: Why is the IProgressMonitor depending that much on the platform
rather
> > then
> > being part of JFace?
> >
> >
> > Thanks
> >
> > Martin (Kersten)
> >
> > PS: Orginal-thread 'SWT vs. JFace' can be found at the
eclipse.platform.swt
> > newsgroup.
> >
> >
>

Re: -> How tied is the connection between IProgressMonitor and platform.core [message #132390 is a reply to message #131296]

Thu, 18 September 2003 15:41

Eclipse User

Originally posted by: John_Arthorne.oti.com_

Core can't have any dependency on JFace. Core can be used stand-alone,
in an headless Ant script, as part of a Swing app, etc. There is no
relationship from core components to any UI component. There can't be
two copies of the same type because they would not be compatible at runtime.
--

Martin Kersten wrote:
> Also I would be glad to see IProgressMonitor becoming a part of
> the JFace API. I guess it is a helpfull and important capability of
> the current wizard implementation. It also wouldn't create any
> broken API I guess - Having two versions of IProgressMonitor.
> One being part of JFace and one 'dummy' being part of core
> and extending the jface version.
>
> Is there a reason, why the ProgressMonitor shouldn't become
> part of JFace? Simon stated that beside the ProgressMonitor
> dependency, the wizard is free of dependencies.

Re: -> How tied is the connection between IProgressMonitor and platform.core [message #133427 is a reply to message #132390]

Fri, 19 September 2003 20:45

Eclipse User

> Core can't have any dependency on JFace. Core can be used stand-alone,
> in an headless Ant script, as part of a Swing app, etc. There is no
> relationship from core components to any UI component. There can't be
> two copies of the same type because they would not be compatible at
runtime.
I am talking about one type extending an other.. so they are compatible (at
least
one of them with the other).

I just would like to see IProgressMonitor (or something similar) declared
as part of JFace because its helpfull and I would have to hack a castrated
version of core to make it accessable. Is there a clear paper stating out
why the decision about IProgressMonitor was made?

Thanks, and sorry for bothering you, but I want to understand this...

Martin (Kersten)

> --
>
> Martin Kersten wrote:
> > Also I would be glad to see IProgressMonitor becoming a part of
> > the JFace API. I guess it is a helpfull and important capability of
> > the current wizard implementation. It also wouldn't create any
> > broken API I guess - Having two versions of IProgressMonitor.
> > One being part of JFace and one 'dummy' being part of core
> > and extending the jface version.
> >
> > Is there a reason, why the ProgressMonitor shouldn't become
> > part of JFace? Simon stated that beside the ProgressMonitor
> > dependency, the wizard is free of dependencies.
>

Previous Topic:	How to build only a couple of projects and not ALL projects on Rebuild All
Next Topic:	Cannot find plugin: org.eclipse.core.boot

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 13 10:22:50 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter