Skip to main content



      Home
Home » Eclipse Projects » GEF » Dumb's man guide to porting GEF 2.0 application to GEF 1.0 / WSAD 4.0.3
Dumb's man guide to porting GEF 2.0 application to GEF 1.0 / WSAD 4.0.3 [message #21758] Fri, 27 September 2002 09:04 Go to next message
Eclipse UserFriend
Hello,

Here is my dumb quest: I am trying to understand GEF using the latest
version on Eclipse 2.0.1,
then I try to see what I can port to GEF 1.0 with is part of the
commercially available WSAD 4.0.3...

Why? because it will take a good while until all WSAD 4.0.3 customers
migrate to WSAD 5.0,
and further more, if GEF in WebSphere Studio Workbench 2.0.1 reflects the
version
in WSAD 5.0 GA, then we are in trouble anyway developping with latest GEF,
because
refactoring of com.ibm.etools.gef into org.eclipse.gef (and other similars)
have not happend.

I guess I am not alone (in the dark ;-). Feel free to join me in this dumb
man's quest!

So, until now I have succeeded into creating a minimal GEF 1.0 editor blank
page that work with WSAD 4.0.3.
I just do not understand why the compiler barks on
com.ibm.etools.gef.ui.parts.GraphicalEditor

being deprecated.

If it can help, here is a snipped of my GEF 1.0 working "blank GEF" editor.
It does nothing but openning a GEF editor in which you can click & drag the
mouse to draw nice selection rectangles ;-) Note that the commented code
with "Eclipse 2.0" means deleted code that used to work with latest GEF
version...


package org.giveawaytogefnewsgroup;

import org.eclipse.core.resources.IMarker;
import org.eclipse.core.runtime.IProgressMonitor;
import org.eclipse.ui.IEditorInput;
import org.eclipse.ui.IEditorSite;
import org.eclipse.ui.PartInitException;


import com.ibm.etools.gef.DefaultEditDomain;
import com.ibm.etools.gef.GraphicalViewer;
import com.ibm.etools.gef.palette.PaletteRoot;
import com.ibm.etools.gef.ui.parts.GraphicalEditor;
import com.ibm.etools.gef.ui.parts.GraphicalRootEditPart;


/*
// Eclipse 2.0
import org.eclipse.gef.DefaultEditDomain;
import org.eclipse.gef.GraphicalViewer;
import org.eclipse.gef.ui.parts.FreeformGraphicalRootEditPart;
import org.eclipse.gef.ui.parts.GraphicalEditor;
import org.eclipse.gef.ui.parts.GraphicalRootEditPart;
*/

import com.dassault_systemes.gefave.model.HelloModel;

