When I am developing an Eclipse RCP application, what is the easiest way to translate those strings in the plugins required by my application into Chinese? As I know, these plugins already have a Chinese version at Babel project. How can I use the existing Babel translations?
Install Babel from its update site. Then restart eclipse, it will use the language corresponding to your system locale, or launch eclipse with -nl <locale> option
Related
I have my own Eclipse platform build by using Tycho.
And i want to include some plugins automatically in it.
So that i can use e.g subclipse without installing it manually.
Whats the possibilities to do this?
You need to add the needed plugins / features to your target platform. Then you can define your packaging to include them by default.
I am using Eclipse Java EE with Vrapper for working on a Java/Scala project. Is it possible to get both syntax highlighting and vrapper (or any kind of vim editing) in regular eclipse?
You can install any plugin on any Eclipse version you want - the only requirement is that the requirement information a plugin holds are true. Each Eclipse version is just a set of plugins bundled together.
In your case, just download one of the prepackaged Eclipse versions, then install the Scala IDE (note, that at the moment only M3 works on Luna) and finally install Vrapper.
There is also eclim (http://eclim.org), a Vim/Eclipse plugin that lets you run Vim inside or alongside Eclipse and access some of the Eclipse features. But not all the Eclipse features are available from Vim, notably the debugger integration.
I am developing an Eclipse RCP product in Eclipse e4 environment using Kepler for RCP developers on 64-bit Linux and Java 7.
I'd like to use Eclipse Babel language packages within my Eclipse product. Copying features and plugins directory into Eclipse IDE directory works without a problem. I can run my Eclipse environment in the language I want by passing -nl argument.
I used PDE to produce a product and applied the same step by simply copying the language package into the product's features and plugins directory. However, it did not work as I see OK and Cancel button labels still in English.
Is it correct to simply copy the files or do I have to add an extra dependency?
Thanks.
We are writing an Eclipse plugin that will work in a ClearCase environment i.e., our plugin will work along with the ClearCase SCM plugin for eclipse(available from IBM).
When developing the plugin, our eclipse(RCP & RAP) don't need ClearCase plugin. However, when we launch the plugin thru "Eclipse Application Launcher", the new eclipse does need the ClearCase plugin.
Is it possible to configure the "Eclipse Application Launcher" to include ClearCase plugin(or any different plugin that's not in the base eclipse) when it fires up another eclipse instance?
I could not find a way to do this from the documentation.
I think Target platform is what you are looking for.
You can use a pure Eclipse release(such as Juno) as development tool, then use another collection of compile and runtime plug-ins via specifying a target platform.
I've created my DSL language and code generator using Xtext nad Xtend. But when I want to use it, I need to open my Xtext project and click "Run as-> Launch Runtime Eclipse". Is it possible to have my editor/generator in the normal eclipse run? In other words, I want to download plain eclipse installation,than install some plugin or somehow configure my eclipse, and than create files of my language, have syntax coloring and all editor features, code generation etc.
You have to export your plugins and install them into eclipse.
option 1: use File>Export...>Deployable plugins and fragments to export your plugins, then install them into an eclipse. That wizard has an option to deploy them directly into your running eclipse.
option 2: build your plugins using PDE build or maven/tycho and create a p2 update site. Then you can install them into any eclipse you have.
Both options are easier to manage if you create a feature that contains your plugins. It's easier to export, and easier to install the feature.