Hi John, Well, honestly, I was going to cheat. ;-) I'm planning on just regex'ing the files, grabbing the namespaces, classes, and delegates (to start out with).
Then build a treeview, and post it on www.123aspx.com (so when I move from computer to computer, I have it available). I figured some other people might also be interested in it, as I'm finding it invaluable, and can't believe I didn't take time to look at it before. Then, if new src is ever released, I'll just re-grep the files. Thoughts? Comments? Smart Remarks? ;-) Cheers, Dave ----- Original Message ----- From: "John Norwood" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 15, 2002 12:53 PM Subject: Re: [DOTNET-ROTOR] docs >I just downloaded rotor, and I was expecting some type of browse utility, >to browse the namespaces and see the code for the type of class. Sounds like a cool utility. Have you thought about how you would implement it? I considered something like this when I created the process to generate the reference docs but never had the time to explore it. Of course this would only work with the managed classes, the unmanaged code would not yield easily to any automated classification process. Most of the class library implementation follows the convention that the file name is the class name. Here at MS we put an index server catalog on top of our enlistment on a Windows machine. There is a DOxygen generated index over the source at http://dotnet.di.unipi.it/SharedSourceCli.aspx. However, it is currently indexed over the beta refresh and not the 1.0 release. John This posting is provided "AS IS" with no warranties, and confers no rights.
