| Re: [cdt-dev] What happened to the Dom Ast View |
|
Well, I’m not certain there really is an Eclipse convention for what an SDK is. It’s been brought up numerous times on the planning council. The better question is what do developers need in an SDK to build CDT extensions. I could see this view being there. But I would also want to make sure that only those people get it, which brings us back to my philosophy on this. We actually have two users of the current SDK.
One to get at the source bundles, which is often required by downstream legal teams, and unfortunately, that’s what the current SDK is. And one is to for aforementioned CDT extension developers, i.e. a real SDK. We would need to split them out and that’s a
fair amount of work. It’s probably easier for extension developers to checkout the repo from git and work with that. Doug.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Sergey Prigogin On Tue, Jan 3, 2012 at 8:55 PM, David Glaser <dglaser@xxxxxxxxxxxxxx> wrote: Sergey, You said
“Your use case is not representative of a regular CDT user. You can get the org.eclipse.cdt.ui.tests plugin
from CDT git repository.” Out of curiosity, what are the expected use cases of people who make use of the CDT SDK. I had
thought that CDT SDK would be used for developing language sensitive editors, refactoring tools, code analysis tools, etc. All of these tools look at the parsed representation of the C++ code – the AST DOM tree and us tool developers would like to examine
the DOM tree to make sure we understand the structure for a particular C++ construct. By Eclipse convention SDK is just the run-time plus the source code. It means that any functionality included in SDK will also appear in non-SDK CDT installations. Regular CDT users programming in C++ are not interested in the AST DOM view.
-sergey
|