Many people have suggested splitting out the PlugIns part of ZPatterns as a seperate product for general Zope use. In addition to this, it is becoming clearer to me as I work on docs, etc., that there really is only one thing left in ZPatterns after you take out PlugIns, and that is DataSkins. (Pretty much everything else in ZPatterns only has meaning in relation to DataSkins.) So, I am thinking perhaps I should split ZPatterns into two products: PlugIns and DataSkins. The DataSkins product would require the PlugIns product. LoginManager would require both. For backward compatibility, there would need to be a "final release" of ZPatterns which contained stubs to load in classes from their new locations, so that existing objects stored in ZODB's would not be "broken". Newly created objects, of course, would refer to the new products automatically. The term "ZPatterns" would then go away, which is just as well because it doesn't really mean anything, anyway. :) Please let me know if you have any comments or questions on this. _____ _/__) ___/