[Librefm-discuss] Libre.fm GSoC Update 2011/06/10 - sephiap

[Mike Sheldon]

Hi all,

 Below is Matt's first weekly progress report on his GSoC project.
(Forwarded by me because the mailing list is apparently rejected e-mails
from a number of people

On Fri, 2011-06-10 at 23:12 +0100, address@hidden wrote:
> Dear libre.fm users,
> 
> 
> This email serves to keep the community updated with the progress of
> the GSoC project.
> 
> 
> Current Status
> 
> 
> jqPlot has been successfully implemented through the implementation of
> Graph objects which serve as wrappers for the existing Statistics
> class at the moment, this will be refactored to provide more intuitive
> encapsulation as defined below. A screenshot of the current state of
> the basic implementation may be viewed
> here: http://f.cl.ly/items/17050v0k1p1l0A3J3w2l/libre.png 
> 
> 
> As is evident, there are a number of things required before the new
> page goes live which include:
> 
> 
>       * Ensure all artist names are accessible links
>       * Ensure all track names are accessible links
>       * Increase spacing between graphs on page
>       * Alignment issues (text vs graph in Top Tracks & Top Artists,
>         x-axis dates)
>       * Interactivity or further information on scrobbles by day (make
>         date unambiguous) 
> Next Steps
> 
> 
> As this is a basic implementation of the jqPlot functionality, none of
> the dynamic features have yet been exposed, however the implementation
> of jqPlot developed will allow fairly straightforward mapping of the
> new functionality into the statistic pages, specifically considering
> the use of AJAX loading present in the jqPlot libraries. Where
> possible, I have tried to emulate the overall aesthetic of last.fm's
> statistics at this point, and will continue to do so unless guided
> otherwise by the community - by this I mean, the placement of
> statistic options (ref: 'Last 6 Months' etc on last.fm), however much
> of the proposed functionality is outside the scope of the default
> last.fm tools, so its influence will be very limited regardless.
> 
> 
> The above aesthetic and functional points will be rectified and
> submitted for merging this weekend, as well as noted refactoring
> should time permit. From this point, I will be focusing exclusively on
> the new internal API functionality to support dynamic query generation
> as originally proposed and would ask again for community feedback in
> determining what data is relevant to you, which data comparisons would
> be most useful? I'm always happy to hear feedback whilst developing
> the ideas.
> Getting In Contact
> 
> I am eager to get as much constructive feedback as possible, if you
> have any ideas / contributions / disagreements you may contact me
> using the following methods:
> 
> IRC: sephiap on Freenode
> libre.fm: sephiap
> identi.ca: sephiap
> email: address@hidden
> 
> Matt Pugh (sephiap)
> 
> 
> 
> 
> 
>