[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [ve-dev] Re: Future of VE
|
Hi Philippe,
>I am sure there have been excellent historical
reasons, but in practice
>it makes VE really resource hungry and very hard to use. Revisiting
that
>with a new eye, with the newer and stabler VM is worth it.
The implementation of the target VM
code is such that it is possible to have VE talk to JavaBeans that are
instantiated inside the Eclipse VM, rather than having to use a separate
VM. This isn't used by the Swing/SWT VE implementation, however it
is used by some guys who did a bunch of work with having the VE working
with mobile MIDP stuff where they had the beans inside Eclipse itself.
One idea we kicked around for ages but
never finished off, was that the VE would allow the option to run directly
against the IDE's VM, perhaps via a preference where if the Java project's
classpath matched that of the IDE itself then this was the default option.
Once we get a 3.3 codebase working maybe we should revisit this as
an option - if nothing else it means that user's first impression of VE
will be faster, and then as that user becomes more complex in terms of
having separate targets and IDEs, they have the option of breaking the
two apart but understand the implications.
Best regards,
Joe
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
