Perspective Layouts - Programmatic vs Declarative

one issue that developers new to rcp face is whether to add ui elements programmatically or declaratively. in my experience, most initially choose the programmatic approach because it seems more familiar. you know, why mess with extension points when you can just code it up and be done with it.

but it’s almost always better to do things declaratively through extension points, the main reason being that doing so allows you leverage the power of rcp as a modular user interface framework . to illustrate this, let’s look at our options for laying out perspectives.

programmatic layout = centralized / hard coded

here is the simplest code needed to add a view to a perspective programmatically. to do so, we implement the iperspectivefactory interface and add a view using its string id.

public class myperspectivefactory implements iperspectivefactory {

	public void createinitiallayout(ipagelayout layout) {
		layout.addview(myview.id, ipagelayout.bottom, 0.5f, layout.geteditorarea());
	}

}

the problem here is that we’ve coupled our perspective to the view being added. this view may exist in the same plug-in as the perspective, but often it does not. if the view is in a different plug-in, we have to declare a dependency on that plug-in just to add the view. it’s possible to reduce the coupling somewhat by replacing myview.id with the actual string id itself, but hidden dependencies based on string equivalency are arguably even more smelly.

in the end, a programmatic perspective layout results in a hard-coded and centralized architecture looking like this.

declarative layout = decentralized / modular

the declarative approach based on extension points resolves these issues. to layout a perspective declaratively we extend the org.eclipse.ui.perspectiveextensions extension point.

<extension point="org.eclipse.ui.perspectiveextensions">
 <perspectiveextension targetid="com.mycompany.myperspective"> 
<view id="com.mycompany.myview" minimized="false"
 ratio="0.5" relationship="left" relative="org.eclipse.ui.editorss"> 
</view> 
</perspectiveextension> 
</extension>

using this approach, each plug-in adds the views that it knows about, resulting in a decentralized architecture where the plug-ins containing the views are now in control.

note that we have not eliminated all coupling, as the perspective extensions still need to refer to the perspective by its string id, but this is not as bad as it sounds. perspectives are much more static than views - you typically define them and make few changes afterwards. views, on the other hand are often moved from one plug-in to another or have their purpose (and potentially their id) redefined. decentralizing control allows you to make these kinds of changes without breaking the perspective layout.

conclusion

adding ui elements declaratively is definitely the way to go. it gives you much more flexibility (e.g. you can add views to perspectives you didn’t create) and also allows you to leverage the modular nature of the framework.

sure, there will always be cases where a declarative approach cannot be taken, particularly when some part of an api is not yet surfaced in the related extension point. but in the absence of such a need, i urge rcp developers to always turn first to the extension point mechanisms and fall back to programmatic approaches as a last resort. as your application evolves over time, you’ll really come to enjoy the flexibility and increased reusability that a declarative approach makes possible.

from http://rcpquickstart.com/