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

Re: [PATCH 2/2] gitweb: Show trailing slash when listing tree entry in tree listing

From
JWJosef Weidendorfer <josef.weidendorfer@gmx.de>
Date
Oct 10, 2006, 13:14 UTC
Message-ID
<200610101514.20705.Josef.Weidendorfer@gmx.de>
In-Reply-To
<452B54A5.4080901@op5.se>
On Tuesday 10 October 2006 10:07, Andreas Ericsson wrote:
> I like my links blue and underlined. Can't be arsed to mouse over things 
> to figure out if they're clickable. If they're not blue and underlined, 
> they're not, insofar as I'm concerned.
Same opinion here.
Better be functional than beautiful but confusing.

If Gitweb would be a desktop application, we would have context menues for different actions on list items, but that is not really possible with web pages (?), and would be unexpected.

Gitweb is a web interface. So lets use the conventions for web pages. One solution is to repeat the actions everytime in every row of a list, as we do now (and I think is fine; we could use icons instead). The other standard solution is to have checkboxes at the front of every row, and the actions as buttons, which means two mouse clicks (which IMHO is a really bad UI).

And as we go with the first solution, we explicitly should state all
possible actions, and not provide an hidden action which is triggered
when clicking on the entry name. Currently, it is not very clear that
* we have a "blob" action at all,
* clicking on the entry name provides the blob action. Seems to me
like an arbitrary choice. Why not "raw" or "blame" instead?
Therefore, I am in favor of reintroducing the "blob" link,
which allows the entry names to stay as they are
now (and could get the hidden redundant action).

One thing I found confusing in this regard the first time: Why do list rows show a recoloring with mouse over? This somehow suggest that the whole row makes up some kind of a button and is clickable (BTW, blame pages do not do this). Can we get rid of this?

Josef
Previous: Andreas EricssonNext: Luben Tuikov
Message 47 of 54 in “gitweb: Do not print "log" and "shortlog" redundantly in commit view”
  1. gitweb: Do not print "log" and "shortlog" redundantly in commit viewLuben Tuikov, Oct 5, 2006
  2. Jakub NarebskiOct 6, 2006
  3. Petr BaudisOct 6, 2006
  4. Luben TuikovOct 6, 2006
  5. Petr BaudisOct 7, 2006
  6. Jakub NarebskiOct 7, 2006
  7. Petr BaudisOct 7, 2006
  8. 1/2 gitweb: Show snapshot links for tree entries in tree listingPetr Baudis, Oct 7, 2006
  9. Luben TuikovOct 7, 2006
  10. Petr BaudisOct 7, 2006
  11. Luben TuikovOct 7, 2006
  12. Petr BaudisOct 7, 2006
  13. Junio C HamanoOct 7, 2006
  14. Luben TuikovOct 8, 2006
  15. 2/2 gitweb: Show trailing slash when listing tree entry in tree listingPetr Baudis, Oct 7, 2006
  16. Luben TuikovOct 7, 2006
  17. Jakub NarebskiOct 7, 2006
  18. Petr BaudisOct 7, 2006
  19. Jakub NarebskiOct 7, 2006
  20. Petr BaudisOct 7, 2006
  21. Jakub NarebskiOct 7, 2006
  22. Petr BaudisOct 9, 2006
  23. Junio C HamanoOct 9, 2006
  24. Junio C HamanoOct 10, 2006
  25. Luben TuikovOct 10, 2006
  26. Junio C HamanoOct 10, 2006
  27. Luben TuikovOct 10, 2006
  28. Jeff KingOct 10, 2006
  29. Luben TuikovOct 10, 2006
  30. Jeff KingOct 10, 2006
  31. Jakub NarebskiOct 10, 2006
  32. Luben TuikovOct 10, 2006
  33. Junio C HamanoOct 10, 2006
  34. Jakub NarebskiOct 10, 2006
  35. Luben TuikovOct 10, 2006
  36. Jakub NarebskiOct 10, 2006
  37. Luben TuikovOct 10, 2006
  38. Luben TuikovOct 10, 2006
  39. Jakub NarebskiOct 10, 2006
  40. Luben TuikovOct 10, 2006
  41. Jakub NarebskiOct 10, 2006
  42. Jakub NarebskiOct 10, 2006
  43. Andreas EricssonOct 11, 2006
  44. Luben TuikovOct 10, 2006
  45. Jeff KingOct 10, 2006
  46. Andreas EricssonOct 10, 2006
  47. Josef WeidendorferOct 10, 2006
  48. Luben TuikovOct 10, 2006
  49. Josef WeidendorferOct 10, 2006
  50. Luben TuikovOct 10, 2006
  51. Junio C HamanoOct 10, 2006
  52. A Large Angry SCMOct 7, 2006
  53. Junio C HamanoOct 7, 2006
  54. Luben TuikovOct 8, 2006

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.