Bugzilla – Full Text Bug Listing
| Summary: | [Xtend] Add key binding to navigate between the xtend file and the generated java file | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Steve Ash <stevemash> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | sebastian.zarnekow, sven.efftinge |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Steve Ash
IF you hover+CTRL over a Java type name (being it in the declaration or in a reference) which was generated from Xtend, you should be able to open up the Xtend source. We are working on making the navigation between Java and Xtend more seamless. But this particular problem is solved. Is there a way to navigate to the generated source code? Thanks Sven- In particular I'm thinking about the following user scenarios: 1- if I'm in the xtend editor and I want to see what the generated java code looks like, it would be handy to have a key combo or "navigate to" to get me there. Although, maybe this isn't particularly useful after the first week or so of using xtend. 2- if I paste a stack trace into the stack trace viewer and click a file:line then it takes me to the java source. It would be nice to have a key combo or "navigate to" to immediately take me to the corresponding xtend source file. 3- if I am in a java source file in the java editor and I use an xtend class: if I hit F3 on the xtend class it takes me to the java source. Ideally it would take me to the xtend class. From your comment were you saying that one of these was already implemented? I'm using the stable release, not a nightly -- in case thats where the change is. (In reply to comment #3) > Thanks Sven- > > In particular I'm thinking about the following user scenarios: > 1- if I'm in the xtend editor and I want to see what the generated java code > looks like, it would be handy to have a key combo or "navigate to" to get me > there. Although, maybe this isn't particularly useful after the first week or > so of using xtend. I see, we could have that. I'm not totally convinced that it is a good idea to give the generated code that much attraction. > > 2- if I paste a stack trace into the stack trace viewer and click a file:line > then it takes me to the java source. It would be nice to have a key combo or > "navigate to" to immediately take me to the corresponding xtend source file. So far JDT doesn't provide any means to hook in when it tries to open a Java element in an editor. I already filed a feature enhancement against JDT and we will definitely do something about it. > > 3- if I am in a java source file in the java editor and I use an xtend class: > if I hit F3 on the xtend class it takes me to the java source. Ideally it > would take me to the xtend class. > > From your comment were you saying that one of these was already implemented? > I'm using the stable release, not a nightly -- in case thats where the change is No it's i the release. But it's not the primary go to declaration. So F3 doesn't work. But if you use hover and CTRL oner the type's name it should allow you to navigate to the Xtend code. Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |