Zope on Windows: enhancements proposed
We've got a wonderful zope control panel (which installs into the standard windows Control Panel) and zope service which we'll be making available in binary and source form this week. Like the Mac OS X controller, this is simply a trivial re-branding extension of our work in supporting the usability of our Bizar Shop product. The windows controller works on win95/win98/NT/win2k. It controls a "real" windows service on platforms were services are run (NT/win2k), and otherwise controls a "service daemon" which stays in the system tray. We'll call this service "Zope", and its job is to lauch "python [script] [args]" with some Zope-specific environment fiddling (INSTANCE_HOME env, cd ${SOFTWARE_HOME}, STUPID_LOG_FILE env). The current method of starting Zope as a windows service using PythonService.exe is kludgy, mostly because of the unnecessary layer of python. The Zope binary distribution's use of PythonService.exe does the same thing that our Zope service does (in the end), which is to lauch "python z2.py [args]". We'd like to propose that the service distributed with Zope move over to using our code. Our control panel will be able to control "Zope (WebSite)", but we probably won't offer the ability to configure it (editing the z2[s].py file in-place is possible - we do that now - but it's rather hackish). So, best scenario is that Zope ships with the controller and our service. Worst scenario is that the controller is downloaded separately and can only stop/start PythonService. In the second case, we'd still ship our service and install it - meaning that there'd be two Zope services in the service manager, but at least the controller, which appears in the control panel, would still be able to fully control Zope. As a separate issue - we're curious about the naming of the Zope installation - why is it called WebSite (and the Zope service "Zope (WebSite)")? The name clashes with another product that's fairly well-known in the windows community originally from O'Reilly: http://www.oreilly.com/software/index.html ... and since Zope is a fairly distinctive name ... Richard ps. happy to put this up as a project if required.
We'd like to propose that the service distributed with Zope move over to using our code.
Great, Im really looking forward to an improved Windows installation. But lets get it out there play with it before anything major happens like shipping Zope with it :)
As a separate issue - we're curious about the naming of the Zope installation - why is it called WebSite (and the Zope service "Zope (WebSite)")? The name clashes with another product that's fairly well-known in the windows community originally from O'Reilly: http://www.oreilly.com/software/index.html ... and since Zope is a fairly distinctive name ...
It is annoying but Zope wins there because OReilly isnt making WebSite anymore. Its just a name, I find the Zope (%s) bit more annoying than anything :)
ps. happy to put this up as a project if required.
Thats probably a good idea. What about other issues such as install and removing service easily later, STDERR logging not going to /dev/null, lack of start menu icons and other windows issues... Cheers -- Andy McKay
On Tuesday 25 September 2001 14:23, Andy wrote:
We'd like to propose that the service distributed with Zope move over to using our code.
Great, Im really looking forward to an improved Windows installation. But lets get it out there play with it before anything major happens like shipping Zope with it :)
Fer sure :)
It is annoying but Zope wins there because OReilly isnt making WebSite anymore.
Yeah, they seem to have sold it to someone else...
Its just a name, I find the Zope (%s) bit more annoying than anything :)
Agreed.
ps. happy to put this up as a project if required.
Thats probably a good idea. What about other issues such as install and removing service easily later, STDERR logging not going to /dev/null, lack of start menu icons and other windows issues...
These are all things we've addressed, but it'd be good to note them somewhere. We've tried to make the process of using Zope (and hence our product) as painless to the average Windows user (and Mac user) as possible. Richard
These are all things we've addressed, but it'd be good to note them somewhere. We've tried to make the process of using Zope (and hence our product) as painless to the average Windows user (and Mac user) as possible.
Oooh, Im a happy camper. -- Andy
participants (2)
-
Andy -
Richard Jones