-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wichert Akkerman wrote: > Previously Tres Seaver wrote: > >>My understanding of PlonePAS was that is was a "canned setup" for a PAS >>instance. I didn't realize that it provided additional skins as well, >>and in fact I don't know why it would do that. > > > PlonePAS includes three kind of things: extra methods to provide a fair > amount of compatibility with GRUF, extra features (local role plugins, > mutable properties, etc.) and a set of templates to allow Plone to work > with (Plone)PAS. > > In PlonePAS 2.x and Plone 2.5 all the templates have been moved > from PlonePAS to Plone. I have a branch for PAS on which I'll work to > merge at least some of the features from PlonePAS into PAS. The GRUF > backwards compability will disappear, proably in Plone 3.5.
Cool, thanks for the explanation. The extra features are plugins, right? Do they require that the rest of the application break the encapsulation (i.e., talk directly to plugins)? Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEYfmC+gerLs4ltQ4RAgn3AKCCAXCZ/lSPss6mnxMIK1zTiGPTuwCfdmNx hb9p5ALqMZS8DU7pcma92go= =h4Ej -----END PGP SIGNATURE----- _______________________________________________ Zope-PAS mailing list Zope-PAS@zope.org http://mail.zope.org/mailman/listinfo/zope-pas
