|Re: [cdt-dev] Building a Swing UI for CDT|
Thanks for getting back to me so quickly.
> CDT's debugger implementation is implemented for the Eclipse ecosystem, this means it is dependent on OSGi, Eclipse platform UI and Non-UI components and a whole raft of other supporting services.
I was afraid this would be the case. Sounds like I'll likely have to roll my own debugger adapter. Thanks for pointing me in the direction of DAP. While DAP is not the out-of-the-box solution I was looking for, it will be highly beneficial to get me going in the right direction. Through the articles on your website I was able to find the lsp4j project you've been working on. So thanks for writing the articles and actively working on lsp4j, it's likely what I'll end up using!
From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Jonah Graham <jonah@xxxxxxxxxxxxxxxx>
Sent: Thursday, September 13, 2018 12:46:40 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Building a Swing UI for CDT
> Is the Eclipse UI neatly encapsulated away from the CDT business logic such that I could have the Swing UI call into the CDT core code?
CDT's debugger implementation is implemented for the Eclipse ecosystem, this means it is dependent on OSGi, Eclipse platform UI and Non-UI components and a whole raft of other supporting services.
The trend going forward is to build new debuggers front and back end based on the Debugger Adapter Protocol (DAP), there is still a long way to go before there is any implementation of DAP that is as feature full as CDT. The advantage to this approach is that it provides more clear delineation between front-end UI and back-end.
I assume you are looking into this due to the start-up performance of the standalone debugger? If so, there may be other (less expensive) options, so let's keep the discussion going.
On Thu, 13 Sep 2018 at 19:28, Mr anderson <fc21@xxxxxxxx> wrote:
Back to the top