Re: GSoC idea: adding JavaScript library / framework in gitweb

Dear jakub,

I have changed schedule based on the good suggetions given by you. please look at it.

Before May 21st  interacting with the beloved community members and get familiarize with the code base. Week 1  Gaining a proper understanding regarding how various are implemented , their design philosophy , coding standards , documentation standards to maintain the best coding practices .Detailed discussions on which JavaScript library / framework to use for client-side scripting in gitweb (jQuery, MooTools, Dojo, YUI) based on several criteria.(as you mentioned , a short paragraph describing which framework to use is also added) Week 2  Transform existing code of JavaScript detection, adjusting timezones and from hand written JavaScript to using JavaScript library,improving their features wherever possible, incrementally and removing the mini-library in `gitweb/static/js/lib/` by proper design and analysis.

Week 3 transform the existing code of incremental blame and improving
its features wherever possible by proper design and analysis
Week 4 & 5 design and implementation of client side sorting of tables
and client side syntax highlighting of the blob view by handling how
git web splits the output into lines and providing line numbers.
There is also a question of integrating it with server-side source
highlighting (turning off JS-based if server side already does syntax
highlighting, and using
the same CSS).
Week 6  testing the code robustly on as many browsers as possible
(with their versions) and documenting the code neatly .If possible
automated testing will also be done using selenium web driver.
MidTerm Delivarables : Transform existing code of JavaScript
detection, adjusting timezones and from hand written JavaScript to
using JavaScript library,improving their features wherever possible,
incrementally  and removing the  mini-library in
`gitweb/static/js/lib/` by  proper design and analysis. Adding client
side sorting of tables and client side syntax highlighting of blob
view .
Week 7 & 8 Using deferrands or queues in the interactive blame to
avoid the editing of DOM which happens asynchronously to avoid
locking and automatic extending of clickable area for places where the
link is constrained to a single cell or of that type.
Week 9 & 10 & 11 adding user interface  to compare arbitrary commits
in the page using commitdiff view similar to MediaWiki page history
view . Creating a side by side diff from unified diff in javascript so
that switching between unified diff and side by side diff could be
handled on client side.
Week 12  documentation , writing a detail report , testing
exhaustively and checking whether the written code follows the best
coding practises and good design.
Note: considerable amount of time will be spent each week
concentrating on design for adding a new feature since its design
greatly affects many things.