Re: [Clockwork-developers] Kicking around some requirements

[Shawn M. <smc...@ei...>]

This one time, at band camp, Joel Loudermilk wrote:
>=20
> * Management GUI. Of course you can do everything from the command line, =
but
>   if you have a large enough schedule, a GUI might be the only way to
>   manage your schedule effectively. The GUI would be the only component
>   that might should be able to also run on Windows.

Two thoughts:

1) I think we should at least look at the feasibility of the client
running on Windows.  Like it or not, most enterprises have some Windows
in production as well.  I don't see much point in making the server run
on Windows, since security and reliability are design goals.

2) It'd be nice if the GUI layout was subject to configuration, not just
completely auto-generated.  I.E., if you could drag a box from one place
to another, so that it makes more sense to the humans staring blankly at
the screen, and retain that setting across invocations of the GUI.  I'm=20
not sure how to do that scalably, but then I'm not sure how to do it=20
non-scalably either.  :-)