Ticket #1243 (new enhancement)
Enable developers to click on UI to find the addComponent call/line in source code
| Reported by: | Sami Ekblad | Owned by: | Jani Laakso |
|---|---|---|---|
| Priority: | major | Milestone: | IT Mill Sponsored Backlog |
| Component: | undefined | Version: | |
| Keywords: | debug source code find addcomponent | Cc: | |
| Known Issue description: | |||
| Hours estimate: | 14 | Deadline (dd.mm.yyyy): | |
| Known Issue version (since): | Known Issue title: | ||
| Hours done: | Depends to: | ||
| Affects documentation: | no | ||
| Known Issue workaround: | |||
| Affects release notes: | yes | Contract: | |
Description
To debug applications that have complex UI it is currently hard to find the Java source code that constructs it.
To help developers find the relevant source code line a generic debug feature into addComponent is suggested:
- Application debug mode
- Find out the code calling the addComponent function in a ComponentContainer?
- Add a button (or similar) to component/windget UI that developer can select it
- When selected, output the formatted src line into stdout, so that Eclipse creates an active link out of it
- Developers can then click the button and and the line in console output to find the code that added the component
Change History
Note: See
TracTickets for help on using
tickets.
