Skip to main content
Jump to: navigation, search

Difference between revisions of "PDE/Incubator/Picasso"

< PDE‎ | Incubator
(Migrated to PDE)
(Replaced content with "= This page is out-of-data, Picasso has been migrated to PDE = See")
Line 2: Line 2:
=== Work Area  ===
The goal of Picasso is to provide a utility to help debugging UI layout issues. Picasso does this by painting the workbench in a way to aid debugging.
=== Developers  ===
*Chris Aniszczyk
*Simon Archer
=== Plug-ins  ===
*[ org.eclipse.pde.picasso] [ [PSF]]
=== Painting with Picasso  ===
To use Picasso, simply [ check it out] and then launch with the tracing options enabled:
*<code>paint</code> - Check this option to enable Picasso. When checked Picasso will paint the workbench.
*<code>paint/extraCompositeMargin</code> - The value of this option is used to pad every <code>Composite</code> object's margin width and height. Typically the default value of <code>0</code> is what you want, but a value of <code>5</code> or <code>10</code> is helpful to ''explode'' a view to reveal the child/parent widget relationships.
*<code>paint/toolTip</code> - Check this option to enable custom tool tips that describe the layout of each widget. While useful, it can be helpful to disable tool tips since they are sometimes large and distracting, especially when all you care about is the way the layout looks.
<br> [[Image:Picasso.png]]
=== Tips  ===
By painting the workbench with Picasso you can easily spot layout issues such as:
*Unnecessary margin padding on <code>Composite</code> widgets. This is typically caused by using <code>GridLayout</code> and not setting the <code>marginWidth</code> and <code>marginHeight</code> fields to <code>0</code>.
*Radio buttons and checkboxes that stretch to consume all available horizontal whitespace. This results in the whitespace to the right of the label being clickable. Doing this can result in the user accidentally selecting a radio button or toggling a checkbox by simply giving focus to the UI. As with push buttons, radio buttons and checkboxes (they're buttons too) should generally not stretch.
*Inappropriate stretching and whitespace consumption.
=== System Properties  ===
The behavior of Picasso can be controlled via the following System properties. Notice that the property keys exactly match the tracing options:
Using these System properties make it possible to control the behavior of Picasso without having to understand how to use and configure tracing options at runtime. One easy way to set these properties is to add them to <code>eclipse.ini</code> after the <code>-vmargs</code> line.

Latest revision as of 12:49, 1 December 2017

This page is out-of-data, Picasso has been migrated to PDE


Back to the top