I'll be there! and I'm bringing a friend. (Sorry for the delayed reply... I broke my mail server and it is still catching up...)<br><br>--Brock<br><br><div><span class="gmail_quote">On 3/14/07, <b class="gmail_sendername">
Scott Walters</b> <<a href="mailto:scott@illogics.org">scott@illogics.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Now that ya'll know at least one thing you're getting out of the deal,<br>who thinks they can make it? We don't need to reserve seating or<br>anything, but more people are likely to come if they see that others
<br>are going to be there.<br><br>-scott<br><br>On 0, Scott Walters <<a href="mailto:scott@illogics.org">scott@illogics.org</a>> wrote:<br>> > * Visualizing code with graphviz<br>><br>> I assume this is a reference to my recent addition to the ideas list on the
<br>> Wiki. Very well then. Even Brock is allowed to make requests.<br>><br>> Let me give some more background and try to sell the presentation a bit<br>> better. A certain large shopping comparison site [1] recruited me recently
<br>> and I've been trying to come up to speed on the code. The codebase is about<br>> 200,000 lines of code that's been worked on by many people over several years.<br>> While trying to make heads or tails of it, I decided I needed something
<br>> like the what the Linux community did with the Linux Kernel Graphing<br>> Project:<br>> <a href="http://www.visualcomplexity.com/vc/project_details.cfm?id=261&index=261&domain=">http://www.visualcomplexity.com/vc/project_details.cfm?id=261&index=261&domain=
</a><br>><br>> The idea is to plot out, on paper, which method calls which other methods, thus<br>> creating a visual "map" of the code structure. The presentation will be<br>> about how I collected the data inside of mod_perl (I had help, using work
<br>> he'd already done), processed it, and turned it into a giant poster, spread<br>> across 30 printed pages.<br>><br>> Initially, I tried to plot on a method level resolution of which method calls<br>> each other method in the system. That turned out to be entirely too much
<br>> data. The result of the first poster attempt looked like a sewing machine<br>> exploded, sending thread everywhere in big knots and balls. The poster<br>> was half ink and half white with unreadable labels. The second version
<br>> was a lot less fun but a lot more readable.<br>><br>> My approach uses a similar approach to <a href="http://www.ida.liu.se/~vaden/cgdi/">http://www.ida.liu.se/~vaden/cgdi/</a><br>> where profiling data is collected, rather than the LKGP approach, where
<br>> a full static analysis is done (though that was my first approach).<br>><br>> I brought an unassembled print out of the 30 pages with me for the "class"<br>> to assemble if they wish ;)<br>>
<br>> These techniques should be useful to anyone confronted with a dauntingly<br>> large or complex codebase they have to work on.<br>><br>> -scott<br>><br>> Footnote 1: Name withheld on the 'net to disassociate them from any "this is
<br>> what really pissed me off at work today" posts I might make.<br>><br>><br>> On 0, Brock <<a href="mailto:awwaiid@thelackthereof.org">awwaiid@thelackthereof.org</a>> wrote:<br>> > We have a meeting tomorrow! We don't have a specific presentation at
<br>> > this point, but we do have several discussion topics:<br>> ><br>> > * mod_perl -- your experiences and a technical overview<br>> > * Visualizing code with graphviz<br>> > * Short scripts you can't live without (I'll show my music player wrapper)
<br>> > * Show off code you've been working on recently!<br>> ><br>> > See you there!<br>> ><br>> > --Brock<br>> ><br>> > On 2007.03.02.17.14, Brock wrote:<br>> > | Greetings Fellow Perl Addicts,
<br>> > |<br>> > | Inspired by Tony's good example (hosting a social meetup, which is<br>> > | taking place tomorrow (see his previous email for details)), and prodded<br>> > | by Scott and Jon, it seems to be about time to have a
Phoenix.PM<br>> > | meeting. We were up in Scottsdale last time, so I'm shooting for Tempe<br>> > | this time.<br>> > |<br>> > | Time: Wednesday 14 March 2007 7:00pm-9:00pm<br>> > | Location: Mill's End Cafe, Tempe, AZ
<br>> > | <a href="http://maps.google.com/maps?q=310+S+Mill+Ave+tempe,+az">http://maps.google.com/maps?q=310+S+Mill+Ave+tempe,+az</a><br>> > | North-West corner of Mill and 3rd (N of University Ave) in Tempe
<br>> > | Parking off of 3rd (free with validation)<br>> > | Topic: News in the Perl World (Brock)<br>> > | Level I topic: TBA<br>> > | Level II topic: TBA<br>> > | Other: Free wireless, bring your laptops!
<br>> > |<br>> > | I was thinking that a good level I topic (beginner/intermediate) would<br>> > | be closures (anonymous subroutines). But if that is too much another<br>> > | great one would be showing off that 10-line program you whipped together
<br>> > | in an hour that you can't live without (mine is my mp3 player). And<br>> > | there are all sorts of advanced topics... topic leader volunteers,<br>> > | unveil yourselves!<br>> > |<br>
> > | I'm also dragging in some fresh blood (Mike and maybe Brian from my<br>> > | work)... and I encourage y'all to do the same :)<br>> > |<br>> > | So lets hear those topic ideas, so I can then cross post this all over
<br>> > | the interweb.<br>> > |<br>> > | --Brock<br>> > |<br>> > _______________________________________________<br>> > Phoenix-pm mailing list<br>> > <a href="mailto:Phoenix-pm@pm.org">
Phoenix-pm@pm.org</a><br>> > <a href="http://mail.pm.org/mailman/listinfo/phoenix-pm">http://mail.pm.org/mailman/listinfo/phoenix-pm</a><br>_______________________________________________<br>Phoenix-pm mailing list<br>
<a href="mailto:Phoenix-pm@pm.org">Phoenix-pm@pm.org</a><br><a href="http://mail.pm.org/mailman/listinfo/phoenix-pm">http://mail.pm.org/mailman/listinfo/phoenix-pm</a><br></blockquote></div><br>