| 2014-03-26 12:14:58 |
David Planella |
description |
Now that the new scope template has landed in Qt Creator, the next step is to integrate the Scopes Tool to run the scopes from the IDE.
Broadly, this will require:
- Launching the Unity Scopes tool [1] with the Run button from the Unity Scopes template
- Adding required dependencies to the SDK to install the Unity Scopes tool
[1] https://code.launchpad.net/~unity-team/unity8/unity-scope-tool |
Now that the new scope template has landed in Qt Creator, the next step is to integrate the Scopes Tool to run the scopes from the IDE.
Broadly, this will require:
- Launching the Unity Scopes tool [1] with the Run button from the Unity Scopes template
- Adding required dependencies to the SDK to install the Unity Scopes tool (bug 1297812)
[1] https://code.launchpad.net/~unity-team/unity8/unity-scope-tool - package unity-scope-tool |
|
| 2014-04-01 14:50:16 |
David Planella |
description |
Now that the new scope template has landed in Qt Creator, the next step is to integrate the Scopes Tool to run the scopes from the IDE.
Broadly, this will require:
- Launching the Unity Scopes tool [1] with the Run button from the Unity Scopes template
- Adding required dependencies to the SDK to install the Unity Scopes tool (bug 1297812)
[1] https://code.launchpad.net/~unity-team/unity8/unity-scope-tool - package unity-scope-tool |
Now that the new scope template has landed in Qt Creator, the next step is to integrate the Scopes Tool to run the scopes from the IDE.
Broadly, this will require:
- Launching the Unity Scopes tool [1] with the Run button from the Unity Scopes template
- Adding required dependencies to the SDK to install the Unity Scopes tool (bug 1297812)
Conversation with zbenjamin about the implementation:
<dpm> The unity-scopes-tool launches scopes. In summary, you get a libyourscope.so and a yourscope.ini file in your build directory that unity-scopes-tool takes care of launching. When you hit Ctrl+R, unity-scopes-tool should be invoked with the .ini file as its argument
<zbenjamin> dpm: and unity-scopes-tool will then run as long as you can see the scope?
dpm: then it would be relatively easy
<zbenjamin> bzoltan: for that to happen we need to gather some people and talk about how we can recognize the "type" of a project. Like if its a scope, qml, qml+backend, html app
<dpm> zbenjamin, unity-scopes-tool is a full-blown app, so it has a close button and it will run until you close it
<dpm> zbenjamin, you can recognize it's a scope by the presence of the .ini file
<zbenjamin> dpm: well will the ini file always be at the same place in the project tree? I guess its a cmake project right? So i can even create it on the file
<dpm> zbenjamin, I'd say we support the tree layout that the scopes template creates already, so in that case, yes, the .ini file would always be at the same place
<zbenjamin> dpm: ok i guess i can use the same trick and depend on make install
dpm: thats what i do for apps atm: make DESTDIR=local install, and then search for the manifest and desktop files to get the exec line. Maybe i can check if the .ini file is there and start the scope-tool
[1] https://code.launchpad.net/~unity-team/unity8/unity-scope-tool - package unity-scope-tool |
|
