git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git User's Survey 2008 partial summary, part 3

From
Shawn O. Pearce <spearce@spearce.org>
Date
Sep 7, 2008, 23:47 UTC
Message-ID
<20080907234718.GC15460@spearce.org>
In-Reply-To
<2c6b72b30809071607m69148ec0mc9d0925e24bb7b7e@mail.gmail.com>
Jonas Fonseca <jonas.fonseca@gmail.com> wrote:
Show 7 quoted lines
> 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.

Yea, that's a big concern for any IDE implementor. Many of the Eclipse team providers (if not all of them?) have derived from the CVS team provider that comes as part of the base platform. So they often share the same look-and-feel. But I think Eclipse defines less of a common VCS UI than what you are implying NetBeans does.

In Eclipse I think it is more common to define VCS custom views
(little windows/toolbars) and let the user turn on/off each view
as they see fit.
 
Show 8 quoted lines
> 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.

Yea, extending the annotation bar to show the index may actually be useful quite useful. If its only 15 pixels of horizontal width lost that's actually worthwhile. I think an older version of EGit had something like this until I broke it. I can't remember.

> I am curious what kind of considerations you have done on this topic
> in your work on EGit.

We've mostly ignored it. I haven't put a lot of thought into it because I have been focused on getting a solid JGit implementation in place.

I do know that I really miss having an overview of what is essentially the left side of git-gui; the staged and unstaged (but modified) file lists. The resource decorator is nice, but it doesn't quite give the same flat-tree overview.

-- 
Shawn.
Previous: Jonas FonsecaNext: Jakub Narebski
Message 16 of 33 in “Git User's Survey 2008 partial summary”
  1. Jakub NarebskiSep 3, 2008
  2. Shawn O. PearceSep 3, 2008
  3. H.Merijn BrandSep 3, 2008
  4. Felipe ContrerasSep 3, 2008
  5. David AguilarSep 4, 2008
  6. Jan HudecSep 5, 2008
  7. David AguilarSep 6, 2008
  8. David BrownSep 3, 2008
  9. Scott ChaconSep 3, 2008
  10. Jakub NarebskiSep 3, 2008
  11. Jakub NarebskiSep 4, 2008
  12. Git User's Survey 2008 partial summary, part 3Jakub Narebski, Sep 6, 2008
  13. Shawn O. PearceSep 6, 2008
  14. Andreas EricssonSep 6, 2008
  15. Jonas FonsecaSep 7, 2008
  16. Shawn O. PearceSep 7, 2008
  17. Git User's Survey 2008 partial summary, part 4 - how do we use GitJakub Narebski, Sep 6, 2008
  18. Andreas EricssonSep 7, 2008
  19. Jakub NarebskiSep 7, 2008
  20. Git User's Survey 2008 partial summary, part 5 - other SCMJakub Narebski, Sep 11, 2008
  21. Anatol PomozovSep 11, 2008
  22. Jeff KingSep 11, 2008
  23. david@lang.hmSep 11, 2008
  24. Jakub NarebskiSep 12, 2008
  25. david@lang.hmSep 13, 2008
  26. Jakub NarebskiSep 13, 2008
  27. Mark BrownSep 15, 2008
  28. Nguyen Thai Ngoc DuySep 14, 2008
  29. Jakub NarebskiSep 14, 2008
  30. david@lang.hmSep 15, 2008
  31. Andreas EricssonSep 15, 2008
  32. Jakub NarebskiSep 16, 2008
  33. Jakub NarebskiSep 11, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.