Skip to main content



      Home
Home » Archived » Visual Editor (VE) » use of internal apis
use of internal apis [message #126445] Mon, 19 June 2006 14:08 Go to next message
Eclipse UserFriend
I am using the following internal classes in my attempt to extend the
visual editor to generate code. Some of these classes are referenced in
the VE tutorial. Is it considered safe to use all these classes?

Thanks,
Ernest

import org.eclipse.jem.internal.instantiation.base.IJavaInstance;
import org.eclipse.jem.internal.proxy.core.IBeanProxy;
import org.eclipse.jem.internal.proxy.core.IBeanTypeProxy;
import org.eclipse.ve.internal.java.core.BeanProxyUtilities;
import org.eclipse.ve.internal.jfc.core.ComponentGraphicalEditPart;
import
org.eclipse.ve.internal.propertysheet.common.commands.Abstra ctCommand;
Re: use of internal apis [message #126458 is a reply to message #126445] Mon, 19 June 2006 16:00 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

For now yes. We don't have any actual API for much of the code. Some of
the base JEM stuff is API but JEM proxy and instantiation haven't been
made into API yet.

Ernest Pasour wrote:
> I am using the following internal classes in my attempt to extend the
> visual editor to generate code. Some of these classes are referenced in
> the VE tutorial. Is it considered safe to use all these classes?
>
> Thanks,
> Ernest
>
> import org.eclipse.jem.internal.instantiation.base.IJavaInstance;
> import org.eclipse.jem.internal.proxy.core.IBeanProxy;
> import org.eclipse.jem.internal.proxy.core.IBeanTypeProxy;
> import org.eclipse.ve.internal.java.core.BeanProxyUtilities;
> import org.eclipse.ve.internal.jfc.core.ComponentGraphicalEditPart;
> import
> org.eclipse.ve.internal.propertysheet.common.commands.Abstra ctCommand;

--
Thanks,
Rich Kulp
Re: use of internal apis [message #126510 is a reply to message #126458] Tue, 20 June 2006 08:28 Go to previous message
Eclipse UserFriend
Great! Thank you!

Rich Kulp wrote:
> For now yes. We don't have any actual API for much of the code. Some of
> the base JEM stuff is API but JEM proxy and instantiation haven't been
> made into API yet.
>
> Ernest Pasour wrote:
>> I am using the following internal classes in my attempt to extend the
>> visual editor to generate code. Some of these classes are referenced
>> in the VE tutorial. Is it considered safe to use all these classes?
>>
>> Thanks,
>> Ernest
>>
>> import org.eclipse.jem.internal.instantiation.base.IJavaInstance;
>> import org.eclipse.jem.internal.proxy.core.IBeanProxy;
>> import org.eclipse.jem.internal.proxy.core.IBeanTypeProxy;
>> import org.eclipse.ve.internal.java.core.BeanProxyUtilities;
>> import org.eclipse.ve.internal.jfc.core.ComponentGraphicalEditPart;
>> import
>> org.eclipse.ve.internal.propertysheet.common.commands.Abstra ctCommand;
>
Re: use of internal apis [message #613367 is a reply to message #126445] Mon, 19 June 2006 16:00 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

For now yes. We don't have any actual API for much of the code. Some of
the base JEM stuff is API but JEM proxy and instantiation haven't been
made into API yet.

Ernest Pasour wrote:
> I am using the following internal classes in my attempt to extend the
> visual editor to generate code. Some of these classes are referenced in
> the VE tutorial. Is it considered safe to use all these classes?
>
> Thanks,
> Ernest
>
> import org.eclipse.jem.internal.instantiation.base.IJavaInstance;
> import org.eclipse.jem.internal.proxy.core.IBeanProxy;
> import org.eclipse.jem.internal.proxy.core.IBeanTypeProxy;
> import org.eclipse.ve.internal.java.core.BeanProxyUtilities;
> import org.eclipse.ve.internal.jfc.core.ComponentGraphicalEditPart;
> import
> org.eclipse.ve.internal.propertysheet.common.commands.Abstra ctCommand;

--
Thanks,
Rich Kulp
Re: use of internal apis [message #613371 is a reply to message #126458] Tue, 20 June 2006 08:28 Go to previous message
Eclipse UserFriend
Great! Thank you!

Rich Kulp wrote:
> For now yes. We don't have any actual API for much of the code. Some of
> the base JEM stuff is API but JEM proxy and instantiation haven't been
> made into API yet.
>
> Ernest Pasour wrote:
>> I am using the following internal classes in my attempt to extend the
>> visual editor to generate code. Some of these classes are referenced
>> in the VE tutorial. Is it considered safe to use all these classes?
>>
>> Thanks,
>> Ernest
>>
>> import org.eclipse.jem.internal.instantiation.base.IJavaInstance;
>> import org.eclipse.jem.internal.proxy.core.IBeanProxy;
>> import org.eclipse.jem.internal.proxy.core.IBeanTypeProxy;
>> import org.eclipse.ve.internal.java.core.BeanProxyUtilities;
>> import org.eclipse.ve.internal.jfc.core.ComponentGraphicalEditPart;
>> import
>> org.eclipse.ve.internal.propertysheet.common.commands.Abstra ctCommand;
>
Previous Topic:Visual Editor and EMF
Next Topic:Visual Editor and EMF
Goto Forum:
  


Current Time: Thu Jun 19 12:08:47 EDT 2025

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

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

Back to the top