The code of the qmlprofiler client has become a bit too complex,
this patch reorganizes the modules in a more sensible way,
having the modules communicate with each other through a
state machine instead of the excess of signals and slots
from before.
Change-Id: I76f7313779888a1bd07a1cdb1acbf2e47aacf42a
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>
Add either QtDeclarative (Qt 4) or QtQuick1 (Qt 5) to QT.
Mixing them leads to problems with include paths and linking.
Change-Id: I188240641216ee227931a7be2105bc4838385c79
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>
- Add Q_PLUGIN_METADATA for Qt 5, use Q_EXPORT_PLUGIN
for Qt 4.
- Generate the Json files for Qt 5 from the pluginspec
files by using a XSLT sheet.
Change-Id: I8653f182ae7d61615971c093df10b84fb06c2172
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
This can happen when e.g. the first attempt failed because of an
unavailable port.
Change-Id: I7e61c6f6d0a65c48c1b7031be95bdabd965fe5ab
Reviewed-by: Christiaan Janssen <christiaan.janssen@nokia.com>
* Removed utils, extensionsystem and aggregation dependencies
for plugins that depend on Core
* Capitalized Find and CPlusPlus
Change-Id: I505e5f46976f26da47ad778860f103b173668b1c
Reviewed-by: Joerg Bornemann <joerg.bornemann@nokia.com>
Actually wait for the 'Waiting for debugger on port ' ... message
to appear in the application output before connecting, and also
use the port specified there.
Change-Id: Ib498e5306bc49f2f3d468353b1c5d1ea38a809e6
Reviewed-by: Christian Kandeler <christian.kandeler@nokia.com>
This is the first step of a larger refactoring. The plan is to make
debuggersettings more orthogonal to individual runconfiguration
implementation. This patch alone already pushes the settings handling
to the debugger plugin and removes code duplication in the
runconfiguration implementation.
Change-Id: I4c78d1658ea462d3df14b873f8f41cc918a23f1a
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>
Reviewed-by: hjk <qthjk@ovi.com>
This patch avoids showing the "use the stop button" if the
application dies but the trace data was sent in time.
Note: with the current implementation in Qt5, the application
sometimes closes before all data could be sent. That happens
with any non-trivial qml application.
Change-Id: Ie7b1568b2d69320d1887587dccac40a4b4d4d788
Reviewed-by: Aurindam Jana <aurindam.jana@nokia.com>
also
QmlProfiler: refactor eventlist state
If unexpected data is received, assuming server stopped profiling.
Also, introducing a eventlist state instead of relying on
signals sent around. This is part of a coming bigger patch
where the profiler client is refactored.
Change-Id: Ibed9007903956daf03cc0fcb90f77b5ad2d3cf90
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>
Getting the #include directives ready for Qt5. This includes the
new-project wizards.
Change-Id: Ia9261f1e8faec06b9285b694d2b7e9a095978d2b
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>
When resetting data, the variable that tracks vertical scroll
on the qml side could go out of sync with the scroll bar.
Fixed by resetting both scrollbar and variable at reset.
Change-Id: I3a130192d460568c44de815d71aa6290c311c89a
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>
User can choose to see them through the context menu.
Change-Id: Ibf1670098126658af497c7a87b46c26f6dd2d41e
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>
When selecting event before the timeline has been
rendered at least once.
Change-Id: I8f34ebacb948163f57e3c2bc893d17c745366294
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>
When the server sends more than one trace consecutively
(e.g. with the profiler JS API), the flags that control
the race condition between the v8 client and the qml
client need to be reset after the data is read. Otherwise
the complete signal will be duplicated.
Change-Id: I63b808d6f0aae404814d5243c1729671b56ca52e
Reviewed-by: Aurindam Jana <aurindam.jana@nokia.com>
QString::fromLocal8Bit() and QString::fromUtf8() are much more slower
than an obvious QString::fromLatin1() and QLatin1String(), so this
commit changes some places where these functions are really not
needed.
QString::fromLatin1() is used in case if QString object is used
immediately (something like QString::fromLatin1().arg()),
QLatin1String is used otherwise like in other places (for example,
QPixmap(QLatin1String("..."))) - to allow to use default QString
constructor and work with QT_NO_CAST_FROM_ASCII.
Change-Id: Ib6eb1c61e9cb35c7c5b7569fea77c5e41d32621a
Reviewed-by: hjk <qthjk@ovi.com>
The JS profiler doesn't use column information. This can produce
undesired side effects when changing the selection from the
QML pane if the signal bounces back.
Change-Id: I76d8c97c53b0c4800f855054cdb5ff5e8d034d65
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>
Due to space restrictions, the descriptive text of events
in the labels column of the timeline view are elided. This
patch adds tooltips on mouseover with location and details.
Change-Id: I229988e114f21e4d9575dff137aa91918ad1afa3
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>
The ':' text item in Detail.qml was visible in RangeDetails
and SelectionRangeDetails. Looked like an irritating text
rendering artifact on the left of the Deatil labels.
I assume that the Text Item was of no use and removing it is
fine.
Change-Id: Ic9c4eec495219b288d18d2179197ffaf01e00afe
Reviewed-by: Christiaan Janssen <christiaan.janssen@nokia.com>
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 <qthjk@ovi.com>
The profile clients now also listens to profiling data sent by
console APIs console.profile and console.profileEnd
Change-Id: I7f7100448263889076e94a1e251b8977ce047843
Reviewed-by: Christiaan Janssen <christiaan.janssen@nokia.com>
