I just got word of the available e4 Eclipse SDK test builds and thought I'd try out the CDT on it. The great news is that I had no build errors for the CDT base functionality (haven't tried our advanced debug views yet). And I was able to create a C++ project and build it. I had issues going into debug, but I am pretty happy on how far it has come.
There's still a lot missing, though, so there is much work ahead. And as I've feared the UI performance is quite bad, but there's a long way to go to clean these things up. I'll be keeping regular tabs on their progress and test as many of the CDT workflows as I can as the platform stabilizes.
Here's a teaser screenshot.
Doug, you beat me to it! I had the same screen up earlier today and planned to post it. :-)
ReplyDeletePat, please open a bug (and ideally, if possible, attach a patch). I would love to be able to control the tab widths through CSS. Right now, the SWT-level capability is missing but it wouldn't be too hard to do.
Brave man, building CDT on literally the very first successful build of the full Eclipse SDK on e4! It's great that you're trying things out so early, and that you had a clean build on the first try. We've certainly got a long way to go, but having people try out their stuff on top of it and report their experiences is a huge help.
ReplyDeleteI was totally expecting a huge failure, but was pleasantly surprised how much did work. Lots more to do, but great job so far!
ReplyDeleteIt might be interesting to see how much the new TabStyling does to the performance.
ReplyDeleteIs the CDT Indexer improved on e4?
ReplyDelete