{"thread":{"id":"3411","subject":"Ideas for qgit","startedAt":"2006-02-21T01:16:20Z","lastAt":"2006-02-21T01:16:20Z","messageCount":1,"participants":["Pavel Roskin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"16486","messageId":"1140484580.5282.54.camel@dv","threadId":"3411","inReplyTo":null,"subject":"Ideas for qgit","fromName":"Pavel Roskin","fromEmail":"proski@gnu.org","sentAt":"2006-02-21T01:16:20Z","receivedAt":"2006-02-21T01:16:20Z","isPatch":false,"sender":{"key":"proski@gnu.org","avatar":null},"body":"Hello, Marco!\n\nMany thanks for releasing qgit 1.1!  Here are things I'd like to be\nfixed in the next version.\n\nThe pop-up menu on revisions gets duplicate entries for tags after using\nthe file viewer (try qgit on the qgit repository).  This is a pure bug\nthat may merit a minor release (1.1.1 perhaps).\n\nTags should be in a submenu.  There are too many of them in some\nprojects.  Maybe there should be a limit of e.g. 10 tags, and the \"more\ntags\" entry that would invoke a dialog for searching tags (and possibly\nother things).\n\nIf all branches are loaded, it would be nice to be able to switch\nbetween branches in a similar way.\n\nThe \"check working dir\" feature picks up files unknown to git, such as\neditor backups and diff files.  It is very rare that a commit only has\nadded files but no files are modified.  Maybe I need to learn a habit of\nadding any file I'm not going to commit to .gitignore, but as it stands\nnow, this feature of qgit seems too obtrusive to me.  Neither \"cg-diff\"\nnot \"stg diff\" will pick untracked files, and it's not even an option\nfor either of them.\n\nCurrent StGIT creates entries for all patches under .git/refs/patches,\nwhich makes all corresponding entries purple.  I think qgit should\nspecifically recognize entries under .git/refs/patches\nand .git/refs/bases and use other ways to highlight them.  At very\nleast, .git/refs/patches should be ignored.  More elaborate approach\nwould be to draw applied StGIT patches differently, e.g. as pluses or\nhollow circles.\n\nqgit doesn't display tags except by yellow highlight.  There is no tag\nname and no way to see the tag object.  I think one way to do it would\nbe to draw marks in the description column, like gitk does.  Another\napproach would be to put all corresponding information in the patch\ndescription pane, perhaps highlighted.\n\nIt would be great to store the cache file somewhere under .git, perhaps\nunder a simpler name, such as .git/qgit-cache.  The trailing \".z\" should\nprobably be dropped, since the users are not supposed to decompress the\nfile or know anything about its internal structure.\n\nSettings should be reviewed for usefulness.  Some show go to the menu,\nsuch as \"Relative time in date column\".  It's hard to imagine that\nsomebody would use this option permanently.  \"Diff against working dir\"\nis already in the menu, and I don't think it merits to be in the\nsettings.  qgit can simply remember the menu setting.  \"Load file names\nin background\" should probably become a pair of radio buttons, since the\nantithesis is not obvious.\n\n\nAs far as I know, qgit is unique among git front-ends for being written\nin a non-interpreted language.  This fits well with git being designed\nfor speed.  It would be great if qgit received its fair share of\nattention from GUI experts that happen to be in the git list ;-)\n\n-- \nRegards,\nPavel Roskin\n"}]}