Comments for Common Navigator and Other Things http://dev.eclipse.org/blogs/francis Francis Upton's Eclipse Blog Thu, 05 Nov 2009 03:06:07 +0000 http://wordpress.org/?v=2.6.5 Comment on Magic Required to use the Common Navigator in an RCP Application that uses Resources by Francis Upton http://dev.eclipse.org/blogs/francis/2008/05/27/magic-required-to-use-the-common-navigator-in-an-rcp-application/#comment-113 Francis Upton Tue, 30 Jun 2009 19:15:42 +0000 http://dev.eclipse.org/blogs/francis/2008/05/27/magic-required-to-use-the-common-navigator-in-an-rcp-application/#comment-113 @Will, yes this has changed in 3.5 and the instructions were revised in 3.5 to reflect this. The new instructions refer to the new API. See this page: http://help.eclipse.org/galileo/topic/org.eclipse.platform.doc.isv/guide/cnf_steps_content.htm. @Will, yes this has changed in 3.5 and the instructions were revised in 3.5 to reflect this. The new instructions refer to the new API. See this page: http://help.eclipse.org/galileo/topic/org.eclipse.platform.doc.isv/guide/cnf_steps_content.htm.

]]> Comment on Magic Required to use the Common Navigator in an RCP Application that uses Resources by Will http://dev.eclipse.org/blogs/francis/2008/05/27/magic-required-to-use-the-common-navigator-in-an-rcp-application/#comment-112 Will Tue, 30 Jun 2009 18:25:59 +0000 http://dev.eclipse.org/blogs/francis/2008/05/27/magic-required-to-use-the-common-navigator-in-an-rcp-application/#comment-112 Has this changed with Eclipse 3.5? For one, you can call org.eclipse.ui.ide.IDE.registerAdapters() instead of org.eclipse.ui.internal.ide.model.WorkbenchAdapterBuilder.registerAdapters() to avoid using the internal (and now deprecated) class. At least in Ganymede help there was a section about RCP with essentially these instructions: http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/cnf_rcp.htm I don't see similar instructions in the Galileo help. Has this changed with Eclipse 3.5?

For one, you can call org.eclipse.ui.ide.IDE.registerAdapters() instead of org.eclipse.ui.internal.ide.model.WorkbenchAdapterBuilder.registerAdapters() to avoid using the internal (and now deprecated) class.

At least in Ganymede help there was a section about RCP with essentially these instructions: http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/cnf_rcp.htm

I don’t see similar instructions in the Galileo help.

]]> Comment on Application “…” could not be found in the registry. by Kurt http://dev.eclipse.org/blogs/francis/2009/05/19/application-could-not-be-found-in-the-registry/#comment-94 Kurt Wed, 17 Jun 2009 16:06:28 +0000 http://dev.eclipse.org/blogs/francis/?p=45#comment-94 I believe that I have found the problem; the missing bundle (plugin) needed to be selected in the Launch Configuration... select project, right-click, , select Plug-ins tab, check the missing plugin. Kurt I believe that I have found the problem; the missing bundle (plugin) needed to be selected in the Launch Configuration… select project, right-click, , select Plug-ins tab, check the missing plugin.

Kurt

]]> Comment on Application “…” could not be found in the registry. by Kurt http://dev.eclipse.org/blogs/francis/2009/05/19/application-could-not-be-found-in-the-registry/#comment-93 Kurt Wed, 17 Jun 2009 15:37:39 +0000 http://dev.eclipse.org/blogs/francis/?p=45#comment-93 I'm encountering the same problem while attempting to use JFreeChart in a simple RCP (Eclipse 3.3.0). The RCP is the simple "RCP application with a view" template found in Eclipse. The JFreeChart jars are bundled into a seperate plugin per the example at http://www.vogella.de/articles/EclipseJFreeChart/article.html. I've found the simply adding the JFreeChart project as a dependency will cause the problem (Application not found in the registry). The log indicates that the JFreeChart bundle is missing... and I'm not sure what to do to get the app to find it (I'm new to RCP). Finally, I've found that I can avoid the problem and get the app to run with the JFreeChart example code simply by changing the ID of my RCP application. Does anyone know why this would seem to solve the problem? Thanks I’m encountering the same problem while attempting to use JFreeChart in a simple RCP (Eclipse 3.3.0). The RCP is the simple “RCP application with a view” template found in Eclipse. The JFreeChart jars are bundled into a seperate plugin per the example at http://www.vogella.de/articles/EclipseJFreeChart/article.html.

I’ve found the simply adding the JFreeChart project as a dependency will cause the problem (Application not found in the registry). The log indicates that the JFreeChart bundle is missing… and I’m not sure what to do to get the app to find it (I’m new to RCP).

Finally, I’ve found that I can avoid the problem and get the app to run with the JFreeChart example code simply by changing the ID of my RCP application. Does anyone know why this would seem to solve the problem?

