| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is the first mechanical step to execute on the 'shared pool of
debugger/analyzer views' idea.
Future steps would be providing infrastructure for the view pool,
making all analyzer/debugger views use the pool and then re-extract
a sensible base for a 'analyzer-and/or-debugger' tool plugin interface.
Change-Id: I1bb392e6dd3084fc56937956bee1d6fd9530335d
Reviewed-by: Eike Ziller <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of describing icons via file name or in the themed icons case
via
a string that is a list of mask/color pairs, we have now a class for it.
Icons are now listed in per-plugin *icons.h headers.
RunControl::m_icon was The only place left where an icon property was in
fact a string. This patch changes that member to be a Utils::Icon.
Change-Id: Ibcfa8bb25e6d2e330c567ee7ccc0b97ead603177
Reviewed-by: Eike Ziller <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The old one had a number of problems, mainly due to the awkward
delegate that was used for presenting the data. For instance:
- Only one diagnostic at a time could be looked at
in detail.
- Once it had been opened, it was not possible to close
such a detailed view again, other than by opening a new one.
We now use a tree view for showing the diagnostics, so users
can show and hide details about as many diagnostics as they
wish. That also gets us sensible item selection capabilities,
so features like suppressing several diagnostics at once can
be implemented in the future.
Change-Id: I840fdbfeca4d936ce600c8f6dde58b2ab93b0d00
Reviewed-by: Nikolai Kosjar <[email protected]>
|
| |
|
|
|
|
|
| |
This makes the view of the valgrind tools avilable for other analyzers.
Change-Id: Icb28a3a6d6dbd7d437de803d50e30fada7dca0da
Reviewed-by: hjk <[email protected]>
|
| |
|
|
|
|
|
|
| |
The Analyzer implementation is now simple and still generic enough
to serve as general base.
Change-Id: I050a21919bf128929b77a64da1f46d157691d849
Reviewed-by: Daniel Teske <[email protected]>
|
| |
|
|
|
|
|
| |
More flexible, less over-engineered this way.
Change-Id: I3e224a6be85d3a187056d79fd506e8cf6a32c8a9
Reviewed-by: Daniel Teske <[email protected]>
|
| |
|
|
|
| |
Change-Id: I74edaef59600a44924d2692c1ebc7f98d8581115
Reviewed-by: Christiaan Janssen <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
| |
Separating out the run control factories is the initial
step towards separation of run control from QML profiler
engine. The goal is to to make the engine agnostic of
the run control.
Change-Id: Ic8279755f0188ab53253a62322fcccf1c17b6aaf
Reviewed-by: Christian Kandeler <[email protected]>
Reviewed-by: Christiaan Janssen <[email protected]>
|
| |
|
|
|
|
|
|
|
| |
The _LIBRARY defines for plugins should consist of the plugin name
plus the suffix _LIBRARY to make it possible to generate those
automatically.
Change-Id: Icafc9bce876d77521b47d815c94e7df6da061a51
Reviewed-by: Oswald Buddenhagen <[email protected]>
|
| |
|
|
|
|
|
|
| |
the information is redundant now
Change-Id: Icc8c8b4ace11538d45c6c9e1dbe5a7976f4743e1
Reviewed-by: Tobias Hunger <[email protected]>
Reviewed-by: Eike Ziller <[email protected]>
|
| |
|
|
|
| |
Change-Id: I4025539f3875e79f03743ba9ed3fd09cd31b998d
Reviewed-by: Tobias Hunger <[email protected]>
|
| |
|
|
|
| |
Change-Id: I25645bb625b467c6f9d895ff89a70acd6a25683e
Reviewed-by: Tobias Hunger <[email protected]>
|
| |
|
|
|
| |
Change-Id: I2b6c5876cafb7cf19fc3040bc84fd88a90b6c0e0
Reviewed-by: hjk <[email protected]>
|
| |
|
|
|
|
|
| |
Easier to refactor.
Change-Id: I151364182df841e7e543f480b1836a1b1897e913
Reviewed-by: Tobias Hunger <[email protected]>
|
| |
|
|
|
| |
Change-Id: If5ad70222983d5dede57fb7443262a736114b85e
Reviewed-by: hjk <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Having one factory per tool (or plugin) created some bugs:
* analyzer project settings being created twice
* per-project analyzer settings widget duplicated
Also, most of the code from the run control factory were copied.
Now, the Analyzer only creates one run control factory shared among all tools, and the IAnalyzerTool
has two new virtual method: canRun and createStartParameters. It simplify the code a bit, and
creating a new analyzer tool is easier (only two classes to subclass: IAnalyzerTool and IAnalyzerEngine).
Change-Id: I4e180846a26b74b2b77cb99bc97534d680a80a4d
Reviewed-by: hjk <[email protected]>
|
| |
|
|
|
|
| |
Change-Id: If74c8035bc83a8113c2a15dcacefa38afbbbb4d8
Reviewed-on: http://codereview.qt.nokia.com/1056
Reviewed-by: hjk <[email protected]>
|
| |
|
|
|
|
|
|
|
| |
It's all dockwidgets now.
Change-Id: Ia47ca9331fdfbe12ca11f77c26afc35e73a2fae3
Reviewed-on: http://codereview.qt.nokia.com/776
Reviewed-by: Qt Sanity Bot <[email protected]>
Reviewed-by: hjk <[email protected]>
|
| |
|
|
| |
Change-Id: I2909a4610afa074e7ace56406b176336b43f7b3f
|
| |
|
|
|
| |
Merge-request: 284
Reviewed-by: hjk <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
| |
- Introduce a shared analysis output pane using a stacked widgets,
layouts for the tools' output panes and toolbar widgets.
- Introduce IAnalyzerOutputPaneAdapter interface returned
by IAnalyzerTool to manage them.
- Remove mode and its mainwindow contents (depending on enum
constants should use cases for it occur).
Reviewed-by: con
|
|
|
Merge-request: 260
Reviewed-by: hjk <[email protected]>
|
