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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 27, 2012 at 8:23 PM, chaitanyaa nalla <nallachaitu@xxxxxxxxx> 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??
>
>
>
> On Sun, Mar 25, 2012 at 11:25 PM, Jakub Narebski <jnareb@xxxxxxxxx> wrote:
>> On Sun, 25 Mar 2012, chaitanyaa nalla wrote:
>>
>>> Dear Jakub,
>>>
>>> if we handle the sorting of the tables on the client side itself,
>>> will that be a  load on the browser?
>>
>> Well, if it turns out to be too heavy a load, we can use the same trick
>> of "timed array processing":
>>
>>  http://www.nczonline.net/blog/2009/08/11/timed-array-processing-in-javascript/
>>
>> See for example this page to see sorttable in action:
>>
>>  http://en.wikipedia.org/wiki/Comparison_of_open_source_software_hosting_facilities
>>
>>> Other ideas which I have in mind are
>>>
>>> 1. Highligting matched portions of project name while searching the
>>>    project name, even more intuitively
>>
>> You probably couldn't have known that match highlighting in project
>> search is done on server side by gitweb.cgi since commit 6759f95
>> (Merge branch 'jn/gitweb-hilite-regions', 2012-03-04):
>>
>>  gitweb: Highlight matched part of shortened project description
>>  gitweb: Highlight matched part of project description when searching projects
>>  gitweb: Highlight matched part of project name when searching projects
>>
>> It is not used by either git.kernel.org or repo.or.cz because it is
>> too fresh (it is to be in yet to be released v1.7.10).
>>
>>> 2. project pagination.
>>
>> Is there any sense in pagination on client side?  Unless you turn it into
>> lazy loading / loading on demand Ajax-y pagination...
>>
>>
>> Yet another idea is to implement creating side-by-side diff from unified
>> diff in JavaScript, so that swicthing between unified and side-by-side
>> diff view could be done entirely client-side, without hitting the server.
>>
>>
>> Note however that I think that it wouldn't be possible in time given to
>> implement all those ideas.  You need to select those of them that you
>> will put in project application.
>>
>> --
>> 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


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]