Thanks

]]> Comment on RCP, p2, Vista and VirtualStore by Francis Upton http://dev.eclipse.org/blogs/francis/2009/05/24/rcp-p2-vista-and-virtualstore/#comment-89 Francis Upton Mon, 25 May 2009 17:54:22 +0000 http://dev.eclipse.org/blogs/francis/?p=48#comment-89 @john I think the issue is that I provided a configuration folder when I installed in the Program Files directory, so part of this checking must assume that if there is already a configuration folder in the Program Files directory then it should just use that. Of course that was my mistake, I should not have provided it there since it was not writable. @john I think the issue is that I provided a configuration folder when I installed in the Program Files directory, so part of this checking must assume that if there is already a configuration folder in the Program Files directory then it should just use that. Of course that was my mistake, I should not have provided it there since it was not writable.

]]> Comment on RCP, p2, Vista and VirtualStore by John Arthorne http://dev.eclipse.org/blogs/francis/2009/05/24/rcp-p2-vista-and-virtualstore/#comment-88 John Arthorne Mon, 25 May 2009 16:09:44 +0000 http://dev.eclipse.org/blogs/francis/?p=48#comment-88 Yes, this has been true since 3.2.2: https://bugs.eclipse.org/bugs/show_bug.cgi?id=209192 Yes, this has been true since 3.2.2:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=209192

]]> Comment on RCP, p2, Vista and VirtualStore by Francis Upton http://dev.eclipse.org/blogs/francis/2009/05/24/rcp-p2-vista-and-virtualstore/#comment-87 Francis Upton Mon, 25 May 2009 15:22:32 +0000 http://dev.eclipse.org/blogs/francis/?p=48#comment-87 @John, is this true for 3.4.2 as well? I'm pretty sure I did not specify the osgi.configuration.area property anywhere, nor did I pass the corresponding flag to the launcher? I do need to know ahead of time where it's going to go, as I have stuff in the config.ini (and stuff for p2 due to the pre-installation that's done when building the kit) that needs to go in the configuration folder. @John, is this true for 3.4.2 as well? I’m pretty sure I did not specify the osgi.configuration.area property anywhere, nor did I pass the corresponding flag to the launcher? I do need to know ahead of time where it’s going to go, as I have stuff in the config.ini (and stuff for p2 due to the pre-installation that’s done when building the kit) that needs to go in the configuration folder.

]]> Comment on RCP, p2, Vista and VirtualStore by John Arthorne http://dev.eclipse.org/blogs/francis/2009/05/24/rcp-p2-vista-and-virtualstore/#comment-86 John Arthorne Mon, 25 May 2009 14:28:08 +0000 http://dev.eclipse.org/blogs/francis/?p=48#comment-86 When the framework starts, it tries to find an appropriate writeable location for the configuration folder. When the install directory is not writeable, or when running on Vista and the install directory is under "Program Files", the framework will default to putting the configuration folder under user-home. This works perfectly in the Eclipse platform and Eclipse SDK itself. I suspect you had somewhere explicitly set the configuration directory to be under the install directory to encounter this problem. When the framework starts, it tries to find an appropriate writeable location for the configuration folder. When the install directory is not writeable, or when running on Vista and the install directory is under “Program Files”, the framework will default to putting the configuration folder under user-home. This works perfectly in the Eclipse platform and Eclipse SDK itself. I suspect you had somewhere explicitly set the configuration directory to be under the install directory to encounter this problem.

]]> Comment on RCP, p2, Vista and VirtualStore by Francis Upton http://dev.eclipse.org/blogs/francis/2009/05/24/rcp-p2-vista-and-virtualstore/#comment-85 Francis Upton Sun, 24 May 2009 22:09:23 +0000 http://dev.eclipse.org/blogs/francis/?p=48#comment-85 @alex I agree, however it's actually completely modular in how you can decompose the osgi stuff (and p2) into different places. The problem is that it's not a habit to set it up correctly. It's really just a matter of configuration and documentation. And well learning the hard way. @alex I agree, however it’s actually completely modular in how you can decompose the osgi stuff (and p2) into different places. The problem is that it’s not a habit to set it up correctly. It’s really just a matter of configuration and documentation. And well learning the hard way.

]]> Comment on RCP, p2, Vista and VirtualStore by Alex Blewitt http://dev.eclipse.org/blogs/francis/2009/05/24/rcp-p2-vista-and-virtualstore/#comment-84 Alex Blewitt Sun, 24 May 2009 21:58:49 +0000 http://dev.eclipse.org/blogs/francis/?p=48#comment-84 It's always been crap that Eclipse writes to the program install area. It's a problem with the Mac installs too. It really should be absolutely unnecessary to write there but sadly Eclipse is designed with poor Windows standards as it's main focus and pays lip service to standard Unix or Mac standards. It’s always been crap that Eclipse writes to the program install area. It’s a problem with the Mac installs too. It really should be absolutely unnecessary to write there but sadly Eclipse is designed with poor Windows standards as it’s main focus and pays lip service to standard Unix or Mac standards.

]]>