The next release of richhtml4eclipse is available. With 0.3 the following new features were added:
Check out the latest release on SourceForge.net. Feedback is really appreciated.
Screenshot of the 0.3 Example Toolbar
If you build your own editor in the most cases you have to provide the capability to print its content. In addition you probably also have to print different business-logic that is not presented by an editor or viewpart. SWT gives you the possibility to generate printing jobs, what is a bit complex. With the Open-Source API PaperClips there is a possibility to generate data that can be sent to a printer in a very easy way. In addition it provides cool UI-Elments, e.g. a Print Preview. In this article is explained how to register a Print-Action as GlobalAction Handler, with formatting the data you want to print and a Print-Preview.
Do you know the palette from GEF?- It is THE Creation Tool for graphical Editors based on GEF. Unfortunately the requirement is often to drag and drop already created objects into the graphical viewer, e.g from a navigation view, or another JFace-Viewer. Therefore you have to implement your own Drag’n Drop mechanism that is also compatible with the EditPart concept and your Commands. Today I want to show you a way how to drag elements from a TableViewer and drop them on my EditParts. Before dropping the elements you have the possibility to hook in your own code for showing an additional wizard/dialog or if you want to manipulate/replace/adapt the dragged model-object. I have written a small manager and that decides when and how a drop is allowed and how to process the dropped data.
Let me tell the truth. It’s not as difficult as it sounds. 
When using a ScrolledComposite, I always had the problem, that I couldn’t use the wheel of my mouse for vertical scrolling. I was really annoyed about it. But now I have found a really simple solution.
A common usecase is running long processes and waiting for their completion. Therefore responsiveness is an important feature, that can be realized with the jobs-framework provided by eclipse. The user wants to continue working while a long running job is scheduled, not sitting in front of a frozen UI that is not responding until the job has finished.
Today I want to demonstrate some key features of the jobs api and encourage RCP developers to use the functionality to make a user friendly interaction and a clear management of your application-specific jobs. A good article for this topic you can find on the eclipse-website.
Do you know the Perspective-Bar? - And have you ever tried to integrate the perspecitve-bar in your RCP? If yes, did you suceed?
From my experience, perspectives are really useful for representing blocks of funtionality, something like a workflow or a set of requirements that are bundled. The perspective-bar is a very nice feature, necessary in the JDT but has a great disadvantage: The lack of integrity.
When I made my first “Hello World” PlugIn I didn’t care about such things like Data-Workflow or Application Data Tree, I just tried the different features the framework provided. But as the applications became more and more complex and also the amount of different views, perspectives and editors increased I was forced to implement different mechanism to manage all the different data and their presentation. In this article I want to show how to install the Model-View-Controller in your RCP to make a clear software-archictcture and flexible ways for interacting between view and model.
Have you ever recognized the complex widgets that are implemented in the IDE plugins?- The most different use cases shipped by plugins like the Compare-Plugin, Team-Plugin, JDT-Plugin are realized with very good looking and also good feeling widgets. So I thought I try to encapsulate such a widget that I can use it in every context. This article gives an overview about a DetailedSectionViewer, which is based on the org.eclipse.ltk.internal.ui.refactoring.history.RefactoringHistoryControl. (more…)
In Eclipse 3.1 there was always the problem that you couldn’t give a sort indicator to a sortable TableViewer. This issue was resolved with Eclipse 3.2. Today I want to show a simple TableViewer with a sorting and indicators, filters and a column reordering. Unfortunately the implementation for the sorters on JFace-Viewers don’t support an ascending or desending flag that takes also care for the indicator-representation. We have to implement this for our own.
Every RCP-Developer is familiar with this question. From a technical view the differences are very well explained by the authors from the eclipse3.0 faq. But is this really helpful? - Which criteria are really important in deciding which graphical components you’ll use? In this article I’ll share my experiences and decisions regarding views and editors.
Powered by WordPress