CLion 2016.2 roadmap
A week passed since we released CLion 2016.1 with so many great features and useful bugfixes. Thanks for your warm reception of this update and your great feedback!
Before we move forward, we’d like to thank all of you who evaluated CLion during the Early Access Program, provided feedback and suggestions, and submitted issues to our tracker. Your input was invaluable in making this release stable and feature-rich. Contribution of several evaluators deserves a special gift. We’re giving each of the following people a free 1-year subscription (to extend your current subscription or get a new one):
- Roman Popov (YouTrack handle: ripopov)
- Christian Hujer (YouTrack handle: cherriedquat)
- Dave Yost (YouTrack handle: daveyost)
- Jan Ekholm (YouTrack handle: chakie)
- 蓝星灿 (YouTrack handle: lanxingcan)
A personal message will be sent to each of you guys with details on how to obtain your license. (And just in case you do not get any email from us within a week, ping us here in the comments.)
We spent some time analyzing the current state of the product, the issues in our tracker, and your feedback and suggestions for the new release. This helped us formulate the following plan:
- Issues with GDB (timeouts, performance, other issues)
- Remote debug
- Project model (CMake)
- Ability to watch command output during CMake execution
- Ability to specify the build/generation output directory
- Support for
- C++ code insight performance improvements
- Formatter performance improvements
We’ll see what we are able to finish before 2016.2 release, while in general we plan to support:
- Doxygen comments highlighting
- Integration with quick documentation pop-up (documentation preview)
- Auto-completion for tags and names
- Navigation to code symbols
- Rename refactoring
Other refactorings like Change Signature with Doxygen comments update, code generation and inspections may also be implemented.
This plan also includes various bug fixes and improvements (especially for C++ language support and refactorings in C++ code), as well as some additional features, that may enter later.
You are probably wondering about project models and Makefiles. The short answer is – no, these will not make it into CLion 2016.2. We still haven’t finished critical work around CMake support, and we are still investigating various options to provide support for other build systems/project models, or even allow opening sources without any build system set inside CLion.
Stay tuned and don’t to miss the EAP launch!
Give CLion a try for free during the 30-day evaluation!
Your CLion Team
The Drive to Develop