From: "Sławomir Lach" <slawek@lach.art.pl>
To: guix-devel@gnu.org
Subject: tao-dialog and writing some system tool in libgreattao
Date: Sat, 20 May 2023 19:25:30 +0200 [thread overview]
Message-ID: <4849462.31r3eYUQgx@localhost.localdomain> (raw)
I am author of libgreattao, the generalized user-communication library. It
could generate UI on the fly (by templates system) and use shell and GUI mode.
Additionally GUI mode could use console, GTK4, Qt5 backends.
Writing DE tools in libgreattao could brings unification and simplicity. For
example, xdg-su could be rewritten in libgreattao, instead of communication
with other tools. Libgreattao will load GTK or QT or console backend. KDE
devel could alter look of programs, creating own design files. The same could
be done by GNOME developers. It brings many possibilities.
Read more:
https://nintyfan.wordpress.com/2023/05/20/tao-dialog/
I known, that It lacks manpower. I rewrite everything currently as version 3,
which eliminates a lot of problems, but it does not compatible fully with
libgreattao2.
tao-dialog is small tool, which partially emulates kdialog and zenity. Maybe
in future I will add xmessage support also. It would not be drop-in
replacament maybe, but it would work great for simple usage. The great thing
is it uses libgreattao, so when script call tao-dialog inside terminal, it
loads console backend of GUI mode. DE could alter environment variable to asks
to load GTK+ or QT backend.
Read more: https://nintyfan.wordpress.com/2023/05/20/tao-dialog/ .
What next? When I done libgreattaoV3 and tao-dialog, maybe replace xdg-su and
write tool for replacing setting-executable-bit-and-running dialog. Maybe I
write select-app-to-open-file-with dialog. Instead of duplicate efforts and
write tools, desktop agents, backends, etc. not better write it in libgreattao
and allow it to generate UI or write template file to alter it. And it will
works in KDE, GNOME and Console?
Thanks,
Sławomir Lach.
reply other threads:[~2023-05-20 17:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4849462.31r3eYUQgx@localhost.localdomain \
--to=slawek@lach.art.pl \
--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).