Re: [Zope-dev] Compatibility issues: ZPatterns 0.4.2,LoginManager 0.9.0
At 11:04 AM 8/27/00 +0100, Steve Alexander wrote: I have been putting CatalogTriggers as DataManagers directly in Specialists. And this *works*??? None of the "Acquired ... Provider" classes supported forwarding to an acquired trigger, as far as I can recall. The fact that it's so bloody awkward to forward to acquired providers is part of why I think they should be dropped. Hmm... looking at source code... aha! Okay, so "Link to Parent Data Plug-ins" provides linking to triggers. I'd forgotten about that, obviously. Dang. This seems to me the obvious place to do some triggering action that applies over all the Specialist's racks, but which has nothing to do with storage. Yes, it is. But it also adds to new user confusion, and leads to a bunch of otherwise-unnecessary code complication. In particular, Specialist wouldn't need to be a DataManager when it's really only a PlugInContainer. I don't yet use SkinScript. However, I imagine there are a number of uses for Triggers that apply at the level of abstraction of a Specialist. Would it be an undue hardship to copy these into all the relevant racks or customizers, until there is a feature to allow inclusion from another rack or customizer? Please think about keeping the feature, if it doesn't make things too complicated. Basically, the problem is that I am trying to decouple delegation interfaces from the ZPatterns core. That is, I'm trying to make it such that DataManagers don't have to know about all the possible things that can be delegated to Data Plug-ins. That way, as additional plug-in capabilities are added, such as content providers and local role providers, the DataManager class doesn't change, since it's just an intermediary for *finding* those providers, and giving dataskins certain persistence-related services. Unfortunately, using items that link to acquired providers with any kind of filtering means that the link itself must provide some form of the interface which is being delegated, which means that the link must know about all possible interfaces. :( Now, I can provide *unfiltered* linkage by direct delegation, but this would mean dropping the ability to selectively take only certain attributes or sheets from the parent. But I suppose that, compared to dropping the capability to acquire altogether, this might be preferable. Hmmm. Let me think about this. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Compatibility issues: ZPatterns 0.4.2,LoginManager 0.9.0
Phillip J. Eby wrote: Would it be an undue hardship to copy these into all the relevant racks or customizers, until there is a feature to allow inclusion from another rack or customizer? Not at all. :-) Now, I can provide *unfiltered* linkage by direct delegation, but this would mean dropping the ability to selectively take only certain attributes or sheets from the parent. But I suppose that, compared to dropping the capability to acquire altogether, this might be preferable. This sounds fine for my use of Triggers that apply across everything that a Specialist manages. -- Steve Alexander Software Engineer Cat-Box limited http://www.cat-box.net ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Compatibility issues: ZPatterns 0.4.2,LoginManager 0.9.0
Hi folks. I'm working on a ZPatterns 0.4.2b1 release for the early part of the coming week, and intend to bug Ty into perhaps releasing an 0.9.0 beta later in the week. However, these versions are likely to have some (hopefully minor) compatibility issues with previous releases. Specifically: * We would like to drop support for Zope 2.1.x from here on out. I know at least one user has a production 2.1.x system, and I hate to strand them, but at least they can continue to use existing ZPatterns releases until their client can upgrade. Dropping 2.1.x support means that we may be able to get rid of DynPersist, which should be a big plus for ease of installation. It also means that we'll be able to start adding newer capabilities that take advantage of 2.2.x-isms such as getPhysicalPath()/restrictedTraverse(), etc. * We would like to drop support for Specialists directly containing data plug-ins. This feature was intended to allow for acquiring shared data plug-ins from within Racks, so that common attribute or sheet providers could be shared among Racks without copying. In practice, Ty and I have never once used this capability, and it could be easily replaced with the ability to "include" a SkinScript within another SkinScript, if we take advantage of 2.2.x-isms. * Related to the above, the "Link to Acquired Provider" and "Acquired ... Provider" objects would no longer be needed, since they exist only to make use of shared plug-ins contained in Specialists. We would remove these classes from ZPatterns, causing any existing instances to become "broken". Deleting these "broken" objects, however, would restore normal operations of the system. As you can see, all of these issues are somewhat interrelated. I wanted to post some advance warning of all this, so that if anyone has any objections, they would have a last chance to protest. :) The overall release plan at this point is that the only other major features planned in the 0.4.x series are content providers (mirroring virtual sub-objects from SQL, LDAP, or whatever) and local role providers (computation by an object of local roles applicable to a user). I do expect to add a few minor features in the way of easier SkinScript editing, and some hooks to allow help to be added to the management tabs which are auto-generated for PlugInGroups. The next big project will be documentation, now that the feature set and terminology is beginning to stabilize. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )