unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: guix-devel@gnu.org
Subject: Re: Guix Front End (GUI) and making it more mainstream, popular in scientific community.
Date: Thu, 29 Oct 2020 20:34:33 +0100	[thread overview]
Message-ID: <20201029203433.2caaa74e@scratchpost.org> (raw)
In-Reply-To: <CAF-xJgsynM3KSzuM__f9dSPUC0epJ2QKdFwDftiLhTTuMfaTxw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2193 bytes --]

Hello everyone,

On Thu, 29 Oct 2020 21:55:10 +0530
Aniket Patil <aniket112.patil@gmail.com> wrote:

>If we build a GUI frontend then we can attract more
> people who don't identify themselves with CLI users. As such there are many
> people like writers, Graphic Designers, General users, etc. who don't
> bother about CLI, will love to see such a package manager.  And considering
> the fact GUIX lets rollback to the previous version of the package it will
> be very helpful in the scientific community, to maintain and work with
> different versions of packages.

I've got one at https://gitlab.com/daym/guix-gui/ .

As of commit 978f7d92b4486829fd4f5030baf2d42c001b0890 (current master),
guix-gui works well enough that you can see the current profile, you have
(slow) tooltips, you can type to search, you can view the previous generation,
and you can get a list of all installable packages in Guix.

Not much more works yet because I've hit this (design) bug in Guix and/or GNOME:

* https://github.com/spk121/guile-gi/issues/96

I hadn't noticed before just how bad a match Guix's private dependencies (which
I think are a good thing) and GNOME's object system is (see link above).

> P.S: I don't know whether GUI for Guix exists or not, to my knowledge it
> doesn't. If I am mistaken please enlighten me on this topic.

It does kinda exist--but working on GUIs in Guile is like pulling teeth.

I'm used to seamless integration like PyGTK is in Python--PyGTK feels
EXACTLY like a native Python library.  You can't tell that it's implemented
in C at all.

The way it is in Guile is not seamless.  Furthermore, there are fundamental
problems in how the package "gobject-introspection" is designed (see link
above)--so I can't see how this can be resilient or consistent at all.

(Also, I've used Delphi before--that's basically the holy grail of GUI
development.  That doesn't help making me less grumpy using this contraption
string-and-duct-tape barely-holding-together contraption instead)

In any case, with all the involuntary yak-shaving I have to do it's gonna
take a while.

Or I could just use Gtk in C and use popen("guix ...").

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2020-10-29 19:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 16:25 Guix Front End (GUI) and making it more mainstream, popular in scientific community Aniket Patil
2020-10-29 18:22 ` jbranso
2020-10-29 18:38   ` Pierre Neidhardt
2020-11-01 21:46     ` Ludovic Courtès
2020-11-02  7:40       ` Pierre Neidhardt
2020-11-02  8:27         ` Jan Nieuwenhuizen
2020-10-29 18:45   ` jbranso
2020-11-02  7:41     ` Pierre Neidhardt
2020-10-29 19:15 ` zimoun
2020-10-30  8:49   ` Lars-Dominik Braun
2020-11-01 21:53     ` Ludovic Courtès
2020-11-02 10:03       ` Taylan Kammer
2020-11-02 10:24       ` Gtk via the web Danny Milosavljevic
2020-11-03  9:54         ` aviva
2020-11-03 13:31         ` Ludovic Courtès
2020-10-29 19:34 ` Danny Milosavljevic [this message]
2020-11-01 22:09   ` Guix Front End (GUI) and making it more mainstream, popular in scientific community Ludovic Courtès
2020-11-02  7:44   ` Pierre Neidhardt
2020-11-02 10:17     ` GNOME in Guix Danny Milosavljevic
2020-11-06  9:41       ` Pierre Neidhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201029203433.2caaa74e@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).