Sounds good to me. I plan to keep on hacking on hackyApp_SpiderWeb to explore the area.
BTW, can I commit my additions to hackyCore_Report. Basically, its a new ChartView for SpiderWeb stuff? Once things settle down, I'd like to take a look at the DailyProjectData implementations. There are a couple of things that needs to be looked at. For example, - each instance manages their own collection of sensor data. I seen a couple of different implementations of the "snapshot/runtime" and aggregate internal data structures. Some times improvements and bug fixes don't make it to all implementations.. For example, DailyProjectCoverage contains a map based on runtime. DailyProjectFileMetric contains a map based on workspace, then runtime. In both cases, if I send data in a different "way", the data structure breaks down. - If I write a new sensor, that sends a couple new pMap attributes should I have to write a new DailyProjectData implementation or alter the current implementation to be able to use that information? - how does DailyProjectData handle or analyze data from multiple sensors? For example, I can send PMD, FindBugs, and Checkstyle data to Hackystat as CodeIssue. Should I have a single DailyProjectCodeIssue that is able to provide information on all three data sources? Or should it combine all the data? Or should there be DailyProjectCodeIssuePmd, etc? The same idea goes for FileMetric. SCLC provides lines of code. But, where should the OO metrics from DependencyFinder go? Anyway, I see a lot of necessary potential improvements in the DailyProjectData layer. thanks, aaron ----- Original Message ----- From: Philip Johnson <[EMAIL PROTECTED]> Date: Monday, November 21, 2005 9:24 am Subject: [HACKYSTAT-DEV-L] XRadar and hackyCore_Kernel > Hi Aaron, > > Just took a second look at this. It would be great to eventually > integrate something > like XRadar into our daily build process. And the animated Kiviat > chart stuff is a great > idea! It will be quite interesting to compare/contrast this kind > of analysis with > telemetry (I think there will be pros and cons to each approach; > they are complementary, > not competitive.) > > In terms of Hackystat analyses, one of the things I want to move > aggressively toward once > 7.0 is out is to eliminate the last vestiges of Java-orientation > from our standard > analyses. There are several parts to this: (a) make Workspace Maps > optional, not > required, for things like Unit Tests, (b) make SCLC the standard > size counting mechanism, > and count multiple language types (.java, .el, .cc, .html, .xml, > etc.) and (c) update > our standard analyses (DailyProjectData, Reduction Functions) to be > both > _language-neutral_ and _multi-language aware_. By "language > neutral", I mean that our > system does not prefer any particular language over any other. By > "multi-language > aware", I mean that all of our analyses are designed to operate in > a context of a system > that is written in several different languages. > > Once all of that is in place, then I would like to see us look at > XRadar from the > perspective of what kinds of useful analyses they are doing that we > could support in a > language-neutral and multi-language aware mode. > > Cheers, > Philip > > --On Thursday, November 17, 2005 11:52 PM -1000 Aaron Kagawa > <[EMAIL PROTECTED]> wrote: > > > Hey Guys, > > > > I found one of the coolest open source tools ever! Its called XRadar > > (http://xradar.sourceforge.net/). Actually, my friend at work > found it. > > > > "The XRadar is an open extensible code report tool currently > supporting all Java based > > systems. The batch-processing framework produces HTML/SVG reports > of the systems > > current state and the development over time - all presented in > sexy tables and graphs. > > It gets results from several brilliant open source projects and a > couple of in house > > grown projects and presents the results as massive unified > html/svg reports. The > > architecture is based on java, xml and xsl." > > > > I ended up integrating XRadar with hackyCore_Kernel. A task that > took a while :) .. > > Anyway, the result was well worth the effort! > > > > ------------------------------------------------- > > Check out this XRadar report of hackyCore_Kernel > > http://csdl.ics.hawaii.edu/~kagawaa/xradar/docs/ > > > > You need to have SVG support in your web browser. The only > plugin I could find is > > http://www.adobe.com/svg/main.html , I couldn't find one for > FireFox. Anyway, install > > that SFG Viewer and use IE for once. > > > > Check out some really cool reports: > > - click on the packages for package overview reports (ie, > > org.hackystat.core.kernel.admin) > > - click on the classes for class overview reports (ie, Alert, > AnalysisInvocation)> > > ------------------------------------------------- > > Check out : > http://xradar.sourceforge.net/reports/dynamics/index.html> > > Isn't this telemetry? Haha cool! BUT! we can do better, see below. > > > > ------------------------------------------------- > > Everything is not perfect yet: > > - missing module metrics > > 1) see http://xradar.sourceforge.net/reports/release4/index.html > > 2) click on "A module" in the top left corner under subsystems. > > 3) scroll down. > > 4) notice the metric values > > 5) see http://csdl.ics.hawaii.edu/~kagawaa/xradar/docs/ > > 6) do repeat steps 2-4, except click on "admin module" > > 7) notice the missing metric values > > > > - i don't really understand the concept of the modules. and i > guess i didn't configure > > it correctly, notice that the modules have all the same Chart! oh > well....> - no clue on how to run this on more that one module (ie. > hackyCore_Installer,> hackyCore_Common, etc). > > - no clue on how to extend XRadar to use Emma coverage values, > Locc, etc. > > > > ------------------------------------------------- > > Next Steps: > > - figure out the above problems > > - basically, the current functionality can go into the V7 build > process already. but, > > only for hackyCore_Kernel until i figure out how to run it on the > whole system. > > > > > > ------------------------------------------------- > > Kiviat Charts in Hackystat! > > I was thinking that these Charts (apparently called Kiviat Charts, > > http://www.soft.com/Products/Screen/kiviat.html) would be really > cool in Hackystat. > > Instead of using this XRadar tool, Hackystat could be generating > these. The problem > > with XRadar is that the charts are more-or-less static. And, I > have to run all the > > generation tools (ie, checkstyle, pmd, etc) each time, which > maybe acceptable for a > > daily build or something. But, the problem is that they need a > snapshot of the code to > > be able to see a chart from a month ago. In Hackystat these > charts can be created > > dynamically using our stored metrics! Also, if we wanted to get > really crazy we could > > animate these SVG charts to "play back" the development process!! > WOW!> > > Can JFreeChart generate Kiviat Charts? > > Answered my own question: > > > http://www.jfree.org/phpBB2/viewtopic.php?p=36352&highlight=&sid=5fce0cebaef005e0630373> > b81190c022#36352 > > > > Many research questions arise... How does Animated Hackystat > Kiviat Charts compare to > > Telemetry? > > > > > > By the way, does this look like a promising tool to use? haha...YES! > > Oh, and here is the ant execution of xradar in hackyCore_Build > > http://csdl.ics.hawaii.edu/~kagawaa/xradar/docs/commandprompt- > xradar.txt> > > thanks, aaron >
