Project Overviewer widget

[Fei]

I think we need a post dedicated to this widget.

So right now I have been trying to work on to get the SVN directories
using HttpUnit, and hook that up with the HackyStat commit sensor
data, so we can relate the file with who is the last editor for each
file. I am able to get the commit data(w/ owner, resource, and
modified time) now, and print the SVN directories as plain text. I'm
thinking to just work with plain text right now since we don't really
know how to do those folder-tree stuff in wicket yet.

I will just commit the code right now, but it's really messy and have
no comment at the moment. But I think you should at least get an idea
what I am trying to do there.

[Fei]

I've been playing around of displaying the directory tree, and it
seems like it takes up a lot more space than I expected. So I'm
thinking to switch the "sidebar" and "content" block, so the tree can
have more space for displaying. (and I tried half/half, it seems still
not enough) Do you think you will have enough room for the clock and
checklist stuff?

[Nathan Britton]

I was planning on putting the clock on top and the checklist where our filler info is.  So I guess it depends on where the tree goes.

--
Nathan Britton

The only impossible task is to find an impossible task.

[Jianfei Liao]

After actually implementing the switch from svn commit data to DevEvent data, I ran into the following problems:

 

1. the data is independent in terms of owner, unlike we only care about the last committed owner for commit data, we want to know the different owner for a same data resource. that being say, if we have 2 developers, we have to match the data twice, if 3 developers, match 3 times, and so on. The way I'm thinking to match the data right now is loop thru the files and compare it with the data resouce, which also contains the file name. It seems to me this is very non-efficient.

 

2. sensor data is "instant", because we can only get the timestamp of when it is modified. if we want to know how long for a developer has been working on a particular file, we need a way to figure out how long the sensor data has been sent for a same file (or resource) continuously.

 

3. the tree we can display right now is based on the svn repository on the google hosting site. in other words, if people are working on files that has not been submit yet, their effort will not be shown (at least in the way we do it, although the sensor data will collect those info as well). maybe we need a better and faster way of constructing the file directories of the project, instead of rely on httpunit and the google hosting site. well, after all, is the directories tree even a good way of showing the project structure?

 

these are the problems i have right now, and they don't seem like easy problems that can be solved over night.