Announcement: Pijul WebView


#1

I wrote a first draft of the interactive history browser I’m planning, similar to gitk and hgtk. It will make exploring the history of a pijul project much much faster.

You can check it out on the nest.


#2

That is great, thanks!

My personal configuration is that pijul is an alias, which does not work currently. You might be considering adding an option to set an environment variable to override pijul path.

Any way, I’ve been able to make your demo work by just hard coding the patch which works in my case. I will definitely keep a lok at your work, and remains available if you have any question, or specific feature you would like to see pijul gets.


#3

Fixed!

Well, the only thing I really miss is already planned for fixing, the ability to view patches, and the performance issue that makes pijul unusable on some of my personal projects which contain large versioned databases. When the new algorithm is implemented, I’ll probably be able to migrate all my projects to pijul!


#4

After struggling a bit with gtk, I decided to move from gtk to a simple local server serving html+css. Like gtk web and hg web.
It will allow me to quickly design a more pleasant and flexible ui.

For now internet explorer is not supported because it doesn’t support “details” elements


#5

I found out that pijul patch actually outputs some useful data about the changes. Probably when I tried it didn’t output anything because I actually tried it on a tag.

Anyway, I implemented a rough server with basic functionality. Click on any commit and it will show the patch!

There’s still plenty to implement, starting from converting the patch to a traditional diff, but this is already getting quite good, so check it out!


#6

Awesome! Do you think you could setup a “demo” webpage?


#7

Sadly not! Anything beyond static websites is completely beyond my skills, I don’t have the confidence to deal with real life servers, security, networks and stuff. The (super simple) flask app I put together is explicitely for local usage on trusted networks (when I run it, it tells me “WARNING: Do not use the development server in a production environment. Use a production WSGI server instead.”).

Actually, I didn’t wrote it as a competitor to the nest, but:

  1. as a tool for bringing something similar to the nest to lone developers working on local only projects (in particular, the ability to quickly view the details of a commit when browsing the log)
  2. maybe as a playground for testing features I’d like in the nest, like comments integrated in the repo itself.

I’d preferred to do it as a desktop application, but abandoned the idea because of the complexity and limited flexibility of the ui compared to html+css.

(Though you are free to reuse it if it’s of some worth to you, I’d be glad!, i’m releasing it as libre software).