I launched an issue to the provider of the package for this enhancement yesterday, but there is still no feedback.

In the meantime I checked other packages and found the package "terminal tab". This is providing you a terminal within the atom surface, where you can launch clickable like in a desktop shell. So you need not to change between windows/applications. This may help in the meantime.

Any other supporter is welcome too (and required for my impression). It would be great if we can find a specialist for atom extension packages who is willing to prepare some improved tools for development.

@advocatux : Yes I have seen it, and there are some interesting options still to evaluate. I already tested the log command, which is quite helpful and a first step to see roughly what is going on. It still cannot replace a good debugger.

@hummelbach:

thank you for your proposal. I tried it already for test purposes on my desktop. After resolving the network issue I could install the necessary image. However, when testing I get an error message related to missing graphics drivers, which are installed according to apt.

Nevertheless, for the small tests I actually run it is still working.

Dear Fulvio,

thank you for your feedback. I will carefully go through these examples.

However, I'm a litte bit concerned about the way UBtouch is going. You are leaving the QT creator IDE for new IDE with as little support for installing toolchains as possible (at the first glance).
You are switching to cmake, which is new for me, too. So porting my QT based applications (using qmake) becomes more and more heavier.
At the first glance I'm missing debug capabilities in ATOM. This is a major drawback for me. Please correct me if I'm wrong.

So far I have reviewed the tedit code, where the c++ plugin is getting the filename from the qml part, so far nothing special on the c++side. By this configuration you are restricted to the directory space which are allowed in the qml environment. And quite this environment is the open point for my.

So the next step would be to install a working toolchain under ATOM.