Re: gnome-config problems



Miroslav Silovic <silovic@zesoi.fer.hr> writes:

> Equivalent Scheme code:

> '(panel
>   (param bgcolor grey)
>   (menu main "Main Menu"
> 	(menu programs "Programs"
> 	      (program netscape "Netscape" "/opt/bin/netscape")
> 	      (program gimp "Gimp" "/usr/bin/gimp"))
> 	(link (applet logout)))
>   (applet clock
> 	  (param whatever something))
>   (applet menu
> 	  (param whatever something))
>   (applet logout
> 	  (link "panel.guile" Logout)))

How about "live" config files, something along the lines of:

(define my-panel (make-proc "/usr/bin/gpanel"))
(set-attribute my-panel 'bgcolor 'grey)
(define my-main-menu (add-menu my-panel "Main Menu"))
(define my-sub-menu (add-menu my-main-menu "Programs"))
(add-menu my-sub-menu ( "Netscape" . (exec "/opt/bin/netscape)))
(add-menu my-sub-menu ( "Gimp" . (exec "/usr/bin/gimp)))
(define my-plugin (add-plugin "Clock" "/usr/bin/gclock"))
(set-attribute my-plugin 'whatever 'something)
	:	:
(open-window my-panel)

This file could be an executable, and the functions could hook into the 
panel's CORBA interface.  This way, I could start/run manipulate several 
applications from one startup-script, some of which may not have to be
visible (open-window...)

This may not be a full replacement for "dead" config files, but I think
the concept is interesting.

~kzm
-- 
If I haven't seen further, it is by standing in the footprints of giants



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]