Thanks, everybody, for your input! As usual, no perfect solution :)
What I would like to propose is that I prototype the approach as I first
documented it, see how it goes. I will play with it myself and see how
it is. I can check this in, we can work with it for a while, and then
revisit, potentially refining using some mechanism like Kathey suggested.
My reasons for this are two-fold:
- it's easier to implement
- it's in general a simpler model and less error-prone
In other words, it's an incremental step, but at least it will be a
start, and maybe it will work just fine.
Thanks,
David
Kathey Marsden wrote:
Bryan Pendleton wrote:
IDE productivity is key.
This is why I put my proposal on the table. Here are the two
different work flows to edit a file in Eclipse
1) IDE takes you to the real file (code generated only in jar build)
Put my cursor on DavidUtil.aMethod() call
Press [F3] (takes me to DavidUtil)
Make my edits
2)IDE takes you to a generated file (code generated for classes build)
Put my cursor on DavidUtil.aMethod() call
Press [F3] (takes me to generated David Util)
<ctrl> [SHIFT] [T] Type DavidUtil
Arrow Down to the real class I want
[ENTER]
<ctrl> [o] (to bring up method list)
arrow down to aMethod()
[ENTER]
Remember what I wanted to change
Make my edits.
These are optimized for keystrokes. Anyone using the mouse is in for a
rougher time of it.
Kathey
