September 30, 2014
The Eclipse Infocenter is the Eclipse help system launched as a web application. Three of five well-hidden features about the Infocenter have already been presented: Basic and Bot Mode, Deep Linking and Search Links. Here comes little known thing number four: Language Switching.
The Infocenter is multilingual. The Eclipse Babel project provides languages packs for the user interface. When the content is available in different languages it depends on your web browser settings which language will be chosen. The language setting of your web browser can be overruled by appending ?lang=… to the URL. Eclipse Luna Help is in English only, but for example the Infocenter for IBM Rational Team Concert for System z 2.0 is available in French (lang=fr), Spanish (lang=es), Japanese (lang=ja), Korean (lang=ko) and many other languages. It is also possible but rarely used to distinguish between American English (lang=en_US) and British English (lang=en_GB). In IBM’s Infocenter for Content Analytics Version 2.2 you can even switch the user interface language to Arabic (lang=ar) with right-to-left layout:
By the way, to confuse your colleagues you can switch the layout of their non-Arabic Eclipse IDE including help to right-to-left with the runtime option -dir rtl. ;-)
Sometimes it make sense to provide only parts of the help content in different languages. For instance, often the user manual is available in several languages, whereas the API documentation is available in English only. But also if the content is not multilingual the chosen (user interface) language affects searching. This is caused by the language-dependent stemming: searching in English for plan without quotes will find topics that contain planning or plans, the same query in Korean does not find these English topics. Infocenter administrators can limit the list of supported user interface languages via the runtime option -locales.
Stay tuned for the last little known thing about the Eclipse Infocenter on my list: Debugging Information!
Like in the past years, we continue in our tradition of hosting a “Christmas DemoCamp”. Please save the following date and mark your calendars on December 3rd 2014 for the next Eclipse DemoCamp in Munich!
We offer 80 seats, but we usually receive around 200 registrations. To give everybody the same chance, registration for the event will start exactly on October 13th 2pm. There you’ll also find detailed information on the location, time and more.
The agenda is not completely set, as soon as it is ready there will be another announcement. If you are interested in giving a talk, please contact me.
We are looking forward to your registration and seeing you in December!
Leave a Comment. Tagged with democamp, eclipse, democamp, eclipse
Inspired by My Top 10 Tups on how to be more productive with Eclipse IDE written by Jordi Böhme López of eclipsesource, i decided to blog about some of the interesting shortcuts that really increase your productivity.
Tip 1 : Copy Pasting of Path from Windows Explorer to Eclipse JDT Editor.
Typically Windows path would be "C:\Program Files\Java" but in Java \ is considered as escape character, so it has to be \\ or /. So to solve this problem, there is an option in windows/preferences.
1. Open Preferences Dialog and in the Filter Text, enter typing.
2. Select Typing under Java/Editor
3. On right hand side, you will find a group named In string literails, inside which you have 2 checkboxes. Enable "Escapt texts when pasting into a String literal"
4. Now copy the Path from Windows Explorer and paste within "" to see the magic.
5. All '\' should be converted to '\\' while pasting itself.
Tip 2 : Generating Getters and Setters in a bean class.
1. Highlight the class level variable for which you need Getters and Setters.
2. Press Ctrl + 1 [Shortcut for QuickFix] and select the option Create Getters and Setters for 'var'
1. Type instanceof and press Ctrl + Space
2. You will see a template being offered with a Yellow Sticky icon.
3. Select on that and the complete syntax of instanceof along with if condition, temporary variable etc would be provided.
This definitely increases your typing speed and not worrying about syntax errors or variable initialisation etc. List of templates supported can be found in windows/preferences. Go to windows/preferences and type templates in the filter box and you would see that every editor plugin will provide variety of templates that is offered on the editor via Content Assist.
Tip 4 : Filtering Imports package during Ctrl + O or Ctrl + Space.
When you type button and do Ctrl + Space, you will always find button from java.awt and org.eclipse.swt, but we are interested only in buttom from swt. So y show from java.awt. So you can define a filter over packages to show on Ctrl + O or Ctrl + Space.
Go to windows/preferences and type Type Filters in filter box. You will see a screen as shown below. add the packages that you want to filter from Ctrl + O or Ctrl + Space.
Jordi Böhme López of eclipsesource. Link provided above.
Tip 5 : Short Cut for Extracting as Local Variable [Alt + Shift + L]
Many a times we will use codes like PlatformUI.getWorkbench(); and then we will want to store that into a variable. We can select that line, right click > refactor > extract to local variable. But this also has a shortcut. Highlight the line and press Alt + Shift + L and this will create a local variable to store the method return value.
These are some of the tips that i really like and use to keep my programming productivity high.
September 29, 2014
This is just a heads up that with Luna SR1 the formerly called “Eclipse Standard” package is no longer available. It has been renamed to “Eclipse IDE for Committers“.
For details/background please have a look at bug 441957.
The main reason for this change is because the name “Eclipse Standard” meant very different things for people so we decided on a name which clearly identifies the target audience of that package. It contains tools for Java and OSGi/Plug-in development and the source code of Eclipse itself. The history of that package is the Eclipse SDK which IMO shouldn’t be a recommended standard download of Eclipse.
Bug what if I just want an unbranded bare minimum Eclipse?
Here are the steps I suggest in order to build your own Eclipse base:
- Download an Platform Runtime Binary archive from http://download.eclipse.org/eclipse/downloads/
- Unzip to your local disc and start Eclipse
- Install the Eclipse Marketplace Client
- Got to Help → Install New Software…
- Select Work with: Luna – http://download.eclipse.org/releases/luna
- Check General Purpose Tools → Marketplace Client
- Click Next
- Review the installation details and click Next
- Accept the license and click Finish
- Restart Eclipse
Now you have an absolute bare minimum, unbranded Eclipse package built by yourself. From here it’s easy to install additional plug-ins from the Eclipse Marketplace (got to Help → Eclipse Marketplace…).
I recommend at least the following plug-ins:
Today at JavaOne we announced the Open IoT Stack for Java, a set of open source technologies that will make it easier for Java developers to build IoT solutions. The focus of the technology is to enable developers to connect and manage the devices, sensors and actuators that are part of their IoT solution. VisionMobile estimates there will need to be 4.5 million IoT developers by 2020. The Open IoT Stack for Java is intended to help Java developers be some of those developers that are building IoT solutions.
To get started consider the following:
- Purchase some hardware, like the Raspberry Pi, and start experimenting.
- Check out the tutorial to build a smart greenhouse.
- Take the time to research and learn two new IoT standards, MQTT and CoAP. Eclipse Paho and Californium provide implementations of each.
- For the home automation DIY, learn about Eclipse SmartHome , a Java based framework for home automation.
- Discover the developer resources available at different sites, like iot.eclipse.org and java.net
If you are at JavaOne, please make sure you drop by our booth to see some very cool demos.
I’m happy to present the agenda of the selected talks:
Ecrit – Marco Descher
UML-RT in Papyrus – Charles Rivet
EMF Parsley N&N – Vincenzo Caselli
MPS-IncQuery – István Ráth
Interactively Developing Generators and Transformations – with Xtendency – Marco Eilers, Klaus Birken
The 13 Most Important Functions of CDO – Eike Stepper
In this year’s format each presenter will have 10 minutes. I’m looking forward to this event and interesting discussions afterwards. Hope to see you there!
Leave a Comment. Tagged with eclipse, eclipsecon, eclipse, eclipsecon
But GENERAL section in preferences was always an exception to this rule. It always appears 1st in Eclipse IDE. But if used in our own RCP, the alphabetic rule applies. That made it evident that somehow the 1st preference page could be changed.
Further investigation took me into understanding that this can be achieved only in the case of RCP when you can control ApplicationWorkbenchAdvisor. In ApplicationWorkbenchAdvisor you need to override getMainPreferencePageId() method and return the ID of the preferencePage that should appear 1st in your RCP similar to General in Eclipse.
Run your RCP to see your PreferencePage appear 1st.
September 26, 2014
Concurrently with the Handly releases announced today, we are also making available (under the Eclipse Public License v1.0) a step-by-step guide to getting started with Handly. It is hosted on GitHub. Despite being a work in progress, we do hope that even in its current form it will be useful for Handly adopters. Early feedback is welcome.
In celebration of Eclipse Luna SR1, I’m very pleased to announce the simultaneous availability of two Handly releases.
This is a major Handly release with the following themes:
Integration with Xtext 2.7.x — The most important goal of this release is to provide integration with Xtext 2.7.x. It will not support previous Xtext versions due to breaking changes introduced in Xtext 2.7 (see bug 442674 for a discussion).
Scalability — Handly 0.1 has been tried out on source files containing tens of thousands of lines of code. From those tests it seems that the JDT-inspired design would scale pretty well. Of course, there is always room for improvement, and this release is going to be even better in this regard.
API Quality — This release includes a number of API enhancements.
No major release can happen without some API breakage. Here is a summary of breaking changes in this release.
Concurrently with 0.2, we are also shipping 0.1.1 release to bring important bug fixes to those adopters who still rely on the 0.1.x line. Please note that this release (as well as the 0.1) will not work with Xtext 2.7 or greater due to breaking changes introduced in Xtext 2.7.
We are making available these two Handly releases simultaneously to minimize disruption for adopters who use Handly integration with Xtext. While Handly 0.1.1 remains compatible with Xtext 2.5, it will not work with Xtext 2.7 or greater; the 0.2 release is integrated with Xtext 2.7.x but doesn’t support previous Xtext versions.
Enjoy and don’t forget to leave your feedback on the adopter forum.
I'm not sure if having a way to change the globals will be added in the future -- mostly, I think that setting the globals is usually cumbersome, and if someone gets your project and it's not configured in itself, different users may have different results, which isn't really nice... on PyDev from the beginning things were only global, but as time passes by, I'm pretty sure that having the local from the start would be much better (which is something I plan to add in the future)!
September 25, 2014
Click on the Pics above to get more details on them. Thanks once again to the organiser for organising such a successful event and looking forward to meet the Indian Eclipse Group @ Demo Camp to be held towards the end of the year.
Getting in touch with the technology, the people behind it and its users.
I would argue that this is the main point of such a conference. Those 3 days are filled with presentations either from the project commiters giving a glimpse of what you could expect, or from users of the technology giving experience reports about how it helped them and what you might want to keep an eye on. Furthermore, presenters are sticking around during the conference and the friendly spirit makes it very easy to start a discussion and learn more.
This content is something you won't find anywhere else.
A lot of Modeling content
If you are into modeling or using it at work, going to this conference should be a no brainer. Xtext, Sirius, EMF Compare and many more technologies are represented during those days.
Speakers are good
In the last five years we have seen an impressive boost of quality regarding the talks and the way they were given. Most of the talks are kept in a 35 minutes slot and with the Program Commitee we worked hard to make sure the sessions will have good content but also good speakers.
3 hours sessions are planned so that you can get your hands dirty using some of the Eclipse Technologies. IoT,Cloud , Java, OSGi, EMF or Xtext are covered for the 2014 edition of the conference. Not only that but rooms are booked for the "Unconference" so that working groups can collaborate or projects can setup a "mini hackaton", that's a rare chance to gather people from different countries to work with.
The Circus, the concert, the receptions. Many occasions to enjoy yourself and to meet the Eclipse family.
If you haven't registered yet you might consider doing it now as the price will rise at the end of the month. I'm looking forward to meet you there !
September 24, 2014
September 23, 2014
The Eclipse Infocenter is the Eclipse help system launched as a web application. Two of five well-hidden features about the Infocenter have already been presented here. After Basic and Bot Mode and Deep Linking here comes little known thing number three: Search Links.
Search links are queries which can be used for sharing or creating a search input field in or outside the Infocenter. You can search all content, a single book or a single chapter. To search all content you have to append /index.jsp?tab=search&searchWord=… to the base Infocenter address like in this example of searching for eclipse runtime options within the Eclipse Luna online help. The following HTML snippet creates a search field for Luna help:
<form action="http://help.eclipse.org/luna/index.jsp" method="get" accept-charset="utf-8"> <input type="hidden" name="tab" value="search"> <input name="searchWord"> <input type="submit" value="Search"> </form>
In order to search within a book you have to use the toc parameter in addition to the tab and searchWord parameters as well as quickSearch=true and
quickSearchType=QuickSearchToc: /index.jsp?tab=search&quickSearch=true&quickSearchType=QuickSearchToc&toc=…&searchWord=… To get the value for the toc parameter, open /basic/searchView.jsp?searchWord=-&scopedSearch=true, select one book, click the Go button and get the value from the scope parameter of the new URL.
A chapter can be specified by the path parameter: /index.jsp?tab=search&quickSearch=true&quickSearchType=QuickSearchToc&toc=…&path=…&searchWord=… The value of tab is a tuple of subchapter indexes starting with 0 separated by underscores. For example path=0_2 refers to the third subchapter of the first top-level chapter of the book specified by the toc parameter.
In addition to the parameters described above you can use the optional parameters maxHits and showSearchCategories. The maxHits parameter specifies the maximal number of results to return and its value ranges between 1 and 500. The user settings Group by Categories can be overridden by showSearchCategories=true or by showSearchCategories=false.
If you do not pass the Turing Test because you are not human you may be interested in the more machine-readable search results in XML. The XML document is available at /search?phrase=… and includes also the scoring. The parameter phrase is equal to the searchWord parameter described above. The maximal number of results is limited to 1,000 (maxHits is not supported). The XML search results can be easily used in scripts. For example, this little Ant script finds common misspellings by querying for each item of Wikipedia’s list of common misspellings. It finds 131 typos in the current Luna help with only a very low false positive rate.
The next little known things about the Eclipse Infocenter on my list are Language Switching and Debugging Information. Stay tuned!