|
It's just an example. But the CDT committers don't often look at the WTP project to see if they have things they would need. One could assume that WTP only does Web tools. XML editing isn't often considered a Web tool.
A bigger one may be _javascript_. It's a good thing I did look over there or I would have built a entire _javascript_ IDE for my Qt desktop and embedded developers.
Sent from my BlackBerry 10 smartphone on the Rogers network.
From: Konstantin Komissarchik
Sent: Friday, October 16, 2015 12:46 PM
To: Discussions about the IDE
Reply To: Discussions about the IDE
Subject: Re: [ide-dev] Ctrl-1 driven development
|
Why is it important that WTP does all the leg work to get the xml editor in all packages? The package owners could take the initiative. I notice, for instance, that the C++ package doesn't include it for some reason.
Konstantin Komissarchik
Senior Development Manager
Eclipse Tools Group
Oracle
Hi.
Why does it matter if the XML Editor is under the WTP top-level project. It is available as a separate feature, so all EPP packages can include it.
It would be fine if WTP took full responsibility for it and promoted it as the Eclipse XML editor and ensure EPP packages were using it, and all users knew about it. And if that’s happening then there really isn’t much of an issue.
CDT is as guilty of doing things like this. We have lots of features that the Platform (and JRE for that matter) didn’t provide that we know our users and adopters do so we built them. But don’t tell anyone else about them even though lots of them would
be useful to other stacks.
Which comes back to the web presence issue we were talking about. I don’t want a better CDT web site, I want a better Eclipse IDE web site. And, yes, we would have a section showing off the features for C++ developers but as we try to do in the UI, we
don’t need to mention the CDT project. That’s not where they start.
When you go to the IntelliJ site, you don’t see features organized by the teams that built them.
|
