I have only a basic understanding of Eclipse RCP. I am about to start an in-house application for our technical support team, that will likely grow over time. The team is distributed across continents so I would like to be able to auto-update the application when new versions are made available. The application aims to capture knowledge from technical support incidents while making it easy to replay data fixes across clients. The things that make eclipse RCP look interesting are Eclipse Communication Framework (ECF) and Data Tools Platform (DTP). My constraints are:
我对Eclipse RCP只有基本的了解。我即将为我们的技术支持团队启动内部应用程序,这可能会随着时间的推移而增长。该团队分布在各大洲,因此我希望能够在新版本可用时自动更新应用程序。该应用程序旨在从技术支持事件中获取知识,同时可以轻松地跨客户端重放数据修复程序。使Eclipse RCP看起来很有趣的东西是Eclipse Communication Framework(ECF)和Data Tools Platform(DTP)。我的约束是:
- Small Team (basically just me for now :)
- Have to manage it as a side project until its usefulness is proven
小团队(现在基本上只是我:)
必须将其作为一个辅助项目进行管理,直到其有用性得到证实
I am basically looking for insights from other developers who have worked with Eclipse RCP or who know a better alternative.
我基本上是在寻找其他使用Eclipse RCP或知道更好替代方案的开发人员的见解。
1 个解决方案
#1
1
The best way to evaluate RCP is to create a small project ... I started with the tutorial here: http://www.ibm.com/developerworks/edu/os-dw-os-ecl-rcpapp.html and gradually created a less trivial application.
评估RCP的最好方法是创建一个小项目......我从这里的教程开始:http://www.ibm.com/developerworks/edu/os-dw-os-ecl-rcpapp.html并逐步创建一个不那么简单的应用程序。
Probably the best single resource I've found is the "Eclipse Rich Client Platform" book (which I initially borrowed from the local university library. The book's web site is here: http://eclipsercp.org/book/.
可能我发现的最好的单一资源是“Eclipse Rich Client Platform”一书(我最初是从当地的大学图书馆借来的。本书的网站在这里:http://eclipsercp.org/book/。
The only downside to RCP is the size of the distributed program, but the automatic software update feature makes this much less painful and, if you modularize the application using plugins, the user doesn't have to download the entire application to receive updates to one plugin.
RCP的唯一缺点是分布式程序的大小,但自动软件更新功能使这一点变得更加痛苦,如果您使用插件模块化应用程序,用户不必下载整个应用程序来接收更新插入。
#1
1
The best way to evaluate RCP is to create a small project ... I started with the tutorial here: http://www.ibm.com/developerworks/edu/os-dw-os-ecl-rcpapp.html and gradually created a less trivial application.
评估RCP的最好方法是创建一个小项目......我从这里的教程开始:http://www.ibm.com/developerworks/edu/os-dw-os-ecl-rcpapp.html并逐步创建一个不那么简单的应用程序。
Probably the best single resource I've found is the "Eclipse Rich Client Platform" book (which I initially borrowed from the local university library. The book's web site is here: http://eclipsercp.org/book/.
可能我发现的最好的单一资源是“Eclipse Rich Client Platform”一书(我最初是从当地的大学图书馆借来的。本书的网站在这里:http://eclipsercp.org/book/。
The only downside to RCP is the size of the distributed program, but the automatic software update feature makes this much less painful and, if you modularize the application using plugins, the user doesn't have to download the entire application to receive updates to one plugin.
RCP的唯一缺点是分布式程序的大小,但自动软件更新功能使这一点变得更加痛苦,如果您使用插件模块化应用程序,用户不必下载整个应用程序来接收更新插入。