Re: [cdt-dev] Building a Swing UI for CDT

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

> 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.

Jonah

~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com

On Thu, 13 Sep 2018 at 19:28, Mr anderson <fc21@xxxxxxxx> wrote:

Hi,

I'm interested in building a Swing UI for the core features of CDT. I'm most interested in creating a Swing UI for debugging that leverages all the great existing CDT business logic. Something similar to the CDT standalone debugger, but using Swing rather than SWT.

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? Has this type of project been explored or completed before with success?

Thanks in advance for any insight,

Morn

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev