From: "Jonas Fonseca" <jonas.fonseca@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Jakub Narebski" <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: Git User's Survey 2008 partial summary, part 3
Date: Mon, 8 Sep 2008 01:07:50 +0200 [thread overview]
Message-ID: <2c6b72b30809071607m69148ec0mc9d0925e24bb7b7e@mail.gmail.com> (raw)
In-Reply-To: <20080906051530.GB28035@spearce.org>
On Sat, Sep 6, 2008 at 07:15, Shawn O. Pearce <spearce@spearce.org> wrote:
> Actually, I'm rather excited by what's going on in the Git IDE
> space these days. The NetBeans plugin is seeing more activity,
> and since GSoC so has EGit. Both projects have been steadily
> picking up contributors. Quite a good thing.
One thing that I am wondering about is how to best integrate the
various git-specific traits. NetBeans already has several VCS plugins,
many of which are derived from the same code and have been built to
abide to the same UI design principles, and so naturally they have a
similar "feel" to them. It seems foolish to not try and respect this
when integrating git into the IDE space. Especially, to make it easier
for people to try out and switch to git.
One example is the question of how to enable users to work with the
index without adding too many obscure UI elements. NetBeans VCS
infrastructure and diff engine automatically annotates, which lines in
the editor has been changed, modified, or deleted, and allows users to
revert on a chunk level. While it seems very practical to extend the
annotation bar to allow changes to be staged (I am not sure if this is
even possible) it could end up cluttering a concept that many users
are already very familiar with.
I am curious what kind of considerations you have done on this topic
in your work on EGit.
--
Jonas Fonseca
next prev parent reply other threads:[~2008-09-07 23:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 14:07 Git User's Survey 2008 partial summary Jakub Narebski
2008-09-03 14:45 ` Shawn O. Pearce
2008-09-03 15:20 ` H.Merijn Brand
2008-09-03 16:25 ` Felipe Contreras
2008-09-04 2:43 ` David Aguilar
2008-09-05 22:17 ` Jan Hudec
2008-09-06 4:17 ` David Aguilar
2008-09-03 15:00 ` David Brown
2008-09-03 15:41 ` Scott Chacon
2008-09-03 16:00 ` Jakub Narebski
2008-09-04 13:23 ` Git User's Survey 2008 partial summary, part 2 Jakub Narebski
2008-09-06 2:22 ` Git User's Survey 2008 partial summary, part 3 Jakub Narebski
2008-09-06 5:15 ` Shawn O. Pearce
2008-09-06 8:27 ` Andreas Ericsson
2008-09-07 23:07 ` Jonas Fonseca [this message]
2008-09-07 23:47 ` Shawn O. Pearce
2008-09-06 22:17 ` Git User's Survey 2008 partial summary, part 4 - how do we use Git Jakub Narebski
2008-09-07 8:31 ` Andreas Ericsson
2008-09-07 8:44 ` Jakub Narebski
2008-09-11 20:14 ` Git User's Survey 2008 partial summary, part 5 - other SCM Jakub Narebski
2008-09-11 21:03 ` Anatol Pomozov
[not found] ` <48C98F92.40903@workspacewhiz.com>
2008-09-11 22:05 ` Jakub Narebski
2008-09-11 21:54 ` Jeff King
2008-09-11 22:51 ` david
2008-09-12 10:44 ` Jakub Narebski
2008-09-13 21:11 ` david
2008-09-13 22:03 ` Jakub Narebski
2008-09-15 11:51 ` Mark Brown
2008-09-14 10:45 ` Nguyen Thai Ngoc Duy
2008-09-14 13:32 ` Jakub Narebski
2008-09-15 3:39 ` david
2008-09-15 7:00 ` Andreas Ericsson
2008-09-16 17:12 ` 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=2c6b72b30809071607m69148ec0mc9d0925e24bb7b7e@mail.gmail.com \
--to=jonas.fonseca@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=spearce@spearce.org \
/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).