Donnie Berkholz wrote:
Hey all,
I've been wanting a GUI for eselect lately, so tonight I hacked up the
start of one called eselect_zenity [1]. It only works for the most
trivial modules so far -- it has to parse eselect output, so special
parsers need to be written for each type.
On 10:54 Thu 08 Nov , Ciaran McCreesh wrote:
On Thu, 8 Nov 2007 02:48:13 -0800
Donnie Berkholz [EMAIL PROTECTED] wrote:
it has to parse eselect output
Part of the idea behind using standardised output functions was that
they could be replaced. The thought was, rather than trying to
Hey all,
I've been wanting a GUI for eselect lately, so tonight I hacked up the
start of one called eselect_zenity [1]. It only works for the most
trivial modules so far -- it has to parse eselect output, so special
parsers need to be written for each type. eselect_zenity uses
(surprise!)
On Thu, 8 Nov 2007 02:48:13 -0800
Donnie Berkholz [EMAIL PROTECTED] wrote:
it has to parse eselect output
Part of the idea behind using standardised output functions was that
they could be replaced. The thought was, rather than trying to parse
console-centric output, you'd swap in a different
On Thu, 8 Nov 2007 04:07:42 -0800
Donnie Berkholz [EMAIL PROTECTED] wrote:
I'll look into that. Got any good starting points (files, functions,
docs)?
Well, the whole of the eselect code is small enough that you should be
able to understand it pretty quickly... Then it'd just be a case of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
Hey all,
I've been wanting a GUI for eselect lately, so tonight I hacked up the
start of one called eselect_zenity [1]. It only works for the most
trivial modules so far -- it has to parse eselect output, so special
