| commit | 1ea7fb94e9d620093b6fdcda33cec0fdad620429 | [log] [tgz] |
|---|---|---|
| author | Patrick Tasse <patrick.tasse@gmail.com> | Wed Jun 12 16:15:41 2019 -0400 |
| committer | Patrick Tasse <patrick.tasse@gmail.com> | Thu Jun 13 14:40:42 2019 -0400 |
| tree | 4eccb2f6e015ff944604fa6fae438297449e1ee5 | |
| parent | e59f68e3de1c2e770d21f8a05ad330271c03ea06 [diff] |
tmf: Improve tooltip layout and preferred size calculations Make each tooltip content calculate once and return its preferred size at creation. Only BrowserContent needs to include the vertical scroll bar width in the preferred size. Its ScrolledComposite does not need V_SCROLL style, since it is handled by the Browser widget. DefaultContent should calculate the preferred size using the inner content Composite, because the ScrolledComposite preferred size includes its scroll bars' sizes, which are not visible if the tool tip is at the correct preferred size. The BrowserContent body margin can be configured, it is reduced to 3px. The BrowserContent content has a 1px margin, it should be included in the preferred size calculations. The DefaultContent does not need to override its parent layout, which is a FillLayout. The GridLayout added a default marginWidth/Height of 5. Change-Id: I6547ea914cd8afba75793ad8f0ac43ced1375d7f Signed-off-by: Patrick Tasse <patrick.tasse@gmail.com> Reviewed-on: https://git.eclipse.org/r/143892 Tested-by: CI Bot Reviewed-by: Simon Delisle <simon.delisle@ericsson.com> Tested-by: Simon Delisle <simon.delisle@ericsson.com>
This source tree contains the source code for the Trace Compass plugins for Eclipse.
The plugins are categorized as follows:
analysis/ | Generic extensions to the base framework btf/ | Best Trace Format (BTF) integration common/ | Generic utilities that can be used by other plugins ctf/ | Common Trace Format (CTF) reader library doc/ | Documentation and code examples gdbtrace/ | Support for reading and viewing GDB traces lttng/ | LTTng integration pcap/ | libpcap integration rcp/ | Code specific to the RCP version releng/ | Releng-related plugins statesystem/ | State System library tmf/ | Core framework
See the components.svg file for a diagram showing the dependencies between the different components.
To set up the environment to build Trace Compass from within Eclipse, see this wiki page: http://wiki.eclipse.org/Trace_Compass/Development_Environment_Setup
The Maven project build requires version 3.3 or later. It can be downloaded from http://maven.apache.org or from the package management system of your distro.
To build the project manually using Maven, simply run the following command from the top-level directory:
mvn clean install
The default command will compile and run the unit tests. Running the tests can take some time, to skip them you can append -Dmaven.test.skip=true to the mvn command:
mvn clean install -Dmaven.test.skip=true
Stand-alone application (RCP) packages will be placed in rcp/org.eclipse.tracecompass.rcp.product/target/products.
The p2 update site, used for installation as plugins inside Eclipse, will be placed in releng/org.eclipse.tracecompass.releng-site/target/repository.
The following Maven profiles and properties are defined in the build system. You can set them by using -P[profile name] and -D[property name]=[value] in mvn commands.
-Dtarget-platform=[target]
Defines which target to use. This is used to build against various versions of the Eclipse platform. Available ones are in releng/org.eclipse.tracecompass.target. The default is usually the latest stable platform. To use the staging target for example, use -Dtarget-platform=tracecompass-eStaging.
-Dskip-automated-ui-tests
Skips the automated UI integration tests. Not required when using -Dmaven.test.skip=true, which already skips all the tests.
-Dskip-rcp
Skips building the RCP archives and related deployment targets. Only works in conjunction with -Dskip-automated-ui-tests, due to a limitation in Maven.
-Pctf-grammar
Re-compiles the CTF grammar files. This should be enabled if you modify the .g files in the ctf.parser plugin.
-Prun-custom-test-suite
Runs a test suite present in releng/org.eclipse.tracecompass.alltests. The test suite to run has to be defined by -DcustomTestSuite=[name], for example -DcustomTestSuite=RunAllPerfTests.
-Pdeploy-rcp
Mainly for use on build servers. Copies the generated RCP archives, as well as the RCP-specific update site, to the paths specified by -DrcpDestination=/absolute/path/to/destination and -DrcpSiteDestination=/absolute/path/to/destination, respectively.
-Pdeploy-update-site
Mainly for use on build servers. Copies the standard update site (for the Eclipse plugin installation) to the destination specified by -DsiteDestination=/absolute/path/to/destination.
-Psign-update-site
Mainly for use on build servers. Signs all the generated update sites using the Eclipse signing server.
-Pdeploy-doc
Mainly for use on build servers. Copies the generated HTML documentation to the destination specified by -DdocDestination=/absolute/path/to/destination. Some directories may need to already exist at the destination (or Maven will throw related errors).
