-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,
I have now started to transform my ideas for the new GUI into pygtk and I
have currently produced http://www.theneb.co.uk/images/lsgDemo3.png

This is currently fully coded in pygtk without glade and in the next few
weeks I'll be developing the GUI into a well laid out state and then I'll
bolt on the liquidsoap communication.

The colours on the jingle board will be random when a user creates a new
board, then the user can either regenerate a new random set or choose their
own.

One main aspect of the GUI I will be heavily developing is User Control,
since it is assumed that the GUI will be in use in studio environments with
multiple users. Therefore we don't want users messing around with key studio
jingle boards and being able to touch the streams directly, some of these
requirements will come under user control within the main daemon and there's
plenty of time to discuss what strategy the team can take.

- From what myself and David B were talking about on irc today, there's the
choice of telnet, telnet + ssl, CORBA or even Operating system specific
sockets for communication (any more please add). Each of them come with
their own distinct advantages and it'll be good to have a full discussion of
which would be the best suited.

Another major aspect about the GUI is that in my current design I've moved
away from the detaching window form of the previous GUI, I need suggestions
on ways to handle this. Since some users might want to have multiple aspects
of the GUI visible at once and I don't want it to become an unorganized
chaos every time the program is opened.

Otherwise I hope you all like the pretty colours in the jingle screen and I
really hope all this works out and we can create a kick ass radio suite.


Regards


Peter Brooks
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFGULKj7l5nNkhXSO8RAj4lAJ0TiROhRzmzN8j6dSfIx1JqWV+cvgCeOeNF
SMpIA++U/KibPF/HhX1qzYI=
=xLiN
-----END PGP SIGNATURE-----

Répondre à