| SWT availabe in Plugin Project - not Java Project? [message #77679] |
Tue, 18 January 2005 13:49  |
Eclipse User |
|
|
|
Originally posted by: carmen.blackdirt.com
If I create a Plugin Project in the work bench and then create a new Class
using the Visual Editor, SWT Widgets are available in the Palette. If I
create a Java Project and do the same thing, SWT Widgets are not
available. I added the SWT jar to the build. I also added other Jars to
make Java project resemble plugin.
Is there a way to make SWT Widgets available to VE in a Java Project?
Thanks,
Carmen
carmen@blackdirt.com
http://www.blackdirt.com
|
|
|
| Re: SWT availabe in Plugin Project - not Java Project? [message #77711 is a reply to message #77679] |
Tue, 18 January 2005 16:37  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
You don't add the jar to make it SWT. We've create a special container
that let's us know a project is SWT (that is because in addition to the
jar you also need some dll's, and there is no easy way to tell Eclipse
to include those. Our special code knows this for SWT and adds them in).
To make a project know about SWT, go to the project's properties, java
build tab, and go to the Libraries tab. Remove your swt jar, and do "Add
Library..." instead, and select the SWT library.
The reason it seems to work for plugins is because the default plugin
template from the wizard adds org.eclipse.ui as a required plugin, and
we check for this and if we see that this is a required plugin for the
project then we know SWT is available.
--
Thanks,
Rich Kulp
|
|
|
|
| Re: SWT availabe in Plugin Project - not Java Project? [message #79204 is a reply to message #77711] |
Mon, 07 February 2005 00:37 |
 scott
Messages: 21
Registered: July 2009 |
Junior Member |
|
|
Rich,
I've download RSSOwl from Sourceforge.net and created a project in Eclipse.
RSSOwl uses the SWT.
If I don't include the swt*.jar files and configure PATH within project
properties to point to the .dll's, I get an error message:
java.lang.UnsatisfiedLinkError: no swt-win32-3063 in java.library.path
The app works "off-the-shelf" and it works fine in Eclipse when I set those
configurations, but not when I just say "add the swt library"
Any ideas what I'm doing wrong?
"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> wrote in message
news:csjdvt$je5$1@www.eclipse.org...
> You don't add the jar to make it SWT. We've create a special container
> that let's us know a project is SWT (that is because in addition to the
> jar you also need some dll's, and there is no easy way to tell Eclipse
> to include those. Our special code knows this for SWT and adds them in).
>
> To make a project know about SWT, go to the project's properties, java
> build tab, and go to the Libraries tab. Remove your swt jar, and do "Add
> Library..." instead, and select the SWT library.
>
> The reason it seems to work for plugins is because the default plugin
> template from the wizard adds org.eclipse.ui as a required plugin, and
> we check for this and if we see that this is a required plugin for the
> project then we know SWT is available.
> --
> Thanks,
> Rich Kulp
|
|
|
| Re: SWT availabe in Plugin Project - not Java Project? [message #79345 is a reply to message #79204] |
Mon, 07 February 2005 19:00 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
You added the SWT library container we provide and it doesn't work when
started from Eclipse? Is that what you said? What fails, the VE or
launching an app? If it is launching an app that fails, use the Java
Bean Launcher instead of the Java Application Launcher. The standard
Java Application Launcher knows nothing about SWT so it won't add the
libraries for you. The Java Bean Launcher is supplied by the VE and it
knows about the SWT container and will add the libraries on launching.
--
Thanks,
Rich Kulp
|
|
|
| Re: SWT availabe in Plugin Project - not Java Project? [message #604715 is a reply to message #77679] |
Tue, 18 January 2005 16:37 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
You don't add the jar to make it SWT. We've create a special container
that let's us know a project is SWT (that is because in addition to the
jar you also need some dll's, and there is no easy way to tell Eclipse
to include those. Our special code knows this for SWT and adds them in).
To make a project know about SWT, go to the project's properties, java
build tab, and go to the Libraries tab. Remove your swt jar, and do "Add
Library..." instead, and select the SWT library.
The reason it seems to work for plugins is because the default plugin
template from the wizard adds org.eclipse.ui as a required plugin, and
we check for this and if we see that this is a required plugin for the
project then we know SWT is available.
--
Thanks,
Rich Kulp
|
|
|
|
| Re: SWT availabe in Plugin Project - not Java Project? [message #605012 is a reply to message #77711] |
Mon, 07 February 2005 00:37 |
scott
Messages: 21
Registered: July 2009 |
Junior Member |
|
|
Rich,
I've download RSSOwl from Sourceforge.net and created a project in Eclipse.
RSSOwl uses the SWT.
If I don't include the swt*.jar files and configure PATH within project
properties to point to the .dll's, I get an error message:
java.lang.UnsatisfiedLinkError: no swt-win32-3063 in java.library.path
The app works "off-the-shelf" and it works fine in Eclipse when I set those
configurations, but not when I just say "add the swt library"
Any ideas what I'm doing wrong?
"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> wrote in message
news:csjdvt$je5$1@www.eclipse.org...
> You don't add the jar to make it SWT. We've create a special container
> that let's us know a project is SWT (that is because in addition to the
> jar you also need some dll's, and there is no easy way to tell Eclipse
> to include those. Our special code knows this for SWT and adds them in).
>
> To make a project know about SWT, go to the project's properties, java
> build tab, and go to the Libraries tab. Remove your swt jar, and do "Add
> Library..." instead, and select the SWT library.
>
> The reason it seems to work for plugins is because the default plugin
> template from the wizard adds org.eclipse.ui as a required plugin, and
> we check for this and if we see that this is a required plugin for the
> project then we know SWT is available.
> --
> Thanks,
> Rich Kulp
|
|
|
| Re: SWT availabe in Plugin Project - not Java Project? [message #605046 is a reply to message #79204] |
Mon, 07 February 2005 19:00 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
You added the SWT library container we provide and it doesn't work when
started from Eclipse? Is that what you said? What fails, the VE or
launching an app? If it is launching an app that fails, use the Java
Bean Launcher instead of the Java Application Launcher. The standard
Java Application Launcher knows nothing about SWT so it won't add the
libraries for you. The Java Bean Launcher is supplied by the VE and it
knows about the SWT container and will add the libraries on launching.
--
Thanks,
Rich Kulp
|
|
|
Powered by
FUDForum. Page generated in 0.01913 seconds
] 
Search
Help
Register
Login
Home
