| Re: [cdt-dev] Blog on the New CDT |
|
Hi Doug,
Thanks for the link. A couple of us will join for the CDT call next week.
Regards,
Marc From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
Sent: Friday, November 2, 2018 11:30 AM To: CDT General developers list. Subject: Re: [cdt-dev] Blog on the New CDT Actually, it’s on a topic branch.
https://github.com/dschaefer/cdt-gdb-adapter/tree/init-contrib
From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx>
On Behalf Of Doug Schaefer
Debug Adapter appears in my fork of cdt-gdb-adapter. I am awaiting CQ approval on vscode-debugadapter before pushing it to its eventual home.
https://github.com/dschaefer/cdt-gdb-adapter
It is early days. We have basic functionality working. We don’t have a test framework in place yet. Jon who’s doing the work here is looking at expressions next.
We can certainly talk about the structure at the call next week. We have a long history of CDT being a diverse project with a single pool of committers. I think that’s been successful, especially times like now where we have so few active committers. Creating project structure for the sake of project structure has its costs that we can’t necessarily afford. Having a big project with lots of different interesting parts helps us look interesting as a whole. But I’m happy to be shown my thinking is incorrect here or work through any issues you may have.
Doug.
From:
cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx>
On Behalf Of Marc Dumais
Hi Doug,
For us, how this is structured is important; how products are split into projects would ideally enable cooperation in the areas where it makes sense, but permit separation of concerns otherwise. e.g. the jdt and jdt.ls projects seem to have achieved something like that, setting up as parent-child projects.
Can we discuss this on the next CDT monthly call?
In the meantime, we are curious to look at your DA contribution. Do you have an ETA for the drop?
Regards,
Marc
From:
cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
After the summit, Jonah and I were chatting about the VS Code extension. I was picturing the entry in the Marketplace where the publisher name was Eclipse CDT. My gut feel is that gives us a huge advantage out of the gate. People know the CDT project and to have our name on a VS Code extension gives it instant credibility. The same will be true for Theia and any other IDE we decide to help.
For me CDT has always been a project, a group of collaborators, never a product or a thing. The product is the Eclipse IDE for C/C++. That doesn’t change. We just have other products that plug into VS Code and Theia.
But I am open to the idea of a new project at Eclipse if you can paint the picture, in particular what it would look like, and show how we’d better off.
Doug.
From:
cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx>
On Behalf Of Marc Dumais
Hi Doug,
"The idea is to bring that to other IDE front ends. And I want to remain a part of Eclipse for all the reasons we're here in the first place. The solid foundation with strong IP providence and great IT support. I don't know a similar place to do this. That's why I believe CDT is the only place this can happen. (And, yes, I looked for one)"
Regards,
Marc
From:
cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
Funny enough, the priority is on collaborating with great people
☺. We have a lot of expertise in C/C++ development environments. The idea is to bring that to other IDE front ends.
And I want to remain a part of Eclipse for all the reasons we're here in the first place. The solid foundation with strong IP providence and great IT support. I don't know a similar place to do this. That's why I believe CDT is the only place this can happen.
(And, yes, I looked for one)
| ||||