/**
* Sample GEF editor.
*/
public class GefHelloEditor extends GraphicalEditor
{
public GefHelloEditor()
{
System.out.println("Called GefHelloEditor() constructor");

// Eclipse 2.0 setEditDomain(new DefaultEditDomain(this));
}


/**
* @see org.eclipse.ui.IEditorPart#init(IEditorSite, IEditorInput)
**/
public void init(IEditorSite iSite, IEditorInput iInput) throws
PartInitException
{
System.out.println("Called GefHelloEditor.init("+iSite+","+iInput+")");

setSite(iSite);
init(); // Eclipse 1.0
setInput(iInput);

System.out.println("return from
GefHelloEditor.init("+iSite+","+iInput+")");
}


/**
* @see
org.eclipse.gef.ui.parts.GraphicalEditor#initializeGraphical Viewer()
**/
/** Eclipse 2.0
protected void initializeGraphicalViewer()
{
System.out.println("Called GefHelloEditor.initializeGraphicalViewer()");
getGraphicalViewer().setContents(new HelloModel());
}
*/

/**
* @see org.eclipse.ui.IEditorPart#isSaveAsAllowed()
**/
public boolean isSaveAsAllowed()
{
System.out.println("Called GefHelloEditor.isSaveAsAllowed()");

return false;
}

/**
* @see org.eclipse.ui.IEditorPart#doSave(IProgressMonitor)
**/
public void doSave(IProgressMonitor iMonitor)
{
System.out.println("Called GefHelloEditor.doSave("+iMonitor+")");
}

/**
* @see org.eclipse.ui.IEditorPart#doSaveAs()
**/
/** Eclipse 2.0
public void doSaveAs()
{
System.out.println("Called GefHelloEditor.doSaveAs()");
}
*/

/**
* @see org.eclipse.ui.IEditorPart#gotoMarker(IMarker)
**/
public void gotoMarker(IMarker iMarker)
{
System.out.println("Called GefHelloEditor.gotoMarker("+iMarker+")");
}


/**
* @see org.eclipse.ui.IEditorPart#isDirty()
**/
public boolean isDirty()
{
System.out.println("Called GefHelloEditor.isDirty()");

return false;
}


/**
* @see
org.eclipse.gef.ui.parts.GraphicalEditor#configureGraphicalV iewer()
**/
/** Eclipse 2.0
protected void configureGraphicalViewer()
{
System.out.println("Called GefHelloEditor.configureGraphicalViewer()");

super.configureGraphicalViewer();
GraphicalViewer viewer = getGraphicalViewer();
// viewer.setRootEditPart(new FreeformGraphicalRootEditPart());
viewer.setRootEditPart(new GraphicalRootEditPart());
viewer.setEditPartFactory(new GraphicalPartFactory());

System.out.println("return from
GefHelloEditor.configureGraphicalViewer()");

}
*/

/**
* This method is only required in Eclipse 1.0
* @see com.ibm.etools.gef.ui.parts.GraphicalEditor#getPaletteRoot()
**/
protected PaletteRoot getPaletteRoot()
{
return null;
}

/**
* This method is only required in Eclipse 1.0
* @see com.ibm.etools.gef.ui.parts.GraphicalEditor#performSaveAs()
**/
protected boolean performSaveAs()
{
return false;
}


protected void initViewers()
{
System.out.println("Called GefHelloEditor.initViewers()");
}
}
Re: Dumb's man guide to porting GEF 2.0 application to GEF 1.0 / WSAD 4.0.3 [message #21806 is a reply to message #21758] Fri, 27 September 2002 09:07 Go to previous messageGo to next message
Eclipse UserFriend
I forgot to mention that, before starting my GEF 2.0->GEF 1.0 dumb quest, I
have tried to install GEF 2.0
on WSAD 4.0.3. The error message I got was that the

org.eclipse.ui.IWorkbenchSite

interface is missing. Could it be I missed myself a trivial issue, or is GEF
2.0.x actually hard-wired to Eclipse 2.0.x ?

Alex.
Re: Dumb's man guide to porting GEF 2.0 application to GEF 1.0 / WSAD 4.0.3 [message #21939 is a reply to message #21758] Fri, 27 September 2002 11:50 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: hudsonr.us.eye-bee-em.com

"Alexandre Vermeerbergen" <ave@ds-fr.com> wrote in message
news:an1js2$abd$1@rogue.oti.com...
> Hello,
>
> Here is my dumb quest: I am trying to understand GEF using the latest
> version on Eclipse 2.0.1,
> then I try to see what I can port to GEF 1.0 with is part of the
> commercially available WSAD 4.0.3...
>
> Why? because it will take a good while until all WSAD 4.0.3 customers
> migrate to WSAD 5.0,
> and further more, if GEF in WebSphere Studio Workbench 2.0.1 reflects the
> version
> in WSAD 5.0 GA, then we are in trouble anyway developping with latest GEF,
> because
> refactoring of com.ibm.etools.gef into org.eclipse.gef (and other
similars)
> have not happend.

If you are targeting WSAD 5.0, you can use either the GEF found in WSWB 2.0
(which is com.ibm), or you could use org.eclipse.gef. You should pick
whichever one suits your needs. WSWB 2.0.1 is immediately available. The
ORG.eclipse.gef version is not yet available, but will have additional
features. What is the trouble you are talking about? When org.eclipse.gef
is released, you can redistribute it into WSAD 5.0, and it will work.
Re: Dumb's man guide to porting GEF 2.0 application to GEF 1.0 / WSAD 4.0.3 [message #21984 is a reply to message #21806] Fri, 27 September 2002 11:52 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: hudsonr.us.eye-bee-em.com

"Alexandre Vermeerbergen" <ave@ds-fr.com> wrote in message
news:an1k0v$adv$1@rogue.oti.com...
> I forgot to mention that, before starting my GEF 2.0->GEF 1.0 dumb quest,
I
> have tried to install GEF 2.0
> on WSAD 4.0.3. The error message I got was that the
>
> org.eclipse.ui.IWorkbenchSite
>
> interface is missing. Could it be I missed myself a trivial issue, or is
GEF
> 2.0.x actually hard-wired to Eclipse 2.0.x ?

Yes, doesn't the GEF plugin requirement statement specify 2.0.0? Eclipse
2.0 plugins do not run on Eclipse 1.0.
Re: Dumb's man guide to porting GEF 2.0 application to GEF 1.0 / WSAD 4.0.3 [message #22502 is a reply to message #21939] Mon, 30 September 2002 03:32 Go to previous messageGo to next message
Eclipse UserFriend
Randy:

It is not the first time I read in this newsgroup your answer to similar
question:

Each time somebody tries to run GEF on WSAD 4.0.3 or WSWB 1.0 or Eclipse
1.0,
your answer is to switch to Eclipse 2.0.x or wait for WSAD 5.0

While I understand that you don't want to maintain older GEF versions, the
logical
diagram editor example that used to work with Eclipse 1.0, WSWB 1.0, WSAD
4.0.3 shows
that a great deal of graph UI can be acheived with *currently deployed
software*.

Switch from Eclipse 1.0 to Eclipse 2.0 is easy, but switch from WSAD 4.0.3
to WSAD 5.0
will likely take much more time because:

- companies that bought WSAD 4.0.x and deployed it for production use are
likely to want to throughly WSAD 5.x on non-crital projects until they
are confident
with this new release... and you know IT decision makers rule: never
trusts a x.0 release ;-)

- some companies will not migrate from WSAD 4.0.3 to WSAD 5.x at all: either
because
they don't see the interest of paying the for a new version if current
version works for their
needs ; or more often because they developped a big piece of software
with WSAD 4.x
that they want to keep for application maintenance purposes, they don't
even want to
to try WSAD 5.x to see what impacts it could have on their deployed
application (if it
runs, don't break it)

Eventually, WSAD 5.x will have its customer base, but for developpers who
want (or are
asked) to bridge the gap between WSAD 4 and WSAD 5, trying to run GEF 1.0
despite
lack of new developments on GEF 1.0 core itselves may be worth.

Does it makes sense to anybody else reading this newsgroup? please, react!

Alex.



"Randy Hudson" <hudsonr@us.eye-bee-em.com> wrote in message
news:an1tiu$hhf$1@rogue.oti.com...
> "Alexandre Vermeerbergen" <ave@ds-fr.com> wrote in message
> news:an1js2$abd$1@rogue.oti.com...
> > Hello,
> >
> > Here is my dumb quest: I am trying to understand GEF using the latest
> > version on Eclipse 2.0.1,
> > then I try to see what I can port to GEF 1.0 with is part of the
> > commercially available WSAD 4.0.3...
> >
> > Why? because it will take a good while until all WSAD 4.0.3 customers
> > migrate to WSAD 5.0,
> > and further more, if GEF in WebSphere Studio Workbench 2.0.1 reflects
the
> > version
> > in WSAD 5.0 GA, then we are in trouble anyway developping with latest
GEF,
> > because
> > refactoring of com.ibm.etools.gef into org.eclipse.gef (and other
> similars)
> > have not happend.
>
> If you are targeting WSAD 5.0, you can use either the GEF found in WSWB
2.0
> (which is com.ibm), or you could use org.eclipse.gef. You should pick
> whichever one suits your needs. WSWB 2.0.1 is immediately available. The
> ORG.eclipse.gef version is not yet available, but will have additional
> features. What is the trouble you are talking about? When
org.eclipse.gef
> is released, you can redistribute it into WSAD 5.0, and it will work.
>
>
Re: Dumb's man guide to porting GEF 2.0 application to GEF 1.0 / WSAD 4.0.3 [message #22546 is a reply to message #22502] Mon, 30 September 2002 10:48 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: hudsonr.us.eye-bee-em.com

> It is not the first time I read in this newsgroup your answer to similar
> question:
>
> Each time somebody tries to run GEF on WSAD 4.0.3 or WSWB 1.0 or Eclipse
> 1.0,
> your answer is to switch to Eclipse 2.0.x or wait for WSAD 5.0

I wasn't responding to your comments about WSAD 4.0.3 and WSWB 1.0. I was
responding to your comments about WSWB 2.0.X, and WSAD 5. Specifically:

> > > Why? because it will take a good while until all WSAD 4.0.3 customers
> > > migrate to WSAD 5.0,
> > > and further more, if GEF in WebSphere Studio Workbench 2.0.1 reflects
the
> > > version
> > > in WSAD 5.0 GA, then we are in trouble anyway developping with latest
GEF,
> > > because
> > > refactoring of com.ibm.etools.gef into org.eclipse.gef (and other
> > similars)
> > > have not happend.

I thought you were saying that *IF* you were developing for WebSphere Studio
Workbench 2.0.1 that you would be in trouble because GEF is still com.ibm in
that product. It is still com.ibm, and that won't change until later, but
there is no reason that you couldn't distribute org.eclipse.GEF onto
WebSphere Studio Workbench 2.0.1. That was my point, that you could use the
new GEF with WSAD 5.



As far as WSAD 4.x.x and new GEF features, this won't happen. For similar
reasons, IBM won't [I'm speculating] be adding any new features to WSAD 4 or
upgrading their EJB support to new levels of the Spec.
But seeing as how GEF is now distributed under open-source, there is no
reason that you couldn't take org.eclipse.gef 2.?.?, and back-port it to
WSAD 4.x.x. This should be easy. The only ramifications would be that you
would have to make the port available to the public.
Re: Dumb's man guide to porting GEF 2.0 application to GEF 1.0 / WSAD 4.0.3 [message #22763 is a reply to message #22546] Wed, 02 October 2002 03:11 Go to previous message
Eclipse UserFriend
Randy:

"Randy Hudson" <hudsonr@us.eye-bee-em.com> wrote in message
news:an9n1r$r3f$1@rogue.oti.com...
> ...
> But seeing as how GEF is now distributed under open-source, there is no
> reason that you couldn't take org.eclipse.gef 2.?.?, and back-port it to
> WSAD 4.x.x. This should be easy. The only ramifications would be that
you
> would have to make the port available to the public.

Ahhhh.... very astute solution indeed!
Let me think about it... I need to investigate "how easy" it could be.

Thank you very much

Alex.

PS: <joke>you have such a gift to return people's expectations into
something like "instead of asking what the [open source] community can do
for you, try doing it for the community ;-)" Have you ever tried to do
politics? </joke>
Previous Topic:Using TreeViewer with GrapicalViewerWithPalette
Next Topic:SWTError: No more handles
Goto Forum:
  


Current Time: Sat Jul 05 00:24:00 EDT 2025

Powered by FUDForum. Page generated in 0.03540 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top