rcp

快速掌握 Eclipse Plugin / RCP 开发思想 李晓明 (lxm@lxm.name) 引言 本文不是快速入门的文章，只面向有一定基础的开发人员，至少看这篇文章之前你应该了解什么是 Eclipse ，什么是 RCP ，什么是 Plugin ，什么是架构，什么是软件框架等等概念。否则的话这篇文章也帮不了你什么。另外，本人对 RCP 的理解也是处于一知半解的程度，如有错误还请指出。 Eclipse 是一种面向开发人员的编程环境（ IDE ），同时它也是一个很好的平台，它提供了一种架构，或者说一种软件框架，可以让开发人员相对比较容易的开发出功能比较强大的，带有人机交互功能的应用程序。 Eclipse 这种强大的功能是通过其插件（ Plugin ）来实现的， RCP 也是如此。 RCP 的全称是 Rich Client Platform ，其根本就是把 Eclipse 的应用平台剥离了其他的插件之后剩下的东西，自然其架构和原理与 eclipse 本身是一样的。 RCP 也可以通过插件来进行扩展，但 RCP 往往是用来开发一些像 Eclipse 一样独立的应用程序。 本文帮助对 RCP 不是很清楚的人快速的理解 Eclipse RCP 和 Plugin 的工作原理与开发方法。 基本知识 让我们闭上眼睛静下心来冥想一下，我们可以想象，如果要开发一个带有人机交互的应用程序

Question about Eclipse RCP and whole perspective/view/editor design - what is the best way to create application which will display multiple windows on multiple monitors? Tutorials and book I've seen always pack RCP/SWT design into views inside perspective within single application window. Should one window rule all others or they all should be equal (closing last one exits application)? How deal with the perspectives and views? Are there any other things we should know? Environment: Eclipse Ganymede, Windows XP. A single Eclipse workbench can create multiple windows. Each window is laid out

I'm using Eclipse HELIOS to code a Rich Client app. The following entries are added automatically to my APP "PERSPECTIVES MENU": "Java, Java Browsing, Java Type Hierarchy, Team Synchronizing". I need to get rid of them. i'm using the extension point="org.eclipse.ui.activities" to disable unwanted extensions (like the editor and search options that appear on the coolbar) I managed to get rid of "Debug" by adding "org.eclipse.debug.ui.*" This is my actual config: <extension point="org.eclipse.ui.activities"> <activity id="rcpcolibri.disablextensions" name="Hidden activities"/>

I was working on Eclipse RCP and I got this error A fatal error has been detected by the Java Runtime Environment: EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007fef54b88ee, pid=3192, tid=5324 JRE version: 7.0_02-b13 Java VM: Java HotSpot(TM) 64-Bit Server VM (22.0-b10 mixed mode windows-amd64 compressed oops) Problematic frame: C [jscript9.dll+0x888ee] Failed to write core dump. Minidumps are not enabled by default on client versions of Windows An error report file with more information is saved as: F:\Eclipse RCP\hs_err_pid3192.log If you would like to submit a bug report, please

总结说明： 1.必须搞明白modules和artifacts是什么东西。 2.modules如果是webApp的话，那么在new modules的时候注意得选择webmodules。如果是从别的地方copy过来的项目，那么可以自己新建一个web.xml或者new之后选择之前项目的web.xml 3.artifacts新建的时候特别注意层次！如果是自己新建立的一个out目录，那么得把jsp的document导入。​ ​ 概述：由于IntelliJ IDEA 和Eclipse都是正对Java开发语言的IDE，所以将Java程序从Eclipse迁移到IntelliJ IDEA并不难，但是，两者在部分名词上存在不同的定义。例如，Eclipse中的“project”(项目)对应 IntelliJ IDEA中的“module”(模块).而IntelliJ IDEA中的“project”,某种程度上，类似Eclipse中的“workfspace”(工作区)。事实上，要迁移不带Eclipse插件的简单 Java应用，你需要在IntelliJ中创建和Eclipse中类似的项目结构。如果你要迁移的是Eclipse 富客户端(RCP)应用，请参阅 使用IntelliJ IDEA 做Eclipse RCP开发。 由于IntelliJ IDEA 和Eclipse都是正对Java开发语言的IDE

Pretty soon now, we're gonna need to develop a GUI for creating configurations (more like scripts, to be honest) for our EAI solution at work. Think of a typical workflow editor. The visualization of the actual flows will most likely be a completely custom job, either in Swing, SWT or JavaFX 2. What I have trouble with choosing is whether to do everything else by ourselves or using a rich client platform. In particular, I've noticed that JavaFX 2 is getting a lot of attention and seems to be really pushed by Oracle as the next big thing in the Java GUI landscape. The demonstrations look

Because my RCP eclipse application fails when run outside of eclipse, but works correctly when running inside of eclipse, I am attempting to use eclipse to remotely debug my application as it's running outside of the eclipse environment. I am using 32 bit Eclipse 3.6.1 on a 64 bit Windows 7 machine. I am using 32 bit Java 1.6 update 37. I use the Eclipse Product export wizard to package the app, and I end up with an eclipse.exe. I have created a Remote Debug Configuration and set it to use port 8765 (random number). For debugging purposes, I start the app from the command line using this line: