A first version of the YARI core components (Eclipse- and SWT-Inspector) is available for RAP 1.4 applications. You can download it from http://sourceforge.net/projects/yari/files/yari4rap/ and add it to your rap target platform.
Note: The Eclipse YARI and the RAP Yari is (not yet) binary compatible.
YARI is a comprehensive tool suite to debug, spy, spider, inspect and navigate Eclipse based application GUIs (Workbench or RCP). Just add it to your Eclipse installation or your target platform and you have runtime access to a bunch of information about installed Plug-Ins, opened workbench parts or you can inspect the ui and its layout.
Using the Eclipse Inspector view you will get the important information about the actual eclipse workbench. See which Plug-In contributes the active part, find actions and URIs for main menu entries, inspect the workbench with its active part, opened editors, views and perspectives, get an overview of all available OSGi and Eclipse services or search all available Eclipse Extension points and see which bundle contributes to which extension or debug complex Eclipse expressions or sourceProvider variables at runtime using the Expression Evaluator dialog.
The SWT Inspector view allows you to navigate through the whole widget hierarchy, inspect and change at runtime layout constraints and see immediately how this change effects to the current layout. Get the SWT Style of a widget in plain text. Change the background color of all the workbench controls to find invisible widgets or see where the controls border exactly is; no more
control.setBackgroundColor(…) is needed in your code, just change the color at runtime.
Open the Bundle Inspector view to get an OSGi Management Agent. Control the lifecycle of already installed bundles. Install bundles from local or remote sources. Diagnose problems if a bundle cannot change to the active state. Inspect bundle headers, call functions on the bundles or have a look at the OSGi log entries using the OSGi log service.
If you have (buddy) class loading problems: Open the ClassLoader Inspector to see which bundle class loader loads which class or which bundle has access to a specific class. This "search" functionality is especially helpful if buddy class loading is used.
Use an extended version of the SWT Sleak tool to find resource leaks or identify the identical resources which are allocated more than one time.
See the Yari Wiki for further information:
Have a lot of fun!