August 30, 2014
Apart from help.eclipse.org for Luna and previous simultaneous releases Eclipse offers its Infocenter for Orion:
In the wild the Infocenter is used for instance by Tasktop without modification except an additional header…
… or by bada Developers:
I like the red style of Wolfram. Even the icons have been adapted:
ARM has made functional changes to the Infocenter. With the menu to the left of the search box you can select where to search, e. g. within the title only or in the whole document. Interestingly, some icons have been removed: there is no Print/Search Topic (and its Subtopics) icon and no Link with Contents icon in the Contents toolbar; no Group by Categories and no number of matches in Search Results.
Sybase also made some search modifications. The drop-down menu right of the search field makes it easier to switch between search scopes that have been created. The flashlight symbol of the search icon to search a topic (and its subtopics) has been replaced with a magnifying glass.
The Infocenter of VMware is hardly recognizable as such. The tabs are shown at the top instead of at the bottom. Maybe because today common web browsers do not have a status line and show the target of a link while hovering it in the left bottom corner which hides bottom tabs.
IBM, the company which has done most of the development work for Eclipse’s Infocenter, added a Collaboration tab to show hot topics and – if logged in – the user’s own comments. There is also a frame below the topic frame for topic-specific comments.
IBM has begun to replace this and other Infocenter instances with its new Knowledge Center. I guess but I don’t know that it is still based on Eclipse Infocenter. It does not use HTML framesets but an iframe for the topic. The search field is wider and the search scope follows automatically the selected book which covers a product.
Most of the modifications described above are about searching. Please drop a comment if you have come across an Infocenter with other modifications. If you like a modification then report it to Eclipse, or even better, implement it and contribute it to Eclipse and watch them reintroduce it into the wild.
August 19, 2014
Assuming you have help content and it comprises more than a couple of sentences, your users will explore it by searching the whole content or by following hyperlink by hyperlink, digging deeper level by level into the table of contents. In Eclipse Help it is also possible to search only part of the content by defining a scope or by selecting a topic and searching its subtopics. But this is rarely used because it is cumbersome. Also the wildcards ‘*’, ‘?’ and the boolean operators NOT and OR are rarely used. Just like with Google or DuckDuckGo people tend to search for keywords only.
Autocomplete, instant search and more
misuses a proxy which makes it slower than when integrated into your help. To see the content of a topic by hovering a search result you have to allow insecure content: click the shield icon in the address bar:
eh.js can also be used for searching a particular part such as a book or a chapter: Place the mouse over a TOC item link to display a search field for this topic and its subtopics only. Eclipse Luna Help contains 66 books and probably you do not want to get your search results flooded by hits in all of them. Or maybe you will use eh.js as a starting point to develop a complete new user interface for the good old Eclipse Help. What should it look like?
July 8, 2014
Today, the counter of the 13 Luna download packages passed the 1,000,000 mark. Two weeks for 1,000,000 downloads, that’s even faster than Kepler with 18 days. 70% of the downloads are from the three packages Classic, Java EE and Java. Three out of 13 (= 23%) packages for these 70% of the downloads are close to the 80–20 rule.
Compared to Kepler (Release plus SR1 plus SR2), which was downloaded 28,951,122 times, C/C++ has increased its percentage from 6.6% to 8.1%. The percentage of Classic has fallen from 43.4% to 36.3%. The new PHP package has already been downloaded more than 50,000 times (5.1%). The percentages of the other packages remained more or less unchanged.
June 25, 2014
In one year, 687 authors (339 committers and 348 contributors) committed about 40,000 changes to 76 Luna projects. With 61 million lines of code Luna is the largest simultaneous release ever.
Some highlights from my point of view:
- Java 8 support by Java Development Tools (Java IDE) and by API Tools (part of the Plug-in Development Environment), as well as by other Luna projects like Xtend, Object Teams and – thanks to the unchanged heap dump format – Memory Analyzer.
- Code Recommenders’ Snipmatch: Its usefulness depends on the quantity of good code snippets. So please share your cool snippets to make this an awesome feature!
- EGit’s rewrite feature of commit messages and the Interactive Rebase View: Maybe, in future Git and I will become friends. ;-)
- Split Editor: a 12-year-old bug has been fixed. Hoorray!
- Dark Theme: Even if I prefer brighter themes it’s good to have a choice.
- The new Terminals View (of the Target Communication Framework): command line (local computer) and PuTTY (remote computers) replacement.
For detailed information read my article “Mein Luna-Jahresrückblick” (in German) in the upcoming (25th July) Eclipse Magazin or in a condensed form online.
PS: Please feel free to use the diagram and screenshots (attribution is nice to have but not required). I opened a bug to collect and share material to promote Luna.
April 21, 2014
Can you find the Easter egg in Eclipse? Granted, it’s not a real Easter egg, but an egg or rather a non-circular ellipse. The Eclipse ellipse can be found in the program and window icons (not in the splash screen).
For instance, in eclipse256.png the Eclipse marble is 230 pixels wide and 223 (instead of 230) pixels high:
I’m curious how the new
Egglipse Eclipse logo will look by Christmas. ;-)
October 3, 2013
The first milestone of Vex 1.1 was published some months ago (if you don’t know Vex yet: it stands for Visual Editor for XML and is an Eclipse XML editor with a word processor like interface). Since then Carsten Hiesserich has joined the project team and mainly works on Vex’s built-in support for DocBook.
One month ago, with the second milestone we switched to Kepler. Unfortunately, the Eclipse Marketplace showed a couple of “one or more required items could not be found” errors and the number of milestone installations fell below 100 per month for the first time. So we decided to switch back to Juno (Eclipse 3.x) only for Vex 1.1, which is scheduled to be released in June 2014.
A couple of bugs have been fixed for DocBook support. In addition, in the Outline View there are now buttons to toggle the visibility of inline elements ( block elements are always shown), of processing instructions, of comments and of the first part of the contained text:
The Vex project has started to use Gerrit, a code review system which is used by other Eclipse projects, too. Vex also has a new separate Hudson instance which is required by Gerrit to veto a commit on failing JUnit tests. And this is Gerry, not to be confused with Gerrit, a young tomcat loafing around and vetoing my coding by walking over the keyboard from time to tim111111111111klllllllllllllll
Don’t be a fraidy-cat and get Vex 1.1 M3 with the new features and maybe new bugs! ;-)
Drag to install: (or use Update Site http://download.eclipse.org/vex/milestones/1.1/)
July 14, 2013
Overall, the 12 Kepler packages have now been downloaded one million times. On average, one million times in less than 18 days means one every 1.5 seconds. Wow!
In Kepler the Eclipse for Mobile Developers package is missing and the Classic package has been replaced by the Standard package which contains now the Marketplace client and Git. The first three most downloaded packages are all about Java development and have together a market share of more than 80%. The first non-Java package is the Eclipse IDE for C/C++ Developers with 6.5% market share.
The 13 Juno packages were downloaded approximately 28 million times (R, SR1, SR2 summed, Classic estimated). That was even one every 1.1 seconds. But in contrast to Kepler Eclipse 4.2.x was counted as the Classic package. In Kepler Eclipse Standard is not the same as Eclipse 4.3.0 and is not included in this calculation.
June 27, 2013
The following is an incomplete list of Kepler articles of news websites (no blog posts). Please add a comment if you know of any more articles.
Some hours before the release I sent e-mails to four German news websites that did not write about Juno last year, telling them when Kepler will be released, where the official press release will be published, some basic information, that they could use my bar chart and links for further reading. Two of them indeed published Kepler articles – a success rate of 50%.
Social networks grow more and more popular in news distribution. But in contrast to social networks and blogs news websites reach an extended audience. That is why I think that such news articles are important for us. Maybe next year we could send the official Luna press release upfront to the news websites with the release time and additional information about what Eclipse is and what a Simultaneous Release is. A set of screenshots and charts would improve the attractiveness of the articles and increase the chance the news will be adopted. What do you think?
June 25, 2013
1 year – 71 projects – 428 committer – 48,000 commits – 4,786 OSGi bundles – 58 million lines of code – these are the numbers of Kepler, which is the tenth Eclipse Simultaneous Release.
Compared to its precursor, Juno, the project count remained the same (taking into account the adjusted project number of Juno from 72 to 71 after the Juno release – reflecting that EMF Query 2 was not part of Juno after all). Four projects have left (Xtend, Jetty, Virgo and Runtime Packaging), four projects have joined (Stardust, Sphinx, EMF Diff/Merge and Maven Integration for Web Tools Platform). To be more precise, Xpand is still part of Kepler but it is no longer a project of its own, Xpand became part of Xtext. The highest version jump was made by Orion: from Orion 0.5 in Juno to Orion 3.0 in Kepler.
In the Kepler year the total number of bugs that were created is lower than in the years before. This could be caused by less (open) activity or/and an increasing use of Gerrit.
The satisfaction with Eclipse is still very high (around 80%) but less than in the years before.
For detail information read my article “Mein Kepler-Jahresrückblick” (German) in the upcoming (26th July) Eclipse Magazin or in condensed form online. I will also give a talk at Java Forum Stuttgart (also in German).
PS: Please feel free to use the diagrams (attribution is nice to have but not required). I opened a bug to collect and share material to promote Kepler.