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

Re: The future of gitweb - part 2: JavaScript

From
Peter Vereshagin <peter@vereshagin.org>
Date
Apr 16, 2011, 17:12 UTC
Message-ID
<20110416171200.GB8201@external.screwed.box>
In-Reply-To
<201104141154.55078.jnareb@gmail.com>

Any time of year you can find me here Jakub. 2011/04/14 11:54:53 +0200 Jakub Narebski <jnareb@gmail.com> => To git@vger.kernel.org : JN> So what are your ideas and comments on the issue of JavaScript code JN> and JavaScript libraries / frameworks in gitweb?

I'd like to note here that js use intensification may be need to be kept separated from extending of the http functions of the regular git use which I believe is currnt;y implemented by mean of gitweb. E. g., I think one day we shall be able to git-push, etc. to http(s) git repository via http(s) the same way we can already git-fetch today. This is another, less explicit way the gitweb is and will be being used, right? Having that in mind I suppose some parts of gitweb development, e. g. code and/or docs may need to be separated like it is done now for cli interface, the porcelain versus plumbing, as both cli and the web can be considered to be the interfaces

One day it will be obvious for the non-interactive web clients like git to have the js capabilities embedded. This will mean we perhaps will have technology other than js for such a separation. But I believe gitweb will have js for ui somewhat earlier.

73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB 12F8 0CE1 4AAC A0E2 6627) -- http://vereshagin.org

Previous: david@lang.hmNext: Jakub Narebski
Message 11 of 30 in “The future of gitweb (long term goals)”
  1. Jakub NarebskiFeb 14, 2011
  2. Michael J GruberFeb 15, 2011
  3. Jakub NarebskiFeb 21, 2011
  4. Michael J GruberFeb 23, 2011
  5. The future of git-instaweb (was: Re: The future of gitweb (long term goals))Jakub Narebski, Feb 25, 2011
  6. Ævar Arnfjörð BjarmasonFeb 22, 2011
  7. Jakub NarebskiFeb 22, 2011
  8. The future of gitweb - part 2: JavaScriptJakub Narebski, Apr 14, 2011
  9. Michał ŁowickiApr 14, 2011
  10. david@lang.hmApr 15, 2011
  11. Peter VereshaginApr 16, 2011
  12. Jakub NarebskiApr 16, 2011
  13. Peter VereshaginApr 16, 2011
  14. Jakub NarebskiApr 16, 2011
  15. Peter VereshaginApr 16, 2011
  16. Jakub NarebskiApr 16, 2011
  17. Jakub NarebskiApr 16, 2011
  18. Peter VereshaginApr 16, 2011
  19. Jakub NarebskiApr 17, 2011
  20. Gitweb != HTTP back-end {Was: Re: The future of gitweb - part 2: JavaScript}Drew Northup, Apr 20, 2011
  21. Jakub NarebskiApr 20, 2011
  22. Pau Garcia i QuilesApr 16, 2011
  23. Jakub NarebskiApr 17, 2011
  24. Pau Garcia i QuilesApr 17, 2011
  25. Jakub NarebskiApr 18, 2011
  26. Petr BaudisApr 17, 2011
  27. Jakub NarebskiApr 18, 2011
  28. Petr BaudisApr 18, 2011
  29. Jakub NarebskiApr 18, 2011
  30. Drew NorthupApr 20, 2011

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.