On 09/29/2016 04:32 PM, Doug Schaefer wrote:
Thanks Mikhail! I can’t wait to try it (I’m stuck on Neon for a while).
As you were one of those missing it to adopt project explorer, it would be nice if you could find some time to try it before the Oxygen release to check whether the implementation solves your issues.
Of course. By a while, I mean a few weeks, probably after Neon.2. I have some pretty big changes to CDT and the Launch Bar I’m working on until then (and an Neon based commercial release).
But to your original question, what other features prevent users from migrating from the Package Explorer to the Project Explorer and the promise of a single Code perspective? There was discussion earlier somewhere that I can’t remember. Is there a bug
open for it maybe?
BTW, this would be a proposed UX guideline. That language plug-ins must share common Code and Debug perspectives. That would greatly simplify workflows for users that use multiple languages. For example, my cloud projects based on vert.x server and Angular
2 clients should not require me to change perspectives when working on the different Java and Typescript files that I have in the same project.
Doug.