Eclipse Community Forums: GEF » why are some classes left out in later GEF integration builds?

Home » Eclipse Projects » GEF » why are some classes left out in later GEF integration builds?

why are some classes left out in later GEF integration builds? [message #66566]

Tue, 25 February 2003 20:51

Eclipse User

Originally posted by: timmerin.singnet.com.sg

I have noticed that current integration builds of GEF-SDK has left out
some classes in it's gefsrc.zip.

The classes in the following were present in the GEF-SDK I20030102.zip but
no longer present in GEF-SDK I20030225.zip.

1)DefaultPaletteCategory
2)DefaultPaletteContainer
3)DefaultPaletteEntry
4)DefaultPaletteGroup
5)DefaultPaletteRoot
6)DefaultPaletteToolEntry

If i use the latest GEF-SDK edition, i will run into compilation problems
as some of my code makes use of some of the missing classes.

Can anyone explain or tell me how i can fix the problem?

Thanks.

Re: why are some classes left out in later GEF integration builds? [message #66587 is a reply to message #66566]

Wed, 26 February 2003 02:19

Eclipse User

Originally posted by: andreas.rummler.tu-ilmenau.de

Joanie Goh schrieb:

> Can anyone explain or tell me how i can fix the problem?

These classes have been renamed:

DefaultPaletteCategory -> PaletteCategory
DefaultPaletteContainer -> PaletteContainer
and so on ...

Andreas Rummler

--
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++
+ Andreas Rummler +
+ Technical University of Ilmenau, Germany (__) +
+ Department Of Electronic Circuits & Systems (oo) +
+ \/-------\ +
+ MAIL: mailto:arummler@acm.org || | \ +
+ MAIL: mailto:andreas.rummler@tu-ilmenau.de ||----|| * +
+ WEB : http://www.inf-technik.tu-ilmenau.de/~rummler ~~ ~~ +
+ PGP : http://www.inf-technik.tu-ilmenau.de/~rummler/public.pgp +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots. So far, the universe is winning."
Richard Cook

Re: why are some classes left out in later GEF integration builds? [message #66607 is a reply to message #66566]

Wed, 26 February 2003 12:11

Eclipse User

Originally posted by: none.us.ibm.com

We did this for future compatibility sake. There was little reason to
separate these into interface + implementation. By removing the interface,
we can evolve the classes over time to satisfy future requests for the
palette. For example, some people want to be able to disable a palette tool
entry, but we currently don't support this.

When using an interface, you can never add new methods, and you end up with
things like:

interface PaletteEntry2 extends PaletteEntry {
boolean isEnabled();
}

Then you have to do instanceof checks, etc., you get the picture...

"Joanie Goh" <timmerin@singnet.com.sg> wrote in message
news:b3h6ja$m35$1@rogue.oti.com...
> I have noticed that current integration builds of GEF-SDK has left out
> some classes in it's gefsrc.zip.
>
> The classes in the following were present in the GEF-SDK I20030102.zip but
> no longer present in GEF-SDK I20030225.zip.
>
> 1)DefaultPaletteCategory
> 2)DefaultPaletteContainer
> 3)DefaultPaletteEntry
> 4)DefaultPaletteGroup
> 5)DefaultPaletteRoot
> 6)DefaultPaletteToolEntry
>
> If i use the latest GEF-SDK edition, i will run into compilation problems
> as some of my code makes use of some of the missing classes.
>
> Can anyone explain or tell me how i can fix the problem?
>
> Thanks.
>

Previous Topic:	Add new Category/ new Entry
Next Topic:	Problem using ScrollableThumbnail with ZoomManager

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Oct 31 02:15:08 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter