Dear Jakub, I prepared a schedule for gsoc ,please take a look and suggest me in case if you feel some tasks couldn't be completed with in indicated time . Week 1 understanding how the whole gitweb and related server side scripts are implemented , their design philosophy , coding standards , documentation standards to maintain the best practise coding practices. Brainstorming sessions regarding which libraries to use on specific scenarios by keeping many criteria’s in mind and creating an abstract design on the additional features that have to be added. Week 2 Improving Javascript browser detection and incremental blame. Week 3 Improving UI of adjusting timezone by deciding which library / framework to use on UI. 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. Week 6 testing the code robustly on as many browsers as possible (with their versions) and documenting the code neatly . MidTerm Delivarables : Improving javascript browser detection, incremental blame,ui of adjusting timezone .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 design and implementation support for graphical representation of history in log ,shortlog and history using Raphael javascript library, adding UI to compare arbitrary commits in the page using commitdiff view similar to MediaWiki page history view and 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 characteristics . 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. Thanks in advance. yours sincerely, chaitanya nalla. On Wed, Mar 28, 2012 at 12:44 AM, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > On Tue, 27 Mar 2012, chaitanyaa nalla wrote: >> Jakub Narebski wrote: > >> > There was also some time ago a patch that added ability to mark a commit >> > to compare current commit to (using JavaScript and cookies), to have an >> > UI to compare arbitrary commits using 'commitdiff' view. Or something >> > similar to MediaWiki (Wikipedia) page history view. >> >> Hey jakub, >> >> Will that patch be included in future version, if it is the case can >> i consider implementing with some enhancements?? > > This idea is in my TODO list for gitweb, but I don't have specific plans > on when it would be implemented (if at all). > > P.S. Please leave only relevant part of cited (quoted) response. Thanks > in advance. > -- > Jakub Narebski > Poland -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html