New module proposal, userpoints history view

I worked in a module time ago (since charts is available) to provide a graphical view for the user point 'history'.

In my setup (a gaming site) having such a view like this (the attached image) would provide more sense of "award" for each point a user gets as they all requested. Finally I did a quick integration with chart and userpoints to just provide the graphical evolution of the user's points.

Now, I would like to share the module, but before start creating new problematic issues I guess the best idea would be to test your own impressions about what to do with something like this. I'll tell you about the inners of the module and then you can consider some tweaking or features to be included for the first public version.

The module does not require any table, it just queries the transactions table using an interval value for the horizontal separator, it can be month/week/day/hour and adds points earned and removes points expired in the interval. The final array is used to build the chart for the user with the same settings. It's quite simple in concept and in code. The most difficult part is to make it themeable IMHO. An administration interface let's you define the kind of interval to be shown (last week, last month, last year, all user lifetime). The local task menu is created automatically (optional feature controlled by a checkbox in the admin interface), to create shortcuts for the view, but it's a menu handler as user/%user/history/%categories what handles the whole information (you may have a view for 2 or more categories using the , separator).

Default views are the same as defined in the filter for userpoints: "all points" (each one has it's own line in the chart), the special "uncategorized" case, and each category. All should obey the interval behaviour defined in the administration settings.

As in my site I'm not removing old points from DB, I can have the 'all user lifetime' view easily, but if the txn are to be removed from the database, a table should be create to keep the value of the total points up to the first entry remaining in the txn table, to start the total SUM with that value.

So, What do you think about it?