From: chaitanyaa nalla <nallachaitu@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: GSoC idea: adding JavaScript library / framework in gitweb
Date: Sun, 25 Mar 2012 00:27:08 +0530 [thread overview]
Message-ID: <CACeyogenMu2HO9iDBGgGmg0QvtdxY5cKcuGEeMAwckJsEi9RbQ@mail.gmail.com> (raw)
In-Reply-To: <201203241949.04956.jnareb@gmail.com>
that's great ,thanks for your time and concern.I will carefully
consider each and every suggestion and approach you if i need any
clarification .
On Sun, Mar 25, 2012 at 12:19 AM, Jakub Narebski <jnareb@gmail.com> wrote:
> On Sat, 24 Mar 2012, chaitanyaa nalla wrote:
>
>> Dear Jakub ,
>>
>> could you please suggest any other ideas or features so that i can
>> think upon them and come up with further good ideas.
>
> One idea for additional feature that I have already mentioned, and which
> I have put on https://github.com/peff/git/wiki/SoC-2012-Ideas is
> client-side sorting of tables, e.g. of list of all projects, a la
> jQuery / MediaWiki (Wikipedia) "sorttable".
>
> Another would be using deferreds or queues for interactive blame, so
> that repainting (editing DOM) happens asynchronously to avoid locking
> up browser, like in
> http://www.nczonline.net/blog/2009/08/11/timed-array-processing-in-javascript/
>
> 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.
>
>
> Yet another would be support for graphical representation of history in
> 'log', 'shortlog' and 'history' views e.g. using Raphael.js
>
> Perhaps it would be possible to employ some JavaScript syntax highlighter
> to pretty-print contents of 'blob' view.
>
>
> Hope That Helps.
>
>
> P.S. You can see gitweb at work here:
>
> http://git.kernel.org/?p=git/git.git
> http://repo.or.cz/w/git.git
> --
> Jakub Narebski
> Poland
next prev parent reply other threads:[~2012-03-24 18:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 6:32 gsoc idea adding javascript library / framework in gitweb chaitanyaa nalla
2012-03-24 13:17 ` GSoC idea: adding JavaScript " Jakub Narebski
2012-03-24 16:09 ` chaitanyaa nalla
2012-03-24 16:48 ` chaitanyaa nalla
2012-03-24 18:49 ` Jakub Narebski
2012-03-24 18:57 ` chaitanyaa nalla [this message]
2012-03-25 8:31 ` chaitanyaa nalla
2012-03-25 17:55 ` Jakub Narebski
2012-03-25 18:08 ` chaitanyaa nalla
2012-03-26 0:44 ` Jakub Narebski
[not found] ` <CACeyogdhChrGe-k+VLkAzq1F9U1TFYsCN5Kc_u7jAwRhaz+fJQ@mail.gmail.com>
2012-03-27 14:55 ` chaitanyaa nalla
2012-03-27 19:14 ` Jakub Narebski
2012-03-27 20:35 ` chaitanyaa nalla
2012-03-28 10:38 ` Jakub Narebski
2012-03-28 18:05 ` chaitanyaa nalla
2012-03-29 9:14 ` Jakub Narebski
2012-03-29 18:37 ` chaitanyaa nalla
2012-03-30 13:29 ` Jakub Narebski
2012-04-01 9:47 ` chaitanya nalla
[not found] ` <CACeyogeh7SSfx5NPFSt=gDdUzrUj0zxQKh84MDA-dW2e7UNGcw@mail.gmail.com>
2012-03-30 12:56 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACeyogenMu2HO9iDBGgGmg0QvtdxY5cKcuGEeMAwckJsEi9RbQ@mail.gmail.com \
--to=nallachaitu@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).