From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2009, #02; Mon, 07)
Date: Tue, 08 Sep 2009 06:10:28 -0700 (PDT) [thread overview]
Message-ID: <m3k509vaym.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vtyzexnhm.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> * jn/gitweb-show-size (2009-09-07) 1 commit
> - gitweb: Add 'show-sizes' feature to show blob sizes in tree view
This is an RFC, because of a) feature naming, and b) tests.
It does work correctly, though.
> * jn/gitweb-blame (2009-09-01) 5 commits
> - gitweb: Minify gitweb.js if JSMIN is defined
> - gitweb: Create links leading to 'blame_incremental' using JavaScript
> (merged to 'next' on 2009-09-07 at 3622199)
I plan on reverting the order of those two patches, as JSMIN patch is
more ready than 'blame_incremental' linking.
With JSMIN there is perhaps question of documenting it, and whether
git-instaweb.sh should use minified JavaScript or not (curently it
does not). With 'blame_incremental' linking there are quite a few
issues:
1. When to do JavaScript detection
a. on load (current solution)
b. on click (via event handler)
2. How to invoke actions requiring JavaScript
a. add 'js=1' parameter (perhaps limiting URLs, as not to
add it e.g. to http://git-scm.com/ $home_link)
b. rewrite action parameter, e.g. from 'blame' to
'blame_incremental' (troubles with path_info URLs)
c. use cookies
Current solution works, but I think is suboptimal.
> + gitweb: Colorize 'blame_incremental' view during processing
> + gitweb: Incremental blame (using JavaScript)
> + gitweb: Add optional "time to generate page" info in footer
>
> Ajax-y blame.
I'd very much like for others to check if it works with other browsers
(Internet Explorer 6, 7, 8; Opera 9, 10; Safari; Firefox 2, 3, 3.5)
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-09-08 13:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 0:56 What's cooking in git.git (Sep 2009, #02; Mon, 07) Junio C Hamano
2009-09-08 6:31 ` Nanako Shiraishi
2009-09-08 6:48 ` Junio C Hamano
2009-09-08 13:10 ` Jakub Narebski [this message]
2009-09-08 13:17 ` Sverre Rabbelier
2009-09-09 11:59 ` jk/1.7.0-status, was: " Jeff King
2009-09-10 16:18 ` Daniel Barkalow
2009-09-10 16:53 ` Johannes Schindelin
2009-09-10 17:55 ` Daniel Barkalow
2009-09-10 18:41 ` Junio C Hamano
2009-09-11 0:09 ` scissors definition and documentation Nicolas Sebrecht
2009-09-11 0:09 ` [PATCH 1/2] mailinfo: add '--scissors' to usage message Nicolas Sebrecht
2009-09-11 0:09 ` [PATCH 2/2] add documentation for mailinfo.scissors and '--no-scissors' Nicolas Sebrecht
2009-09-11 0:29 ` [PATCH v2] " Nicolas Sebrecht
2009-09-11 7:19 ` Junio C Hamano
2009-09-11 13:41 ` [PATCH v2] " Nicolas Sebrecht
2009-09-11 18:53 ` Junio C Hamano
2009-09-11 20:08 ` Nicolas Sebrecht
2009-09-11 21:00 ` Junio C Hamano
2009-09-12 3:03 ` Nicolas Sebrecht
[not found] ` <682ef47420f36d8c53e42981370d377b621d7b86.1252698215.git.nicolas.s.dev@gmx.fr>
2009-09-11 19:50 ` [PATCH v3 2/2] " Nicolas Sebrecht
2009-09-12 0:33 ` What's cooking in git.git (Sep 2009, #02; Mon, 07) Junio C Hamano
2009-09-12 4:38 ` Junio C Hamano
2009-09-12 11:46 ` Sverre Rabbelier
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=m3k509vaym.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).