Re: [ve-dev] Launch Configurations for Proxy remote VM's.

[Phil Muldoon <pmuldoon@xxxxxxxxxx>]

On Wed, 2004-02-18 at 15:42, Rich Kulp wrote:
> Currently when we launch the remote vm that we use for BeanInfo
> introspection and for hosting the live objects from an editor we have
> a hard-coded configuration. We want to change this so that the
> configuration can be modified by users. This is sometimes necessary
> because the standard configuration is not sufficient. One hope is that
> in the future, maybe we can launch the simulator for a PDA or
> something, and those probably won't launch as a standard vm.

I was pondering something along these lines awhile back, when I was
thinking along the lines of compiling the Visual Editor with gcj to .so
(as we do with out own plugins (rpm, changelog, etc), the eclipse driver
and the CDT). It was an academic exercise then, but one of the problems
was in launching the bean (Well that and debugging and no swing support
in gcj). I'm glad to see you pursuing the launch configuration as it
allows - in your example above - the extension of non standard launch
configurations.

> The actual content of this configuration will be dictated by the needs
> of the proxy plugin. So my basic questions for the group are:

I'd almost always go with the context menu. The problem with toolbars
you highlight in your extension explanation to point one.

>         The advantage of the toolbar is that it is a familiar
>         paradigm.

Well you lose that, but in your ant example I almost always use the
context menu. It's just easy for me to keep track of what is going on
when I have multiple projects in the workspace. Could we have both?


regards

phil