Obviously the best thing about this approach is that there is no native code to
worry about!
Having the 2nd/3rd/Nth instances register with the first via the standard port is a great idea. If
the first instance shuts down gracefully, it could actually poke one of the registered instances to
While I completely agree that we need some easy method of installing and
that it would be ideal to do so from a web browser, wouldn't this
solution require one to basically do all of their browsing from within
Eclipse?
For Summer of Code this year I worked on a project [1] that would
allow
Subject:Re: [equinox-dev] [prov] p2 / browser integration
mailing list equinox-dev@eclipse.org
cc
Subject
Re: [equinox-dev] [prov] p2 / browser integration
Forgot to mention some simple approaches we could also consider for the
UpdateManager:
1. The UI could detect a standard http:// site or feature URL on the
clipboard, or allow the user
Could you guys check out what done of our student did this summer to address
that very issue? http://wiki.eclipse.org/Google_Summer_of_Code_2007
http://wiki.eclipse.org/Eclipse_Web_Interface
--
Cheers
Philippe
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
