| test swt/jface dialog without rcp runtime? [message #334583] |
Wed, 18 February 2009 22:21  |
Eclipse User |
|
|
|
Originally posted by: nospam.somewhere.org
I am developing an swt/jface dialog in a rcp plugin. For
developing/testing my need is to start this dialog without the need to
start the whole eclipse application. I simply added a pubic static void
main() to the dialog, but got eclipse runtime problem when starting this
dialog out of the eclipse.
The dialog references classes from another rcp plugin. This plugin
internally uses eclipse/java preferences and throws an exception when
instantiating the preference classes.
Main problem i think is the main method, which doesn't initialize
eclipse runtime. I also reference another plugin (eclipse project), the
classpath is okay, but not the runtime environment.
Question: is there a simple way to initialize eclipse runtime and to
avoid the described problem. My need is a development testing iteration.
The solution should simply work and needs not to be a clean way.
The only alternative i currently see, is to create a new product
configuration. Thats too much effort for simple testing, isn't it?
Any ideas?
|
|
|
|
| Re: test swt/jface dialog without rcp runtime? [message #334605 is a reply to message #334583] |
Thu, 19 February 2009 23:18  |
| Eclipse User |
|
|
|
Ceeper wrote:
> I am developing an swt/jface dialog in a rcp plugin. For
> developing/testing my need is to start this dialog without the need to
> start the whole eclipse application. I simply added a pubic static void
> main() to the dialog, but got eclipse runtime problem when starting this
> dialog out of the eclipse.
> The dialog references classes from another rcp plugin. This plugin
> internally uses eclipse/java preferences and throws an exception when
> instantiating the preference classes.
>
> Main problem i think is the main method, which doesn't initialize
> eclipse runtime. I also reference another plugin (eclipse project), the
> classpath is okay, but not the runtime environment.
>
> Question: is there a simple way to initialize eclipse runtime and to
> avoid the described problem. My need is a development testing iteration.
> The solution should simply work and needs not to be a clean way.
>
> The only alternative i currently see, is to create a new product
> configuration. Thats too much effort for simple testing, isn't it?
>
> Any ideas?
Does SWTBot help you at all?
http://www.eclipse.org/swtbot/
Cheers,
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/caniszczyk | http://twitter.com/eclipsesource
|
|
|
Powered by
FUDForum. Page generated in 0.06626 seconds
Home