It is ideal as an intranet and extranet server, as a document publishing system, a portal server and as a groupware tool for collaboration between separately located entities.
A GUI Controller is akin to the existing Controller for Plone and Zope for Windows. It provides a simple GUI interface to the Zope functions, such as stop, start, configure and monitor the server. There are a few areas of functionality:
configure: the ability to change the configuration of the Zope instance without having to know rather arcane Z2.py command line switches. On Windows this would involve changing the service settings. This would give the user the ability to change ports, debug mode settings and so on.
basic admin functions: start, restart, pack, create emegency user, uptime etc...
monitor: see the current status of the Zope instance, how busy it is, what threads are being used, cache sizes, databases sizes, ZEO stats... the list goes on
The current Controller runs on Windows and the Mac, each instance has a different code base. The new Controller will be written mostly in Python using a cross platform toolkit for that will allow us to run the Controller on at least: Windows, Mac and Linux. Whilst there will obviously be some different code to handle different platforms, the aim is to reuse as much code and functionality as possible. This is a major motivation behind the scheme.
The Contoller should be able to connect to multiple instances from one location, regardless of location. Allowing one user to remotely manage many Zope or Plone instances.