Community
Participate
Working Groups
E4 addresses two long-standing complaints by RCP developers: 1) That RCP is too hard to understand and has too many APIs. One subpart of this concern is that RCP does not come with "batteries included" for creating enterprise RCP applications. 2) That in a world of desktop/cloud mashups, RCP remains purely a desktop-centric framework. This contribution seeks to further these two concerns using two libraries that are built on top of existing Eclipse APIs: 1) The Enterprise Installer: Enterprise network-centric applications normally install as a small kernel, and then add features and/or update themselves automatically over the wire. While Eclipse's update manager and P2 APIs can be made to support these use-cases, additional work is required by the developer. The out-of-box experience is anything but "batteries included". The Enterprise Installer supplies simple APIs and examples, making it a snap to create this kind of self-updated application. 2) The essence of the World Wide Web is the hyperlink. Hyperlinks let us share Google search results, our personal page on Facebook, or invoke a bit of functionality in Twitter's REST API. Deep Linking is (a) a small DSL built on top of HTTP hyperlinks, enabling literally any part of an RCP application to become URL-addressable, and (b) a set of OSGI bundles (i) exposing all Eclipse perspectives as URLs, and (ii) adding an extension point that can be used to write an arbitrary callback that is URL-addressable. In addition, we supply a small OSGI application that (a) can be registered on the native platform as a URL protocol handler, and (b) proxies requests made to this native deeplink protocol through to the actual HTTP server that will handle the request. This proxy also makes sure that the actual client application that can handle a particular deep link request is running and will automatically start it if it is not. This bug report serves to track discussion about this code contribution and as the link to the IPZilla request.
Source code for this contribution has been uploaded to the IPZilla ticket# 4081: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4081
Dave, it seems from https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4081#c26 and c27 that if we can change the feature copyright notice, we can check it into CVS and continue working with it from there. PW
(In reply to comment #2) > Dave, it seems from https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4081#c26 > and c27 that if we can change the feature copyright notice, we can check it > into CVS and continue working with it from there. > > PW Thanks Paul; good to see you're on top of this too. I'm right now in the middle of fixing those copyright notices. :) Re: Checkin: Do you want to check it out of the CQ and import it into CVS, or would you prefer that I do it under your supervision?
I've created places for your projects to go: /cvsroot/eclipse e4/<area> and I left area as you broke it out: org.eclipse.e4.enterprise.deeplink: bundles doc examples features tests org.eclipse.e4.enterprise.installer: bundles doc examples features fixtures tests org.eclipse.e4.enterprise.utils: bundles doc examples features tests You can check in all of your projects in the appropriate places once you've updated the feature headers mentioned in the CQ. If you have any more questions, just comment on the bug or ping me on IRC: irc://freenode.net/#eclipse-e4 PW
