to do

2002-01-05 Gary Poster [email protected]

Speed tests and tweaks
CMF arbitrary properties need to be thought through
unit tests, functional tests
The aliasName--which must be the alias id in some circumstances but can be its own value in others--is problematic. I made the choice to operate in this way because it was unnecessarily limiting in some circumstances to force an alias to use the id as its name, but a necessity when the alias was going to try to force itself in dynamic links (BASEx, URLx, etc.). However, that then makes it very difficult to prevent users from making basic conflicting naming errors. I have tried to catch this in as many places as possible, but can still conceive of ways in which my checks might be circumvented. I wonder if the flexibility of being able to name an alias the same name as another as long as the two were to appear in different folders is really important enoughto warrant this kludge
Some other folks are planning on contributing to this project: see http://sourceforge.net/projects/vhf/ if you'd like to participate

2002-01-01 Gary Poster [email protected]

Considering adding a standard browser redirect object to be held in host objects along with alias objects. Not sure if it would work. Need to experiment on setting RESPONSE within BeforeTraverse hook call...
I can see part of how one could put the VHF in the control panel--make a variation on BeforeTraverse.NameCaller that could find the VHF in the control panel. Still haven't really explored how you put objects in the control panel, though... Is someone else working on this kind of functionality? Not sure I care about this... Does anyone else, much?
I have never done unit tests and have no clue how to do them in Zope. However, I'll pick at it when I get a chance, as I certainly see the value.

HELP REQUESTED:

any critique would be appreciated; in particular, suggestions on security, interfaces, optimizations, and breadcrumbs API would be appreciated. Heh, did I forget anything?

Nov 29 2001 Gary Poster [email protected] This is an EARLY BETA release. INTERFACES MAY CHANGE.

Finalize an interface for the Virtual Host objects so that they could be replaced with different functionality and still have the Virtual Host Folder be fine with it. Make it an actual __implements__ kinda thing as described in the dev guide. I'm on track for this--I think the interface I'm hinting at now in the code isn't too bad--but want to delay the final decision. The security permissions are the items I'm not sure what to do with to be honest. Since some folks still write DTML methods, and DTML is a protected environment, maybe I should open up my setters to a Protected status, rather than Private. Obviously I'm not sure which end is up for this: expert advise appreciated.
Write the planned CMF Virtual Host Tool
On the basis of that planning and writing, finalize the Virtual Host Folder interface. Again, use __implements__ and all, and again, I think it's close.
More debugging, including finding the fix for the unloading help file VHF_Configure.stx