Skip to main content



      Home
Home » Archived » Visual Editor (VE) » Adding 3rd party beans to VE
Adding 3rd party beans to VE [message #56095] Sun, 15 August 2004 11:05 Go to next message
Eclipse UserFriend
Originally posted by: conanjb.comcast.net

Is it possible to add/import 3rd party beans into the VE bean selector?
I have some commercial beans that I've used with VCafe and I would like
to be able to use them within VE.

If this is possible can someone direct me to instructions on how to
achieve this. If it's not possible, are there plans to provide for this
feature in the future?

TIA

jb
Re: Adding 3rd party beans to VE [message #56149 is a reply to message #56095] Mon, 16 August 2004 11:16 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.NO.SPAM.us.ibm.com

The simplest way is to just add the jar to the build path of the
project. Then the choose bean will see it and you can select them. The
biggest problem is if there are BeanInfo classes. If there are and they
are in different jars or in different packages you need to tell the user
how to use the BeanInfo path in the project's properties how to find the
beaninfo jar and add the beaninfo classes to search path.


--
Thanks, Rich Kulp

Re: Adding 3rd party beans to VE [message #56227 is a reply to message #56149] Tue, 17 August 2004 09:19 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: conanjb.comcast.net

Thanks. That works great. One other question: Is there any way of having
the these 3rd party beans appear in the bean palette?

jb

In article <cfqius$5jj$1@eclipse.org>, richkulp@NO.SPAM.us.ibm.com
says...
> The simplest way is to just add the jar to the build path of the
> project. Then the choose bean will see it and you can select them. The
> biggest problem is if there are BeanInfo classes. If there are and they
> are in different jars or in different packages you need to tell the user
> how to use the BeanInfo path in the project's properties how to find the
> beaninfo jar and add the beaninfo classes to search path.
>
>
>
Re: Adding 3rd party beans to VE [message #56244 is a reply to message #56227] Tue, 17 August 2004 12:12 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.NO.SPAM.us.ibm.com

Now you are getting into a difficult area. :-) We don't have a way yet
of customizing the palette by a user when they contribute the beans
themselves in the project. We only have a way when a contributor
packages the whole shabang (palette, beans, beaninfo, any special ve
code they may want to use to extend the ve) into a plugin.

However, we don't have an up to date doc on this yet. The one we have is
for WSAD 5.1.2 (which is where the VE came from).

--
Thanks, Rich Kulp

Re: Adding 3rd party beans to VE [message #56297 is a reply to message #56244] Wed, 18 August 2004 09:31 Go to previous message
Eclipse UserFriend
Originally posted by: mendelgili.netscape.net

see org.eclipse.ve.jfc\palette\javavisualbeanscats.xmi which is the JFC
palette. XMI is a bit verbose ... but the net net is specifying the
class, icon, and a label. ... the only thing with it, is that the
syntax must be just right.

The JFC palette above is registered in the org.eclipse.ve.jfc plugin as
following, which mean that when the JRE container is on the build path,
he xmi above will be appended to the palette.

<extension
point="org.eclipse.ve.java.core.contributors">
<palette
container="org.eclipse.jdt.launching.JRE_CONTAINER"
categories="palette/javavisualbeanscats.xmi"
loc="last">
</palette>


Plugins can register palette entries.

Note that the .xmi is a text file and is a resource on the jfc plugin....;-)
Re: Adding 3rd party beans to VE [message #597337 is a reply to message #56095] Mon, 16 August 2004 11:16 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.NO.SPAM.us.ibm.com

The simplest way is to just add the jar to the build path of the
project. Then the choose bean will see it and you can select them. The
biggest problem is if there are BeanInfo classes. If there are and they
are in different jars or in different packages you need to tell the user
how to use the BeanInfo path in the project's properties how to find the
beaninfo jar and add the beaninfo classes to search path.


--
Thanks, Rich Kulp

Re: Adding 3rd party beans to VE [message #597354 is a reply to message #56149] Tue, 17 August 2004 09:19 Go to previous message
Eclipse UserFriend
Thanks. That works great. One other question: Is there any way of having
the these 3rd party beans appear in the bean palette?

jb

In article <cfqius$5jj$1@eclipse.org>, richkulp@NO.SPAM.us.ibm.com
says...
> The simplest way is to just add the jar to the build path of the
> project. Then the choose bean will see it and you can select them. The
> biggest problem is if there are BeanInfo classes. If there are and they
> are in different jars or in different packages you need to tell the user
> how to use the BeanInfo path in the project's properties how to find the
> beaninfo jar and add the beaninfo classes to search path.
>
>
>
Re: Adding 3rd party beans to VE [message #597364 is a reply to message #56227] Tue, 17 August 2004 12:12 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.NO.SPAM.us.ibm.com

Now you are getting into a difficult area. :-) We don't have a way yet
of customizing the palette by a user when they contribute the beans
themselves in the project. We only have a way when a contributor
packages the whole shabang (palette, beans, beaninfo, any special ve
code they may want to use to extend the ve) into a plugin.

However, we don't have an up to date doc on this yet. The one we have is
for WSAD 5.1.2 (which is where the VE came from).

--
Thanks, Rich Kulp

Re: Adding 3rd party beans to VE [message #597386 is a reply to message #56244] Wed, 18 August 2004 09:31 Go to previous message
Eclipse UserFriend
see org.eclipse.ve.jfc\palette\javavisualbeanscats.xmi which is the JFC
palette. XMI is a bit verbose ... but the net net is specifying the
class, icon, and a label. ... the only thing with it, is that the
syntax must be just right.

The JFC palette above is registered in the org.eclipse.ve.jfc plugin as
following, which mean that when the JRE container is on the build path,
he xmi above will be appended to the palette.

<extension
point="org.eclipse.ve.java.core.contributors">
<palette
container="org.eclipse.jdt.launching.JRE_CONTAINER"
categories="palette/javavisualbeanscats.xmi"
loc="last">
</palette>


Plugins can register palette entries.

Note that the .xmi is a text file and is a resource on the jfc plugin....;-)
Previous Topic:V E on Mac OS X
Next Topic:problem: JToolBar in JMenuBar
Goto Forum:
  


Current Time: Thu May 08 12:51:33 EDT 2025

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

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

Back to the top