Reverse Engineering

[lester]

The Reverse Engineering feature is very useful for learning about code that already been developed. However I find this feature difficult to use and very slow. I would suggest the following

- Starting to reverse engineer should as simple as just pointing to a root directory(source or class) and start.
- The reverse engineering should quikly import all the files and present the user with the source tree.
- More elaborate process should done in background.
- There should be check box to select "Continue on Error" so that if the user does not have to sit and watch a long import process.

[Eve]

Your first suggestion is already implemented.  (Although the dialog allows for a few more options than that)

Look at Project | Source Code Engineering | Import Source Directory.

I'm curious, what kind of source tree are you suggesting that EA should show the user?

Simon

[lester]

Thanks for the reply. I was able to follow your instructions. The only problem I had was that my project source code was in P:\tiger\.. which got moved over to S:\tiger\... Even though I used reverse engineer with the new root, some how EA remembered the old source tree and always refered to it. Hence I had to delete the the source code in the Project Views->Views->com... Then reverse engineer again. After this it worked correctly.

I found the reverse engineer process to be too slow. Moreover if it encounters a problem, it stops with a dialog box requiring user inputs. Instead use a check box "Proceed on Error". Use a log file to report and indicate to the user of any errors encountered.

The source tree that I was refering to is already in place under Project Views->Views->com....

[Eve]

You can use EA's local paths options to handling changing the path of source code.  There are a few places this has been mentioned on the forum, so I'd suggest doing a search for them.

Simon