|Advice for Kepler based Product [message #1089431]
||Sun, 18 August 2013 14:42
| K Kumar
Registered: March 2011
We are planning to develop an eclipse desktop product. This product is more like a mini ide than a standalone RCP product. It would need the following features of Eclipse IDE.|
1. Common Navigator Framework (Project Explorer)
3. Text Editors (Xtext based framework)
4. Problem View/Errors View/Console View
5. Quick Access
6. Preferences Pages
Question is, to develop a mini-IDE type of tool (with above features) based on 4.x stream, what is the best approach that we can take?
Thank you for your response.
|Re: Advice for Kepler based Product [message #1089738 is a reply to message #1089673]
||Mon, 19 August 2013 02:56
| Jonas Helming
Registered: July 2009
as most of the stuff you want to re-use needs the compatibility layer
anyway, IMHO you do not have a real choice here. Therefore, I would use
the compatibility layer. However, you should develop everything you
create from scratch in e4 style, meaning all your handlers, views, etc.
should be POJOs. In 4.4 it will probably be possible to use e4 POJOs in
a compatibility mode application. In the meantime, you can also use this
Am 19.08.2013 06:29, schrieb K Kumar:
> Hi Wim,
> We are looking to develop a product to provide certain capabilities to
> users. Those capability structures would fit into existing Eclipse IDE
> features like I listed in first message.
> With Eclipse 4, there are two ways we can develop eclipse based product.
> 1. Pure Eclipse 4 way with DI and all but this option doesn't seems to
> have many capabilities of Eclipse IDE like Common Navigator (as those
> were designed with 3.x in mind so will not work in 4.x mode)
> 2. Compatibility mode, where we would develop our product in old style
> but run in 4.x platform.
> Question was around, is this my assumption is correct? If not, what
> other options do we have to develop the mini IDE for our needs?
Powered by FUDForum
. Page generated in 0.06852 seconds